What can we share from a retrospective?
We talk a lot about having a safe space for a retrospective, about creating that environment where it’s safe to open up and honestly talk about the real problems. We tell management that they should have no expectation of knowing about the specific conversations that went on inside a team’s retro, and that’s correct.
The facilitators role
If you’re facilitating the daily coordination meeting (standup, daily scrum, whatever you want to call it), and you’re doing all the talking, then you’re doing it wrong.
Constraints enable creativity
With retrospectives, we generally have specific formats that we follow, rather than just pulling people together and expecting them to talk. This feels very counter-intuitive for many; surely we don’t need rules or formats to get people to come up with creative ideas. Yet doing that will dramatically improve the results we get.
Six Thinking Hats Retrospective
Six Thinking Hats is an approach for creativity that was created by Edward DeBono. I use it as the basis for an agile retrospective, and find this approach to be particularly effective when the topic we’re discussing is expected to be controversial or heated.
Retrospective Magic
The content from this workshop has been expanded and turned into the video course Retrospective Magic.
Putting the Moose on the Table: A LEGO based retrospective
In order for teams to step into high performance. it’s critical that they develop the practice of having effective conversations about what is and isn’t working. Yet in practice, the retrospective meeting is often the least-valued of the agile events: team members feel that their retros are boring, repetitive, and superficial.