Retrospective 1
Download as PPTX, PDF0 likes538 views
The document outlines how to conduct a retrospective at the end of a sprint to help a Scrum team improve. It recommends that teams take time to reflect on what went well and not so well in the previous sprint, and identify one or two commitments for improvement in the next sprint. The retrospective process involves individuals answering three key questions, sharing notes, group discussion, and identifying action items. Useful discussion questions are also provided to help teams understand different perspectives.
Retrospective 1
- 2. The goal of a Retrospective • No matter how good a Scrum team is, there is always opportunity to improve. • The team should set aside a brief, dedicated period at the end of each sprint to deliberately reflect on how they are doing and to find ways to improve. • The retrospective supports team formation and bonding, particularly as any areas of conflict can be identified and dealt with. • There are many different ways to run a retrospective.
- 3. 3 key retrospective questions What should we continue doing in the next sprint? What went well? What should we stop doing in the next sprint? What went not so well? What should we start doing in the next sprint? What can we improve?
- 4. Plan 1. Individually answer the 3 key questions (10minutes) 2. Individually bring the notes at the whiteboard (10 minutes) 3. Group discussion and prioritization (10 minutes) 4. Identification of actionable commitments (2 commitments max) (10) 5. Conclusions
- 5. Usefull Questions • Why did you do it like this? • Why did this (or didn’t this) work for you? • Why do you consider something to be important? • Why do you feel this way? • Why did you decide to work together on this?
Editor's Notes
- #4: Questions and UNDERLYING questions