Retrospective
0 likes•852 views
The document presents an overview of sprint retrospectives, emphasizing the importance of collaborative team learning rather than individual feedback. It details a structured framework for improving retrospectives, including steps like setting the stage, gathering data, generating insights, and deciding on action items. Various retrospective formats and tools, such as the starfish method and the glad-sad-mad format, are suggested to enhance team engagement and effectiveness.
Retrospective
- 1. Retrospective Summary meeting at the sprint end Favara Vincenzo
- 2. About me Retrospective It allows team to learn, think and decide together It’s not the place to have individual feedback It’s not the answer to fill tech or collaboration skills gaps It should be unique https://www.scrum.org/resources/what-is-a-sprint-retrospective
- 3. Retrospective standard framework How can improve retrospective? Set the stage (establish its focus) Gather data (create a shared poll of data) Generate insights (understanding influences and causes) Decide what to do (action item) Close it (contributions and better ideas to next one) 1 2 3 4 5
- 4. Retrospective SMART Action Items How can improve retrospective items? Specific – what are you going to do and who? Measurable – how can you quantify progress? Achievable – can you actually accomplish this? Relevant – does it matter? will it fix the problem? Time Based – when will it be done? 1 2 3 4 5
- 5. How long? Maybe we need more than 2 hours
- 6. ● Scrum master do a little summary ● Team starts talking about posts ● Vote ● Create action items ● Close retrospective (feedback) ● Use a remote dashboard ● Scrum master in according with team decide first 2 points: focus and provide data ● Every team member should fill dashboard Meeting One hour Remote Half sprint time
- 7. Starfish What we are using! ● Start ● Stop ● Keep ● More ● Less Type: Verbal Number Members: 5+ Remotable: YES
- 8. Starfish Variants: Some used variants ● KALM: Keep, Add, Less, More ● DAKI: Drop, Add, Keep, Improve ● 4L’s: Liked, Learned, Lacked, Longer for Type: Verbal Number Members: 5+ Remotable: YES
- 9. Glad Sad Mad Simple and classic! Glad: What makes you happy Sad: What disappointed you or that you wished be improved? Mad: List of things that make you crazy and stop you from performing at your best? Type: Verbal Number Members: 3+ Remotable: YES
- 10. “Why” Retrospective Some used variants This meeting format is used to find issues causes asking follow up “why?” Each member create a chain of reasons due to which why and so on Type: Not-verbal Number Members: 7+ Remotable: YES mandatory
- 11. Token of appreciation Need chocolate box! “I would like to give a chocolate to X because he was nice in...“ Then you give the chocolate box to X and ask him to repeat the gesture Type: Verbal Number Members: 7+ Remotable: NO
- 12. Presentation Team can see the slide about topic Why Use anonymous dashboard Starfish Do we miss starfish? Let’s come back! Team on Fire We tried and tested, what we learned? The choose Which retrospective is the best for us? Appreciation buy some chocolate boxes!!!! Glad Sad Mad Emotional focused Retrospective plan How can we plan what we learn today?