• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

What's the difference between ExtremePlanner & FileNet's Team Collaboration Manager?

 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello ALL

Can anybody please tell me the difference between the ExtremePlanner & FileNet's Team Collaboration Manager which was introduced in their new P8 suite.

Thanks in advance for your valuable postings

--
Regards,
Atul Shinkar
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Atul Shinkar:
Hello ALL

Can anybody please tell me the difference between the ExtremePlanner & FileNet's Team Collaboration Manager which was introduced in their new P8 suite.

--
Regards,
Atul Shinkar



Well, I don't know anything about FileNet's products, but according to their website:

"It provides the contextual framework and collaboration tools, including discussion forums, live meetings, and interactive polls, to enable group members to share information and participate in processes to facilitate group decision-making."

ExtremePlanner does not do discussion forums, live meetings or interactive polls, so I'm pretty sure that would be one major difference :-)

What it does do is help agile software teams track user stories (features or defects) through multiple planning cycles (iterations) and delivery to customers (releases).

Hope that helps, at least a little bit.
 
Atul Shinkar
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks a lot SIR
The information you provided was really good.
I again want to ask you one more question that does "ExtremePlanner" follows any SDLC Model or it itself is a new SDLC Model?


Regards,
Atul Shinkar
 
Dave Churchville
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Atul Shinkar:
Thanks a lot SIR
The information you provided was really good.
I again want to ask you one more question that does "ExtremePlanner" follows any SDLC Model or it itself is a new SDLC Model?

Regards,
Atul Shinkar



ExtremePlanner is not itself an SDLC (software development life cycle), but can be used to support most iterative development processes.

Most of the features were designed to support Agile processes such as Extreme Programming (http://www.extremeprogramming.org) and Scrum (http://www.controlchaos.org).

These processes have in common the idea of an iterative approach to development. Frequent, consistent delivery of running, tested features that add the most business value (as determined by the customer).

A typical Agile development cycle looks like this:

1. Release Planning - prioritize the backlog of features and choose the highest priority ones that we have the capacity to implement by a certain date

2. Iteration Planning - given a set of priorities, choose a subset that we can get done in the next 2 to 4 weeks. Break features down into development tasks and write acceptance tests for the upcoming features to be implemented.

3. Development and Daily Standups - in the middle of an iteration developers do a little design, a little implementation, a little testing, and a little code review. Each day the team meets very briefly to discuss what they completed previously, what they are working on next, and any obstacles.

4. Iteration Review - At the end of an iteration, the team demonstrates completed, tested, working functionality to the customer to get feedback and direction. At this time the customer can request new features and re-prioritize the backlog before the next iteration begins.

5. Retrospective - Team discusses what's working well and what needs improvement (need more naps, better test coverage, shorter meetings, etc.)

6. Repeat steps 2 - 5 until the release, take a few days to recharge, then start from step 1 again.
 
reply
    Bookmark Topic Watch Topic
  • New Topic