2010 07 Jun
In traditional projects, and the old life cycle management methodologies, the requirements changes were so hard, and the teams try to resist it as possible. So the detailed requirement catching was the first goals of project. So to minimize the changes in the requirement team shall include whatever they can imagine in their analysis and have to see the and predict the coming path for the software in order to minimize the final cost.
In contrast agile methodologies easily respond to changes, they are built on the base that requirements evolve, and it’s impossible to catch all the requirements even if you analyze and design a project for a long time.
In agile projects the requirements evolve but he timescale is fixed, so if an amount of work will be added to the project a comparable amount should be removed in order to meet the deadline.
