Exercise "Sprint Retrospective"
Summary¶
Here you will find the definitions of the most important terms from this chapter.
Sprint Retrospective¶
The Sprint Retrospective provides Developers with the opportunity to analyse and improve processes and workflows from the previous Sprint. It usually takes place after the Sprint Review.
Lessons learned¶
Lessons learned refers to the process of documenting experiences, findings and mistakes during a project. These lessons are analysed after each major milestone, but at the latest at the end of the project, in order to gain valuable insights that can be used in future projects or project phases to achieve improvements in planning, execution and results.
Plus-Delta method¶
The Plus-Delta method is a retrospective technique applied after completing a project or a specific period. Team members reflect on the positive aspects (Plus) and areas for improvement (Delta). This helps solidify the experiences from the project and optimise future projects or phases. The Plus-Delta method is also suitable for enhancing the effectiveness of the Sprint retrospective at the end of each Scrum Sprint.
Test yourself¶
Try to answer the following questions on your own. Take your time and think carefully before checking the solutions.
When does the Sprint Retrospective take place?
The Sprint Retrospective takes place after the Sprint Review and before the start of the new Sprint. The Sprint Retrospective marks the end of a Sprint.
Who convenes the Sprint Retrospective?
Just like the Sprint Review, the Sprint Retrospective is convened by the Scrum Master. They are responsible for ensuring that the Sprint Retrospective takes place and that all Developers and the Product Owner are informed.
What is the focus of the Sprint Retrospective?
The Sprint Retrospective focuses on the way of working. It is the Developers' turn at this point to give feedback on the Sprint.
What is the primary purpose of the Sprint Retrospective?
It is primarily used by the Developers to improve productivity and processes, but the entire Scrum Team can benefit from the Sprint Retrospective as well.
Under what circumstances may a Developer be directly criticised in the Sprint Retrospective?
No individual may be directly criticised or praised during the Sprint Retrospective. The team of Developers is in focus and should get feedback as a team.
What questions should the Developers ask themselves?
- What went well during the Sprint?
- What went not so well during the Sprint?
- How can we improve?
Why should the Sprint Retrospective not be skipped?
Skipping the Sprint Retrospective would mean that the project is not a continuous Scrum project, and the Scrum Team would miss the opportunity to improve the Developers' qualifications. With each Sprint Retrospective, the Developers have the opportunity to reflect on the previous Sprint and to work out what went well and what went not so well. In this way, they can improve themselves and increase the quality of the project Sprint by Sprint.
What is the maximum length of the Sprint Retrospective?
The Sprint Retrospective may last a maximum of 3 hours.