Skip to main content

Scrum is simple to understand but difficult to master(?)

According to the Scrum Guide, "Scrum is... Simple to understand, Difficult to master."


I have never agreed with this statement. Scrum is easy. I can explain it in 5 or 6 sentences. If you agree with the basic principles and design decisions, Scrum makes sense and is very easy to follow.

However, most organizations are not structured around these principles. Scrum therefore implies changes in how people work, and those changes are really hard for most organizations:
  1. Deliver something of value at least once per month. Many developers and teams are not capable of doing this, and have to learn a lot of new skills. Their organizations are structured around not doing this. Changing this is hard.
  2. A team solves the whole problem (from idea to done). This implies feature-teams, but most organizations are organized as component teams, so this implies a reorganization. This is hard.
  3. One voice speaks for the customer. The means decision-making about the product is delegated into the team. This fundamentally changes the conversations with the team, from commanding to discussing; from tell to consult, advise and agree; from about what to do to about why and how to do it. This implies rethinking how leadership works, and this is hard.
  4. A coach helps everybody get better. This introduces a new role whose value is barely understood to serve people whose value is massively underestimated.
  5. Inspect and adapt at regular intervals: this means examining yourself and changing. Inspecting may lead to recognitions that are not consistent with your self-image. When the team discovers something that needs outside help to fix, management is expected to make it happen. Who is now telling whom what to do? This implies taking priority requests from people you used to give orders to. Lots of things about adapting can be hard to do.
I think the challenge of doing great things with Scrum is reflected in “the first impediment”: not having a Scrum Team with the skills and authority necessary to be a Scrum team. The PO can’t decide. The Team is not cross functional nor does it own their time or infrastructure. The Scrum Master does not have time or access to management to make improvements happen. Fail before you begin.

If you want to get off to a good start with Scrum in your organization, get your management involved to fix or prevent the first impediment! Get the roles right. I believe if you do that, everything else is much easier.


Comments

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…

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…

What is the role of a Business Analyst in Scrum?

When I teach a CSM class, my goal is that my participants go home delighted (and of course that they learn about Scrum, that they are motivated to do Scrum, and can pass the online CSM exam). So after every class, I ask for feedback, in particular what could I do to get a better score. And for the next class, I strive to implement or address two or three of the points raised by my participants.

One issue that was raised was unanswered questions. It is annoying to ask questions and not get answers! Time is limited, so it is not always possible to answer all questions, so I thought, why not answer them on my blog? So here goes, first question:
What is the role of a Business Analyst in Scrum? This question is a challenge because Scrum doesn't answer this question! Scrum is a simple, team-based framework for solving complex problems. The roles and ceremonies in Scrum are designed to ensure that inspect and adapt can occur regularly with complete and correct information. Scrum does not…