Overview |  | Roles |  | Work Items |  | Views |  | Index |  | Glossary |

Project Portal
| ### Next Steps Schedule Scenario |
| Activity: Estimate Scenario
Project Manager
|  |  |  | Plan an Iteration |  |
|  | Participating Roles Responsible: Project Manager Consult: Developer
### Overview Scenario estimates are used to provide a general picture for understanding how much effort the scenario requires. These estimates aid the business analyst in making priority decisions and setting external expectations. The project manager works with the developers to collect estimates for the top ranked scenarios in the scenario list. # Entry Criteria Dependencies: The length of the iteration is defined for the project. Notification has been received that the scenarios in the scenario list have been prioritized, published, and are ready to be estimated. # Sub-Activities
1 | Identify a Subset of the Scenario List | Open the scenario list from the project portal. For each of the highest priority scenarios, determine the appropriate developer or development group to provide an estimate. Provide estimates for enough of the highest priority scenarios to provide options for the business analyst. Provide estimates for enough scenarios to encompass approximately twice the average velocity.
2 | Create Implementation Estimates | Work with the developers to do a rough order of magnitude estimate of the time needed to implement each scenario.All estimates should be made in ideal person days. If further elaboration is necessary, work with the business analyst and the developers to add more detail to the scenario. Update the scenario list to reflect these estimates. Publish the list to the project portal.
3 | Identify Special Needs | Work with the developers to identify risks that can delay or prevent successful completion of the work required for realizing the scenarios, such as knowledge deficiencies and third-party software dependencies. Create a risk work item describing any identified risks. Communicate any special needs that a scenario might have. Look for potentially overloaded developers or dependencies that might affect the scheduling.
# Exit Criteria
| The highest priority scenarios have estimates that indicate ideal person days needed.
| The updated scenario list is published to the project portal.
| Special resources, risks, or constraints associated with realizing a scenario are communicated and if necessary, recorded in the scenario work item.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |