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

Project Portal
| See Also Plan an Iteration |
| Guide Iteration Project Manager
|  | Participating Roles Responsible: Project Manager
### Overview Once an iteration begins, it is important to stay on top of issues. When an issue arises, the speed with which it is dealt with can have an impact on the velocity. Issues flagged on a work item allow work items that are blocked to be registered in the issues report. The issues report should be run each morning at a minimum. When an iteration is completed, retrospectives should be conducted to determine ways to improve the process and environment. A retrospective meeting should be held to bring closure on the iteration, the same way that an iteration planning meeting starts one. # Entry Criteria When: At the start of each iteration # Activities
1 | Monitor Iteration | Review work item priorities. Resolve issues.
2 | Conduct Retrospective | Set up the retrospective. Hold iteration retrospective meeting. Incorporate feedback into the next iteration.
# Exit Criteria
| The iteration is completed and retrospective feedback, when necessary, has been incorporated.
(C) 2005 Microsoft Corporation. All rights reserved. Build 97 |