Skip to main content

What is Scrum?

Xing just opened up an agile forum in their German Speaking Project Management Group. Some 30'000 members. First topic of discussion: Is agile mainstream? Before they could answer that question, they needed to ask, what is agile, what is Scrum? So here, in ten points or less, what is Scrum:
  1. use good people
  2. play by simple and clear playing rules
  3. develop in small increments
  4. measure progress exclusively in terms of finished functionality
  5. have a clear definition of 'done'
  6. enable direct communication between customer and developer
  7. have a defined rhythm of planing, doing and evaluating
  8. remove impediments ASAP as they arise
  9. assure continuous improvement through regular retrospectives
Sounds simple, doesn't it? People will try to tell you they've been doing just that for years.

But they haven't. Scrum is radical, it's so different that only companies who are facing serious pressure will really embrace Scrum.

Many companies will do it part way (and that's OK - they'll get some of the advantages, if they do enough of it), but innovative companies with visionary thinkers or in those pressure situations will be the companies who really profit from Scrum: the start-ups, the project rescues (my trial by fire) and the companies facing enough competitive pressure or structural change that it really hurts. These will be the full adopters who get the full value from scrum.

There's more to it than that, of course, but this should help you get started.

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…

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 …