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.


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.
Peter said…
Hi Markus,

Thank you kindly for this warm recommendation!


Popular posts from this blog

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…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …

Money for Nothing, Changes for Free

“Money for Nothing, Changes for Free” encourages both customers and suppliers to focus on value.

A key advantage of Scrum projects is that at least once per sprint you have something that could be shipped and no work in progress. You can change direction every sprint, and you can reevaluate whether the project is a good investment or if your money could be better spent elsewhere. Abrupt cancellation is risky for the supplier.

While the concept of an early-exit penalty is not new, Jeff Sutherland gave it a unique allure with his allusion to the Dire Straits hit.
Desired Benefit Incentivize both customers and suppliers to focus on functionality that provides genuine value.
Structure This works with Agile software projects because there is little or no work in progress. After each Sprint, functionality is either complete or not started. Work is basically on a Time and Materials basis with a cost target, often with the intention that the project should not use up the entire project budge…