Exercises "Sprint Review"
Here you will find the definitions of the most important terms from this chapter.
Joint meeting to review the Sprint results and identify future changes. The Scrum Team presents the work done to key stakeholders and progress towards the Product Goal is discussed.
Acceptance criteria must be defined for user stories and other PBIs, on the basis of which it can be assessed after Sprint completion whether the corresponding PBI can be accepted or not.
A technical debt exists when a user story is not perfectly implemented and the Developers are aware that improvements will have to be made in the future. This is accepted when time is short. The growth of the technical debt with each new Increment increases the complexity of the product and reduces the Velocity.
Answer the following questions independently. Please take your time and think carefully about what you would answer before revealing the solution.
What is the purpose of the Sprint Review?
The purpose of the Sprint Review is to review the results of the Sprint and to determine future adjustments. The acceptance of the Increments takes place, it is checked whether the Sprint Goal has been achieved and the progress towards the Product Goal is discussed.
What is the responsibility of the Scrum Master prior to the Sprint Review?
The Scrum Master is responsible for planning and conducting the Sprint Review Meeting. In the course of this, he invites the Product Owner as well as everyone who is interested in attending the Sprint Review. Ideally, together with the invitation to the Sprint Review, he sends out a list of all the topics that will be discussed during the Sprint Review.
How does the presentation of the Increment look like?
The Increment, which is potentially deliverable, is presented and tested as such in a live demonstration. The presentation is therefore not theoretical, but practical. Questions about the Increment are explicitly welcome. The presentation will be done by the Developers.
Where does the Sprint Review take place?
The Sprint Review can be held in a variety of rooms. For example, it makes sense to hold the Sprint Review in a laboratory if the development work has also taken place in a laboratory. If the Developers have mainly worked in a particular office, the Sprint Review could also be held in that office.
What is the main task of the Product Owner during the Sprint Review?
The Product Owner is encouraged to test the Increment. It is important that the Product Owner actively participates in the Sprint Review and gives feedback. The Developers need the feedback to continuously improve in the upcoming Sprints.
What is a technical debt?
A technical debt is when a user story is not perfectly implemented and the Developers and the Product Owner are already aware at the time of acceptance that improvements will have to be made in the future. This is accepted when time is short. The growth of the technical debt with each new Increment increases the complexity of the product and reduces the Velocity.
When can an Increment be accepted?
Only when it is one hundred percent complete. A partial acceptance of an Increment is not possible.
How long does the Sprint Review take?
Maximum 1 hour per Sprint week.
Who takes part in the Sprint Review?
Scrum Team and stakeholders, customers if applicable.