This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
The main benefit is that they help you concentrate on the different risks a project faces. The inception phase is concentrating on the questions "Can this be done (by use)? How much is it likely to cost?". The elaboration phase concentrates on "What architecture/techniques should we use." - once the team gains confidence in this, you reached the construction phase. I don't know what to think about the transition phase, though.
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Originally posted by Hari babu: Hi What are the benefits you guys can think of when we break a development cycle into inception,elaboration, construction and transition phase? Hari
Another benefit is the user feedback at the end of each stage. E.g. At the end of the inception phase the user can tell you if the requirements define the system that they want. If not then it is pointless continuing. Regards, Fintan
Originally posted by Fintan Conway: Another benefit is the user feedback at the end of each stage.
Personally, I would like user/customer-feedback much more often than after every phase. Preferably at least every couple of weeks, at the end of an iteration. You could do this without having the phases, so it seems to me...
E.g. At the end of the inception phase the user can tell you if the requirements define the system that they want.
I think I don't fully understand - isn't it the user/customer who is *specifying* the requirements?