Scrum Alliance pitch
“Retrospectives are great … except when they’re not. Without care and attention, retrospectives become stale, boring, and ineffective. And this is especially likely with distributed teams, where it is easy to put yourself on mute and start answering email instead of focusing on your team. In this Collaboration at Scale webinar, we’ll explore how you can keep retrospectives fresh, engaging, and impactful. We’ll focus especially on helping distributed teams identify the frameworks that allow them to explore different ways they can improve performance.“
Interestingly I was asked about getting feedback from the pilots and was wondering if there anything I can learn.
Scrum centric with more than 10 teams. Interactive webinar.
Ben Linders (consulting coach) Shahzad Zafer (internal coach)
Laura Richardson (sales, management)
Conteneo is co-presenter.
My version: cas_webinar_03082017.pdf
From the poll questions:
Summary we do it a lot, but not always effective. Therefore need to understand:
Coaching questions to drive conversation about improving retrospectives:
Why are retrospectives less than effective?
Who should attend
How do we keep retrospectives fresh?
The key is variation
Three key tips for distributed teams
Just because you have distributed people it does not mean you cannot do an exercise Use the same thinking for distributed teams as well and adapt to being distributed Vary exercise, environment, goal
How to deal with problems that team cannot deal with alone? Create large / multi team retro Note this can be another reason that retros become stale
Add to the backlog (for the items that are bigger) For smaller items need to make it visible Don’t create the secret backlog Make the actions visible
Make results of actions visible
How do you deal with dependent teams? Make that the goal of the retrospective and pull in people to participate
How do you deal with technical retrospective issues? Perhaps make it a hack-a-thon to be the retrospective