The Chaos Report
The CHAOS Report (1994)
The Standish Group
Slides preparados por Miguel Mira da Silva com base no resumo do relatório disponível na Internet http://www.standishgroup.com/sample_research/chaos_1994_1.php
The CHAOS report (1994) 1
Introduction
• Bridges are normally built on-time, on-dudget, and do not fall down.
– Because the design in frozen
• Software never comes on-time or on-budget, and always breaks down
– A frozen design does not accommodate changes in the business practices – 3,000 years of experience – Failures are covered up, ignored and/or rationalized
• We keep making the same mistakes over and over again!
The CHAOS report (1994)
2
Introduction
• Focus of this research
– Scope of software project failures – Major factors that cause software projects to fail – Key ingredients that can reduce project failures
• The US spends $250+ billion each year on softare
– Software development projects are in chaos – 31,1% of projects will be cancelled before they ever get completed
• Lost opportunity costs!
– The new Denver airport is costing the city $1.1 million per day (failure to produce software to handle baggage)
The CHAOS report (1994) 3
Introduction
• The hard data!
– In 1995, the US will:
• Spend $81 billion in cancelled projects • Pay an additional $59 billion for projects that will be completed but will exceed their original time estimates • Many of these projects are mundane!
– Success side:
• Only 16,2% of the software development projects are completed on-time and on-budget - 9% in large companies • Projects completed have only 42% of the original requirements
– There are more failures now than just five years ago
• It’s not getting better!
The CHAOS report (1994) 4
Methodology
• Survey
– The respondents were IT executive managers
• Ñot business users!
– 365 respondents
• Projects were classified into 3 types:
– Type 1 “Success” – on-time, on-budget, all features as initially specified
The Standish Group
Slides preparados por Miguel Mira da Silva com base no resumo do relatório disponível na Internet http://www.standishgroup.com/sample_research/chaos_1994_1.php
The CHAOS report (1994) 1
Introduction
• Bridges are normally built on-time, on-dudget, and do not fall down.
– Because the design in frozen
• Software never comes on-time or on-budget, and always breaks down
– A frozen design does not accommodate changes in the business practices – 3,000 years of experience – Failures are covered up, ignored and/or rationalized
• We keep making the same mistakes over and over again!
The CHAOS report (1994)
2
Introduction
• Focus of this research
– Scope of software project failures – Major factors that cause software projects to fail – Key ingredients that can reduce project failures
• The US spends $250+ billion each year on softare
– Software development projects are in chaos – 31,1% of projects will be cancelled before they ever get completed
• Lost opportunity costs!
– The new Denver airport is costing the city $1.1 million per day (failure to produce software to handle baggage)
The CHAOS report (1994) 3
Introduction
• The hard data!
– In 1995, the US will:
• Spend $81 billion in cancelled projects • Pay an additional $59 billion for projects that will be completed but will exceed their original time estimates • Many of these projects are mundane!
– Success side:
• Only 16,2% of the software development projects are completed on-time and on-budget - 9% in large companies • Projects completed have only 42% of the original requirements
– There are more failures now than just five years ago
• It’s not getting better!
The CHAOS report (1994) 4
Methodology
• Survey
– The respondents were IT executive managers
• Ñot business users!
– 365 respondents
• Projects were classified into 3 types:
– Type 1 “Success” – on-time, on-budget, all features as initially specified