Skip to main content

10 Myths about Scrum

I recently introduced Sharon Bowman's Myth or Fact exercise to my Scrum courses - it has proven to be very a popular way to explore Scrum. Last week in Brussels, we took it a step further - I asked the participants to identify their Myths around Scrum. Here is their list. What do you think, Myth or Fact?

  1. Scrum is easy to implement.
  2. Scrum helps you recognize problems
  3. If you do not apply Scrum 100%, you cannot be successful with Scrum.
  4. Scrum can only be applied for time-and-material projects.
  5. Scrum is only for team players
  6. Scrum will solve any problem
  7. Scrum is inflexible
  8. Scrum always works
  9. Scrum is a revolution
  10. Scrum gets easier over time
In my humble opinion, 1 is fact if everyone wants to implement it, 2 is a fact, 3 and 9 are debatable (and probably depend on your definition), and everything else is a myth. What do you think?

Comments

Philipp said…
Hi Peter

Like everything else we are getting better while practicing. So number 10 is surely a fact to me. The more we use it the easier it will become to organize and orchestorate our products with the ideas of scrum.

BR, Philipp

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…

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 …