Sprint review

Sprint review

Attendees
Required: development team, scrum master, product owner
Optional: project stakeholders
When: At the end of a sprint or milestone.
Duration: 30-60 minutes.
Agile Framework: Scrum and kanban. Like planning, review for kanban teams should be aligned with team milestones rather than on a fixed cadence.
Purpose: Iteration review is a time to showcase the work of the team. They can be in a casual format like "demo Fridays", or in a more formal meeting structure. This is the time for the team to celebrate their accomplishments, demonstrate work finished within the iteration, and get immediate feedback from project stakeholders. Remember, work should be fully demonstrable and meet the team's quality bar to be considered complete and ready to showcase in the review. 

Comments

Popular posts from this blog

Agile Bug Triage Meeting

Release Planning in Agile

Scrum Framework ( Scrum Methods)