Sprint Retrospective

• Inspect and adapt the way the Scrum Team works
• Characteristics
  • Participants: Scrum Team
  • Time-box: maximum of 3 hours for a 1-month Sprint. For shorter Sprints, is usually shorter
  • Structure:
    • Inspected elements often vary with the domain of work
    • inspects how last Sprint went with regards to individuals, interactions, processes, tools, and their DoD (DoW)
    • discusses what went well during the Sprint, what problems it encountered, and how those problems were (or were not) solved
    • identifies the most helpful changes to improve its effectiveness
    • most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint
  • Purpose:
    • plan ways to increase quality and effectiveness
• Models
  • Example 1
    • Timeline significant events, continue doing, Start doing, Stop doing, shout-outs
  • Example 2
    • Went well, didn’t go well, ideas for improvement
• 11 Ideas to Spice up Your Retrospective
  • The Feedback Game
  • Discuss the Team's Purpose
  • The Constellation Game
  • Why Retrospectives?
  • Expectations
  • Writing the Unspeakable
  • Remember the Future
  • Circle of Influence & Concern
  • Follow Through
  • Choose a Different Location
  • Ask Someone Else to Facilitate the Retrospective