1

Determine an Overall Priority

• Assign an overall priority for each scenario in the list. Record the corresponding numeric value in the rank field in the scenario list.
• Sort the scenarios list by rank. Place the highest priority scenarios first on the list. Rank the remaining requirements against one another.
• Close the low priority scenarios that will be implemented in a future release using the deferred reason code.
• Save and publish the list to the project portal.

2

Outline High Priority Scenarios

• Use the scenario description template to outline and provide a brief description of the highest priority scenarios. The outline should contain enough detail for developers to provide an estimate.
• Add notes in the description field outlining complexities surrounding of the quality of service requirements.
• Save and attach the outlined scenario description to the scenario work item.

3

Communicate Need for Estimates

• Send a notification to the project manager and developers requesting general estimates for the top scenarios.
• Set expectations that the estimates are used to get an overall understanding of how difficult each scenario is to implement.
• Assign a due date for returning the estimates. Provide a description for the scenario if any additional details are needed.

4

Split or Reprioritize Requirements

• Optional
• If the cost of the scenario exceeds the iteration budget, determine if the requirement can be split.
• Split the scenario into two or more smaller ones if splitting is deemed appropriate.
• Close out or defer any scenarios deemed too costly.
• Revisit the priorities based on development estimates and obtain further estimates to identify requirements for the upcoming iteration.

A prioritized list of scenarios is published to the project portal.

The highest priority scenarios in the list have completed estimates.