Why?
- The team holds the meeting to demonstrate a working product increment.
- The functionality should be reviewed with the Product Owner throughout the iteration and not only in the iteration review sessions to ensure that expectations are aligned.
- After the demonstration, the Product Owners reviews the commitments made at the Iteration Planning Meeting and declares which items are considered done.
- Incomplete items are added to the product backlog and reprioritised against other items.
- It is an opportunity to get the end users involved and iteratively refine everyone’s understanding of the requirement.
When?
- At end of an Iteration.
- Maximum one hour per week of Iteration length.
Who?
- Team Lead – Facilitates
- Product Owner
- Project Manager
- Business Analyst – Facilitates demonstrating product increment and sign-off
- Developer
- Tester
- Relevant Stakeholders
- Country Stakeholders
Inputs:
- Completed working functionality from iteration.
- Refined product backlog
- Iteration commitment
Outputs:
- Updated product backlog
- Updated product/release burnup chart
- Goal for next Iteration
- Feedback to discuss retrospectives.
Business Analyst Involvement:
- Demonstrates working product increment to Product Owner and other relevant stakeholders.
- Obtain sign-off for working product.
- Add any additional user stories from session to product backlog .
BA Agile Framework 