Statistics: (276 Views) (0 Comments) Posted by: adrian on Tuesday, March 04, 2008 Categories: Project Management, Agile Methods, Requirements Management and Communication (BABOK KA)

Agile software development teams embrace change, accepting the idea that requirements will evolve throughout a project. Agilists understand that because requirements evolve over time that any early investment in detailed documentation will only be wasted. Instead agilists will do just enough initial requirements envisioning to identify their project scope and develop a high-level schedule and estimate; that’s all you really need early in a project, so that’s all you should do. During development they will model storm in a just-in-time manner to explore each requirement in the necessary detail.

This article addresses the following issues:

• The agile change management process
  • Freezing requirements during an iteration?
  • Modeling ahead?
• Why requirements change
• Prioritizing requirements
• Estimating requirements
• Why this is desirable
• Potential challenges with this approach

Author: Scott W. Ambler