Agile methods encourage requirements to change as often as necessary to ensure that the customer receives the best value for the resources committed.
A requirements paradox: Requirements must be stable for predictable results. However, the requirements always change.
Agile methods trade on the concept of being adaptive to changing customer needs. The scope evolves as the customer is exposed to each product release and gives feedback, thereby influencing the next increment’s design. Taken holistically, feedback, reflection, and next-iteration influences present unique challenges in scope definition and requirements management. Traditional cause and effect plan-to-product relationships ...