Scenario C: Find and fix an unsatisfied requirement

Pre-conditions

1. A set of requirements for the next release/milestone/sprint is identified
2. This requirement set is linked to a planned set of corresponding change requests
3. The requirement set is also linked to a test plan
4. Links are created between requirements, change requests and test cases

Scenario

1. Close to the end of the iteration, a requirement with no corresponding test cases is identified in the requirement set
   1. Alternatively, it could be a requirement with failing test cases, or incomplete or no change requests
2. The problem is brought to the attention of the right people
3. The problem is addressed
   1. Test cases are created or updated and linked to the requirement
4. The requirement set provides a more accurate overview of the progress made towards the next release
   1. No requirements should be flagged as problematic

Post-conditions

• The user can check that the requirement set does not contain any requirements with missing test cases