Download as PDF, PPTX
Uploaded byMarc Löffler
Ale2012 retrospective
The document discusses ways to make retrospectives for agile software development teams more engaging and effective. It suggests adding hypotheses to retrospectives to give them more purpose and focus. Various metaphor-based retrospective formats are presented, like using soccer or cooking terms, to help teams think differently. The key ideas are that retrospectives need purpose and new perspectives to avoid repetition and keep people motivated to work on identified issues.
More Related Content
Similar to Ale2012 retrospective
![Xdde15 the art of facilitating retrospectives [and other team meetings]](https://cdn.slidesharecdn.com/ss_thumbnails/xdde15-theartoffacilitatingretrospectivesandotherteammeetings-151203192013-lva1-app6892-thumbnail.jpg?width=640&height=640&fit=bounds)
Ale2012 retrospective
- 1. Spice Up Your Retrospective (MarcLöffler, @scrumphony)
- 2. What do youexpect to take home from this session?
- 3.
- 4. Motivate people and keep them engaged
- 5. Work on identified tasks
- 6. What prevents them? • Repetition Boring Retros • Same problems No effect • No responsibility • Tasks are not visible • Tasks are too big
- 7. Two root causes •Missing Relativeness • Missing Purpose
- 8. Two root causes •Missing Relativeness • Missing Purpose
- 10. „The object towardwhich one strives or for which something exists; an aim or a goal”
- 11.
- 12. You can‘t fakepurpose!
- 13. Why is itmissing?
- 14.
- 15.
- 16. Inject purpose into retrospectives
- 17.
- 18. Add hypotheses toyour retrospectives
- 19. Set the Stage Gather Data Traditional Generate retrospective Insight flow Decide What To Do Closing (Esther Derby & Diana Larsen)
- 20.
- 22. The power ofmetaphors
- 23.
- 24. What soccer terms come into your mind?
- 25. • Imagine yourlast sprint was a soccer match of 90 minutes • Create a live ticker of this match • Only use soccer terms • Check your hypotheses from last time
- 26. Next steps… • GameAnalysis • Prepare for the next match including to define testable(!) new testable(!) hypotheses
- 27.
- 28. What‘s your recipe for a perfect sprint?
- 29. Why do you think this recipe will create the perfect sprint? (Hypotheses)
- 30. What steps or ingredients weremissing in your last sprint?
- 31. Two metaphor tips… • Create a list of metaphor terms before you start • Don‘t leave your metaphor!
- 32. Possible benefits ofusing metaphors • Think outside of the box • New, creative ideas Fun!
- 33.
- 34. Retrospective Cookies retrospectivecookies.com
- 36.
- 37. Summary • Any retrospectivewithout a purpose is a dead retrospective. • Add hypotheses to your retrospectives. • Play around with metaphors for new ideas.
- 38. What about your hypotheses?
- 39. Thanks for your attention
- 40. Contact Marc Löffler Email: marc.loeffler@spoonique.de Web:http://blog.scrumphony.com Twitter: @scrumphony
- 41.