Skip to main content

MasterClass Workshops: Taking Scrum to the Next Level

For years, I have been giving Scrum courses and workshops. These entry-level courses are, above all, eye openers! They introduce people to new ideas about how to organize work, and for some of you, a light goes on! You take Scrum back to your organization and start to do Scrum. Then reality sets in. Confronting the challenges of changing your organization is hard! Doing Scrum well is not easy. To help you overcome these obstacles, I created the MasterClass workshop series.

MasterClasses are about improving your understanding of Scrum.  MasterClasses complement Scrum with other important frameworks – especially Radical Management. MasterClasses are about working through real problems and finding real solutions. MasterClasses are about becoming Agile.

MasterClasses are one-day workshops, so it's easier to get away. I hold one every month, right after my monthly Intense Certified Scrum Master course. They repeat, so you can pick the date most convenient for you. And you can come by yourself, or in a small group, to work through problems together.

Most of them I teach myself, though I often invite renowned experts to lead individual workshops.

I am really excited about the first two MasterClasses. The first, Scrum Performance Workshop, is a combination Retrospective, Scrum refresher and problem solving session. I've integrated some ideas from Siraj Sirajuddin's Temenos Workshops, tested them at the Scrum Gathering in Atlanta, and the result is an intense, productive day to help your team get in the flow.

I'll tell you about the second workshop on Storytelling in a separate blog entry. In the mean time, here is a list of the coming MasterClasses:

I have a special introductory price for the first Scrum Performance Workshop and a surprise planned after work ;-). Check out registration for details...





Comments

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 …