Skip to main content

MSF for Agile Software Development

Go Search
Home
  
MSF for Agile Software Development > Wiki Pages > WorkDefinition - Guide Iteration  

WorkDefinition - Guide Iteration

WorkDefinition Information

Guide Iteration

Description

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. The 'issue' flag on a work item allows work items that are blocked to be registered in the issues query. The issues query 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.

Mitigate a RiskConduct RetrospectiveMonitor Iteration

Attributes

When
At the start of each iteration
Exit Criteria
The iteration is completed and retrospective feedback, when necessary, has been incorporated.

Inputs and Outputs

WorkProductInputOutputAllowable States
Bug(none)
Quality of Service Requirement(none)
Risk(none)
Scenario(none)
Task(none)

Predecessors

TypeNameDependency Type
Plan an IterationFinish-Start

Last modified at 12/10/2007 3:34 PM  by Administrator