Scrum Pattern: Sprint Review

 

  
ContextThe Development Team has finished a Sprint.
ProblemWhat is the best way to check if the Product Backlog Items of the Sprint Backlog have been implemented?
Forcestoo little/too much reporting
too little/too much effort for informal acceptance
SolutionEstablish a Sprint Review Meeting.

The main purpose of the Sprint Review Meeting is to find out, which Product Backlog Items (PBIs) have been successfully implemented. The User Story format for PBIs includes acceptance criteria which work as a checklist for the Development Team and Product Owner to check, if a PBI has been done which where undone work is left and needs to be addressed. Furthermore the impact of the Sprint on the Release Plan is discussed.

Resulting ContextThe Sprint Result has been accepted by the Product Owner and the Development Team is ready for the next Sprint.

Comments are closed.