Skip to main content

Reflection on my MasterClass on Scrum Performance

Last Thursday, I held my first MasterClass Workshop in my new training facility "zum Talgarten". The topic was Scrum Performance and the target audience was people who have been doing Scrum for a while yet feel the need to get better. Three people attended (in German, they say "klein aber fein!"), a Product Owner and ScrumMaster from one company, the former ScrumMaster from another.

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:

  1. Identify reasons and goals for attending this workshop.
  2. 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).
  3. Share and discuss your Scrum with the other participants
  4. Reflect on how you and Scrum have failed each other
  5. Review how Scrum-by-the book works, and why
  6. Create a Vision of how Scrum should be in your organization
  7. 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.

Comments

Markus Rohrbach said…
Hello Peter

The workshop was a great refresher and an idea-/information exchange platform, to learn, how scrum adaptations were successfully and which were not successfully made in other companies.
Furthermore how/when a tailoring of the scrum process from the book is recommended or when you better leave it.

It gave me an outlook what I can and must make better or in a different manner for my next scrum project.

Thank you again and I wish you great success in the coming workshops.
Markus
Peter said…
Hi Markus,

Thank you kindly for this warm recommendation!

Best,
Peter

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …