Developing the Scope and Requirements
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, gives feedback, and thereby influences the next increment’s design. Taken holistically, feedback, reflection, and next-iteration influences present unique challenges in scope definition and requirements management.
Actual outcomes are more dynamic over time than is a plan-driven project development ...