Artikel versenden

Scrum Retrospectives


// / / / /

The retrospective is one of the key elements that Scrum prescribes. Retrospectives have a long history coming from japanese management tradition and are key element of the Toyota Production System. They are core for continuous process improvement. Retrospectives enable a team starting with Scrum to improve and adapt over time. There is no need to be right the first time, there is a need to become better and better. Retrospectives happen after an iteration, a Scrum Sprint. They take place directly after the Sprint Review, that concentrates on the results of the sprint (running system, documentation, tests). The focus of the retrospective is the process. The following composition gives some guidelines how to conduct a Scrum retrospective.

Facilitator: Scrum Master, invites to retrospective
Objective: Find process improvements, define concrete steps
Participants: Scrum Master, Team, Product Owner
Optional Participants: Invited persons (Management, …)
Timebox: 2 h
Rules: No fingerpointing, put issues honestly on the table

  1. Explain agenda, rules and objective of the meeting
  2. Check-In: Ask participants for their feelings or a picture when they think back the last Sprint
  3. Each Participant: Put positive topics with cards to the wall (3 per participants), explain them
  4. Whole team: Categorize found topics
  5. Vote (most important categories, cards), 3 votes for each participant
  6. Do steps 3 to 5 with negative topics
  7. Ask the 5 why’s for the most important Negatives
  8. Ask for improvements, put task cards or user stories into the next sprint with concrete actions
  9. Finish: Do Retrospective on retrospective
  10. Organizational Learning: Publish results of the retrospective to the management and other team


Quelle Foto: © Dark Vectorangel –

| Keine Kommentare

Top | Impressum | Datenschutz