Agility reduces the upfront requirements effort by focusing only on business need, but when the development team starts analyzing, the functional requirements and business rules emerge. If you don’t capture them, you are guaranteed to forget decisions the day after the iteration ends. A functionally organized, continually updated, requirements model informs many downstream efforts, including user acceptance testing, end user training, bug verification, and even preparation of new user stories.
Agile Requirements Manager, Mia McCroskey, will share best practices for agile requirements management:
- Using the functional model to determine when a feature was coded
- Deciding who should capture the requirements during an iteration
- Choosing what and when to document
- Learning how to maintain traceability
- Managing and maintaining cost effective projects
Mia will explain how IBM Rational DOORS provides her teams with easy access to their requirements, including feature release history, related functionality, and most importantly, a record of what they coded in the last iteration.