Skip to main content

Standish Chaos reports miss the point

The Standish Chaos report of 1995 is probably the most cited work on project success and failure. The latest incarnation is quoted as saying:
  • 32% of all projects succeed
  • 44% of all projects were challenged
  • 24% of all projects failed
where succeeded means 'delivered planned scope on time and on budget'. Scope, Time and Budget are the classic legs of the 'Iron Triangle' ('What about Quality?' 'We don't talk about quality, that's a given.' 'Right.') which every project leader is taught is the holy grail of a successful project. But is that really success?

I teach my Scrum students about 5 perspectives on success, depending on who you are:
  • As a developer: success is fun and learning. A good working climate and personal development.
  • As a PL: satisfy the constraints of the Iron Triangle
  • As the line manager: business units are happy - line management gets to deal with escalations. (Or for a programming shop: the salesperson who is happy when the customers are happy).
  • As the user: "the product helps me do important things better and easier than before. I am thrilled and want to use the product."
  • As the investor/sponsor/paying customer: a good ROI (however defined
Which of these is most underrated? My vote: Fun and Learning. For the reasons why, check out this video from or Dan Pink's talk about motivating people.

Which of these is most overrated? My vote: Satisfying the Iron Triangle. Why do I say this? So many participants in my Product Owner courses, when asked what was their worst professional disaster, responded 'We built the product, but no one wanted it. The whole effort in time and money was for nothing.' Focusing on the project leaders definition of success misses the user and sponsor's view of success completely.

Want your project to be a success?
  1. Figure out who your customers and users are. Make sure they will be thrilled with what you build.
  2. Figure what what the product should earn for the company and what it should cost.
  3. Assume it will produce half of what you estimate and cost twice as much. Is it still profitable? If not, think twice about doing the project.
  4. Figure out what is the minimum set of functionality to get your customers excited about your product. Build that (more or less - you are probably going to learn more about/from your customers and your product along the way, which will change your understanding of what you need to build)
  5. Stay focused on delivering value to your customer. Do Scrum.
Did I say 'Do Scrum?' Yep Scrum helps you do all the rest.


Dave Rooney said…

I agree that the criteria used by Standish are somewhat archaic, but the Success/Challenged/Failure Rates are only part of the CHAOS Reports.

What I find much more useful is their weighted Top 10 list of success factors. An example of this, from the 2004 report, can be found on the InfoQ site.

That list matches much more closely with the criteria for success that you've observed (and mine as well, for that matter!).

Dave Rooney
The Agile Consortium
PM Hut said…

You can see how project success evolved from 1994 to 2009 in this CHAOS Report.

Things are definitely looking better, success rate has doubled...

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …