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

Project Portal
| See Also Assess Progress |
| Activity: Monitor Iteration
Project Manager
|  |  |  | Guide Iteration |  |
|  | Participating Roles Responsible: Project Manager
### Overview Understanding an iteration’s progress is critical to its success. One of the most important elements in measuring progress is the resolution of high priority scenarios, quality of service requirements, and bugs for the iteration. The backlog and bug reports show which tasks are still open for each of these work item types. Identify tasks to be finished, and communicate priorities so the most important parts of the iteration are completed first. The goal of the project manager is to identify potential blocking issues or bottlenecks and move the project forward. # Entry Criteria Dependencies: The final iteration plan is complete and the iteration has begun. # Sub-Activities
1 | Review Work Item Priorities | If the priorities of the scenarios or quality of service requirements change within an iteration, it is the responsibility of the project manager to bring the business analyst, architects, developers, and testers together for a short meeting to discuss the changes. Priorities may change for many reasons including technical reasons, changing customer priorities, or dependencies.
2 | Resolve Issues | Review the issues report periodically to make sure none of the development or test tasks are blocked. Work with the team member to determine what can be done to unblock them. Review project risks periodically to make sure none are going to become showstoppers.
# Exit Criteria
| Priority changes have been communicated.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |