Task: Iteration Review Meeting |  |

Each iteration concludes with a Iteration Review where the team demonstrates a solution increment.
Disciplines: project management, Risk management

Relationships

Roles

Primary Performer:

- Customer
- Developer
- Product Owner
- Solution Architect

Additional Performers:

Inputs

Mandatory:

- Solution

Optional:

- None

Outputs

- Backlog Item
- product backlog

Main Description

At the end of each sprint a iteration review meeting is held. During this meeting the Scrum team shows what they accomplished during the iteration. Typically this takes the form of a demo of the new features.
Participants in the iteration review typically include the Product Owner, the team, management, customers, and engineers from other projects.
During the iteration review the project is assessed against the iteration goal determined during the iteration planning meeting. Ideally the team has completed each product backlog item brought into the iteration, but it is more important that they achieve the overall goal of the iteration.

Key Considerations

The iteration review meeting is intentionally kept very informal, typically with rules forbidding the use of PowerPoint slides and allowing no more than two hours of preparation time for the meeting. A iteration review meeting should not become a distraction or significant detour for the team; rather, it should be a natural result of the iteration.