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

Project Portal
| See Also How To: Create an Iteration Plan |
| ### Next Steps Create Solution Architecture Implement a Development Task Fix a Bug Guide Project |
| Plan an Iteration Project Manager
|  | Participating Roles Responsible: Project Manager
### Overview To plan an iteration, determine the right balance of scenarios, quality of service requirements, and bug allotments for the upcoming iteration. The amount of work that can be completed in an iteration is limited. The scenarios and quality of service requirements with the biggest business value are prioritized for inclusion in the current iteration. An initial iteration plan is created using the estimated scenarios and quality of service requirements. Once the scenarios and quality of service requirements are part of the iteration plan, they are written up by the business analyst as scenarios. Developers and testers then divide the scenarios into tasks and create more detailed estimates. The new detailed estimates are used to load balance the tasks assigned to developers. The iteration planning meeting brings together the appropriate business analysts, project managers, and developers to finalize the iteration plan. # Entry Criteria Dependencies: The scenario list and quality of service requirements list have been prioritized and published to the project portal. # Activities
1 | Determine Iteration Length | Create the project plan. Check the scenario size. Examine integration costs.
2 | Estimate Scenario | Identify a subset of the scenario list. Create implementation estimates. Identify special needs.
3 | Estimate Quality of Service Requirement | Identify a subset of the quality of service requirement list. Create implementation estimates. Identify constraints.
4 | Divide Scenarios into Tasks | Identify development tasks. Create development tasks. Choose development tasks. Reassign the scenario. Create test tasks.
5 | Divide Quality of Service Requirements into Tasks | Identify development tasks. Create development tasks. Choose development tasks. Reassign the quality of service requirement. Create test tasks.
6 | Schedule Bug Fixing Allotment | Schedule the bug allotment. Consider dependencies and other factors. Hold the iteration planning meeting.
7 | Schedule Scenario | Create an initial iteration plan. Adjust the initial iteration plan. Hold the iteration planning meeting.
8 | Schedule Quality of Service Requirement | Create initial iteration plan. Adjust the initial iteration plan. Hold iteration kickoff meeting.
# Exit Criteria
| The iteration plan is complete and published to the project portal.
| An appropriate amount of work is scheduled for the iteration.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |