Get more out of your retrospectives
Get more out of your retrospectives
Join the DZone community and get the full member experience.
Join For Free[Latest Guide] Ship faster because you know more, not because you are rushing. Get actionable insights from 7 million commits and 85,000+ software engineers, to increase your team's velocity. Brought to you in partnership with GitPrime.
What I learned about retrospectives
- Change the format on a regular basis. One attendee switches things up every retrospective.
- You can get great results by focussing on more of what works. This is inspired by appreciative inquiry. We are so used to looking at what the problem is, that looking at success can have a powerful shift.
- Another was to have each person write a personal commitment story card for something to do in the next iteration. They signed the card and someone else agreed to pair with them on it to provide support. The cards were posted beside the scrum board as a reminder. They were reviewed at the start of the following retrospective.
- Liked-Lacked-LongedFor was also suggested as a powerful way to connect with people’s deeper selves.
Related posts:
- Team and pair games for building collaboration Tobias Mayer led a fun and effective session (Agile Playground)...
- Games and tough questions for Agile Adoption Luiz Claudio Parzianello and Rafael Prikladnicki gave a talk at...
- Constellation, Timeline and Marketplace for Tuning Teams Lyssa Adkins ran a very practical session at DeepAgile that...
- Play the Scrum Simulation (based on XPGame) for Great Learning This post describes a way to modify the XPGame to...
[Latest Guide] Ship faster because you know more, not because you are rushing. Get actionable insights from 7 million commits and 85,000+ software engineers, to increase your team's velocity. Brought to you in partnership with GitPrime.
Like This Article? Read More From DZone
Published at DZone with permission of Michael Sahota , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}