Skip to main content

When should you apply Scrum?

... and when not? I was really surprised to discover it is not easy to find an answer this question. Let's look at what Scrum is, then look at when Scrum is appropriate and when not.

What is Scrum?

Scrum is a simple, team-based framework for solving complex problems. Scrum is modelled on successful patterns for product development as identified in "The New New Product Development Game". I would summarize these patterns as follows:

  1. Inspect and Adapt at regular intervals
  2. Produce something that might be valuable for your customer at regular intervals
  3. One voice speaks for the customer
  4. An interdisciplinary team solves the whole problem
  5. A coach helps everybody involved to get better
  6. Management provides direction and support, and knows when it's best to stay out of the way
How is scrum different than traditional approaches? The principles of traditional management might be summarized as follows:
  1. Define a plan, follow the plan
  2. Check progress against milestones
  3. Maximize utilization of resources
  4. Managers, customers or stakeholders make key decisions
  5. Well-defined processes, carefully followed, ensure predictable results.
  6. Optimization should improve the efficiency of a process

When does Scrum make sense?

Scrum was created for solving complex problems. What is a complex problem? If you can't know the answer before you start, it's a complex problem. You may not even be sure you are asking the right question! What is the right feature set for this product? Will this product meet the needs of the market? Sure, you can answer these questions in advance, but only through validation do you know if you have gotten the right answer.

Scrum is a team-based framework. It's about people. Scrum works well when people want to do it.  

What happens when the people don't want to do Scrum? It doesn't work very well. Scrum does not lend itself to being imposed from above. You can do it, but you create huge internal resistance. A good Scrum implementation, even if top-level management wants it too, is pulled from below. 

When does classical management make sense?

Some people would say the answer to this is never. But I think it is more complicated than that.  The patterns of classical management, which was invented by the automobile industry at the beginning of the 20th century, were hugely successful. They are the foundations of most large enterprises, and even today, as Agile methods have made development projects much more successful, an increasing percentage of the wealth generated by society stays in hands of top layers of classical management. This is also a definition of success!

So when do the patterns of classical management make sense?

The key word is predictability. If you can define a process with known inputs that produce the desired outputs, it is probably economically advantageous to do so. This works well for production problems, but is not well aligned with the needs of creative tasks like product innovation.

Should you use Scrum?

I would encourage you to use Scrum (or another empirical process) for unpredictable contexts:
  • Your main objective is some kind of problem solving.
  • Multiple skill sets are needed to solve the problem ("a team")  
  • Validation from customers or stakeholders is important to getting the right answer 
  • The people involved want to do it. (I often get called in to help people decide they want to do it).
I would encourage you to use a defined process for more predictable contexts:
  • A known input can lead to a predictable output
  • The problem and the solution can be clearly defined
I would encourage you not to do Scrum if the people involved do not want to do it. 

Having said that, if you ask people for examples from their own experience of great projects they'd like to emulate moving forward, these projects often look a lot like Scrum. If you ask people how they would like to organize their work, they often come up with something that looks a lot like Scrum!
    Lastly, I would also encourage you to challenge whether the tasks that you think belong to the predictable group really do belong there! 


      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…