Embed Size (px)
DESCRIPTION
The retrospective is the important meeting within an agile process. This is the meeting were change is starting, but on the same hand this meeting gets boring very fast. Here are some ideas to spice up the retro.
Citation preview
How to spice up your retrospective
Bringing back the fun to change
Why
What if the team is bored by retrospectives?
What if the changes you detect are the same over and over again?
What if that changes are not be followed up?
What if
Restrospectives are fun and are the main source for small or big changes and improvement?
Ideal
Retrospective is the most important meeting during the scrum process.
It brings with every meeting small or big changes to improve the process continuously.
How
boring, useless happy, fun, yeah!
Well
1. Ask the team2. Try it out3. Listen to the team
Example 1 - The shipWhat was the “wind” in your sails during the sprint?
What was the “heavy load” during the sprint?
What was the “anchor” during the sprint?
Example 2 - Sweets
- Sweets are combined to open questions- Colour of sweets are a channel to Like, Don’t Like, Improvements
Example 3 - Fortune Cookie“Knowing these two immovable facts, I came to one simple conclusion: GREAT retrospectives should put food and questions front and center.”
Adam Weisbart
Example 4 - LivetickerOutcome - Tickermeldungen, wie z.B.
„Wir hatten zwei späte Tore in der 88′ und 89′ Minute“ (Fertig gestellte Stories)
„Ab der 67‘ Minute mussten wir mit 9 Spieler auskommen“
„In der 55‘ Minute gab es ein böses Foul“ (z.B. weil der PO mit neuen Anforderungen um die Ecke kam)
Example 5 - Where to we stand?
Conclusion
Balance between fun and hard work to detect useful changes.
Fun vs. Routine
Links
Fußball-Retro:
http://spoonique.de/2012/04/27/die-fusball-retrospektive/
Beispiele für Retros: http://blog.sybit.de/2012/06/agile-breakfast-retrospective/
Fortune Cookies Retro:
http://weisbart.com/cookies
