The inspiration for this workshop came out of my workshop at the Scrum Gathering "Reinventing Scrum". I discovered none of the participants wanted to reinvent Scrum, they all wanted to debug their own Scrum implementations. And so the workshop was born.
The second piece of the puzzle came from the Temenos retreat I attended last summer. (Read more in the article on Deep Trust - a foundation for lasting change in your organization). A Temenos retreat goes through a process of reflecting and letting go of what happened, then creating personal and shared visions for the future. I set out to follow this model:
- Identify reasons and goals for attending this workshop.
- Draw of picture of your Scrum flow, showing how you really do "Scrum" (which may or may not be very close to how Scrum is actually defined).
- Share and discuss your Scrum with the other participants
- Reflect on how you and Scrum have failed each other
- Review how Scrum-by-the book works, and why
- Create a Vision of how Scrum should be in your organization
- Create a list of improvements to start implementing on Monday.
That was the idea. This proved to be too ambitious for a one day workshop, so I focused on achieving the participants goals. This is what I am now reflecting on — Stay with the one day format, or expand to two days?
How did the participants feel? They appreciated getting feedback on their current system, sharing practical experiences, the discussions with each other on their issues, and learning about various common patterns (e.g. "Snow White and the 7 Dwarfs") and how to solve them. (I'll be posting their quotable comments on the MasterClass announcement shortly). The Net Promotor Score was +67% (2 promoters, no detractors), and Erik Foneska agreed to a spontaneous video interview. Here is his recommendation:
The next public workshop is scheduled for December 6. I'm going to do it once more as a one day workshop. In the meantime, I'll consider whether it should become a two day workshop/retreat for next year.