- A feature should not be demonstrated in the Sprint Review if it doesn’t meet the Definition of Done (DoD).
- Always explain the context around the features to be demonstrated to have everyone on the same page.
- The Product Owner accepts only those features which were agreed at the start of a Sprint and met the Acceptance criteria.
- The Product Owner decides whether the features demonstrated in the Sprint Review are ready for release or need more work on it to bring it to the release-ready standard.
- The preparation time for the Sprint Review must not be long. Team can have a quick planning session and identify what to demonstrate.
- Sprint Review is a primary platform to collaborate and understand the progress of the software. The constructive feedback is always welcome.
- Stakeholders can provide a valuable feedback in the Sprint review sessions.
- The Sprint Review session involves demonstration of the features, discussing acceptance criteria, to elicit feedback and what could be the implications on the future Product Backlog Items (PBIs).
- The features should be presented as a Team achievement rather than an individual. Encourage Team Work.
Follow and Like us:
Agile Scrum – Sprint Review Facts
No comments:
Post a Comment