Skip to main content

Scrumbut, or What could you omit from Scrum?

Jelle van Wieringen recently wrote on LinkedIn:
Next Monday in Mannheim, Germany we will discuss Scrumbut in our open monthly "Scrum Stammtisch". This months topic is the consequences of leaving out elementary elements of Scrum. I'd like to know what [people] think...
As perhaps the first person to ask people to take the Nokia test in public, I feel a little bit responsible for the creation of the term "ScrumBut." Is it OK to change Scrum? Certainly there are situations where necessary, and others where it's not OK (and probably some overlap between the two!), so here is my take on changing Scrum:

The core of Scrum is really very small. Inspect and Adapt. At regular intervals. Everything thing Scrum is designed to enable effective inspection and adaptation at regular intervals.

To me, Scrum represents a solution to the challenge of solving complex problems based on those simple principles. It's a reference implementation. You'll never do it exactly like it is in the book, but especially at the beginning, you should try to get as close as possible to the book.

As you get good at Scrum, your inspections and adaptations may take you away from the book. When is that OK?

I have two tests for good changes to Scrum:

  1. Does it cause you to inspect and adapt more often than Scrum-by-the-book? If yes, it's probably a good change. If not, then probably not. 
  2. Is your change the result of an agreement, either among the Scrum Team or between the Team and its stakeholders, to improve performance? If yes, it's probably a good change. If not, i.e. you are accommodating some endemic problem or inability to change, then you are probably being tempted by the Dark Side and should tread cautiously. 

I think (1) is a stronger, more reliable test than (2). And I think if (1) and (2) both pass, well that's a sign of impending Awesomeness!

What's you take? When is it OK to change Scrum? How do you check that the change is OK?

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…

Five Simple Questions To Determine If You Have the Agile Mindset

My company has started a top-down transition to Scrum and Kanban. Will that make us an Agile company? About 2 years ago, I attended a conference hosted by the Swiss Association for Quality on the topic of Agility. As a warm-up exercise, the participants were given the 4 values of the Agile Manifesto, then asked to arrange themselves in space. How Agile is your company? How Agile do you think it should be? Very Agile on left, very traditional on the right. There was a cluster of people standing well to the right of center. “Why are you standing on the right?” It turns out that they were all from the railway. “Our job is to run the trains on time.” They were uncertain whether this agility thing was really aligned with their purpose.
Is Agility limited to software? Steve Denning has collected the evidence and laid out the case that Agile is not limited to software, nor is it merely a process, nor is it something you can do with part of your time, nor is it something you can have your …