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.