Statistics from the Famous 1995 Standish Group Report.

Slides:



Advertisements
Similar presentations
Transforming Healthcare in the US Virgin Islands….. Primary Healthcare.
Advertisements

Software Engineering of Standalone Programs Prof. Ruth Dameron, Course web site with course materials is under WebCT – Need an identikey.
The Chaos Report © The Standish Group 1995.
Terminology Successful Project: Completed on time and on budget, with all requirements implemented and the user community is generally happy with the.
“Influences on the project development and management success” Melita Sogomonjan ISPM IDU3390.
The Nature of Information Technology Projects
Information Technology Project Management – Fourth Edition
“Not Fully Specified (Project) Objectives” CS524 – Software Engineering I Azusa Pacific University Professor Dr. Sheldon X. Liang Fall I 2007 Ernie Rosales.
Risk Management Chapter 7.
8 September ProcessWithin the Steps  Put together minimal solution Start with external commitments Introduce internal milestones  Focus on the.
 The Rise of Computer Science ◦ Machine Language (1 st Gen) ◦ Assembly Language (2 nd Gen) ◦ Third Generation Languages (FORTRAN, BASIC, Java, C++, etc.)
9-Jun-15 GCIS 504/GENG 580- The requirements problem1.
1 How to Cause Information Technology Disasters William A. Yasnoff, MD, PhD Oregon Health Division.
Requirements Specifications Today: Homework #1 due For next class: Pressman 11; SRD Team Status Reports Requirements Process (continued) Bio Break ( 5.
The Analyst as a Project Manager
SOFTWARE ENGINEERING II COMP319
Understanding Information Technology System Project Failure By: Michael Bury MIS
“80% of software projects fail”  Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features and functions as initially.
Chapter 1 The Nature of Information Technology Projects Copyright 2012 John Wiley & Sons, Inc. 1-1.
Information System Economics IT PROJECT MANAGEMENT.
Mark Dochtermann, PMP, CISSP Microsoft Corporation September 13, 2006 Project Management Performance.
(from Dr. Diane Pozeksky. “80% of software projects fail” Standish Report (1995) Standish Report 16.2% completed on-time and on-budget with all features.
Establishing a Best Practice Community It Takes a Village to Make a Successful Project Presented by Emily Iem, PMP, CBAP.
Reducing ITS Project Risk By using and developing consensus based regional ITS architecture and a systems engineering process Robert S. Jaffe, Ph.D., CSEP.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 IS Projects: Success and Failure Role of the Project Manager Project Management Tasks in SDLC.
Chapter 7: Project Cost Management Information Technology Project Management, Fourth Edition Cost Management Principles and Cost Estimating Tuesday, March.
Requirements Management with Use Cases Module 2: Introduction to RMUC Requirements Management with Use Cases Module 2: Introduction to RMUC.
Kelly J. Harris SEARCH Deputy Executive Director
June 2005 Coral Trisko, PMP Enterprise Project Management Ltd. Project Management... a step in the right direction!
Readjusting Project Dynamics for a Successful Outcome Dan Williams Director, Project Consulting April 2012.
MSF Overview (Microsoft Solutions Framework) Eran Kolber Vice President – LIH Ltd Regional Director – Microsoft Product Management Advisor – MSF Development.
VCU Information Systems Institute Advanced Delivery Methodology Courtesy of Data Management That Works.
PROJECT MANAGEMENT FUNDAMENTALS Page 2 Why Project Management? Current Issues: n Complex nature of business today — More cross-functional efforts — Need.
1 Requirements Management - General concepts - Noureddine Abbadeni King Saud University College of Computer and Information Sciences Based on “Software.
Introduction to Systems Analysis and Design
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
Rational Requirements Management with Use Cases v5.5 Copyright © Rational Software, all rights reserved 1 Requirements Management with Use Cases.
3 1 Project Success Factors u Project management important for success of system development project u 2000 Standish Group Study l Only 28% of system development.
Lecture 1 Title: Introduction to ITPM By: Mr Hashem Alaidaros MIS 434.
Failures, Successes And Identifying Best Practices For Higher Success of IT Projects CHINOYEREM DEBORAH OKOROAFOR CHIMA W. ORIJI
Presented By Beverley Sinclair Key Issues, Trends and Risks in IT Procurement.
Software Requirements and Design Khalid Ishaq
The Software Crisis A Report from 1979.
Agile – The Movement Chapter 1 “Agile”, the Movement from SDLC 3.0 Beyond a Tacit Understanding of Agile.
Project Management Lecturer : Behnam Faizabadi PhD,PMP 8/23/2011 Behnam Faizabadi PhD,PMP Project MGMT Consultant.
Telco Financial Analysis May, XXXX/ Gemini 12/6/ XXXX/Gemini CP/PD A&D - Confidential Approach Evaluated financial aspects of XXXX by.
MADALINA CROITORU Software Engineering week 3 Madalina Croitoru IUT Montpellier.
Copyright ⓒ 2005 SE Technology. Co.,Ltd. All rights reserved. What are the differences between the architectural description of large scale software development.
Chapter 1 The Requirements Problem
1 Systems Analysis and Design in a Changing World, Tuesday, January 23, 2007.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Project success = business success TM Introduction to Agility Agility is a comprehensive response to the business challenges of profiting from rapidly.
The Chaos Report A series of reports issued by The Standish Group, an industry analysis firm Classifies software projects into 3 classes: ̵ Successful:
Structuring An Effective Project Management Office and IT Governance David Stokes, PMP Jane Matthews, PMP Florida Department of Health Division of Information.
303KM, Introduction to Project Management1 Chapter 1: Introduction to Project Management.
 Overview of Project management. ◦ Management. ◦ Project Management. ◦ Software Project Management. ◦ Project(Dimensions, Characteristics, Complexity,
© 2006 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice What is the “Big Issue”? What causes.
What is a Functional Spec?  Defines what the functionality will be NOT how it will be implemented  Describes features of the software product product's.
Understanding Information Technology System Failure
The “Accidental” Project Manager
The Nature of Information Technology Projects
Project Management What is Project Management?
The Nature of Information Technology Projects
Introduction to Project Management
10 Steps to Better Requirements
ASEE Software Engineering Process Improvement Workshop HOT TOPIC, 2001
Projects: In the Beginning
Projects: In the Beginning
Technology Challenges and 10 Critical Success Factors
Andreas Altmannsberger Frank Bühler Mike Rowe
Presentation transcript:

Statistics from the Famous 1995 Standish Group Report

Survey 365 Companies (small, medium, large) Major Industry Segments (banking, health care, insurance, etc.) Software Applications

Failure Statistics Project Success - The project is completed on-time and on- budget, with all features and functions as initially specified Project Challenged - The project is completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. Project Impaired - The project is canceled at some point during the development cycle.

Failure Statistics Project Success - The project is completed on-time and on- budget, with all features and functions as initially specified Project Challenged - The project is completed and operational but over-budget, over the time estimate, and offers fewer features and functions than originally specified. Project Impaired - The project is canceled at some point during the development cycle. 16.2% 52.7% 31.1%

Restarts ?? out of 100 software projects must be restarted from scratch... sometimes MULTIPLE TIMES.

Restarts 94 out of 100 software projects must be restarted from scratch... sometimes MULTIPLE TIMES.

Cost Overruns Cost Overruns % of Responses Under 20% % % % % Over 400% The average across all companies is ???

Cost Overruns Cost Overruns % of Responses Under 20% 15.5% % 31.5% % 29.6% % 10.2% % 8.8% Over 400% 4.4% The average across all companies is 189%.

Time Overruns Time Overruns % of Responses Under 20% 13.9% % 18.3% % 20.0% % 35.5% % 11.2% Over 400% 1.1% For the same combined challenged and impaired projects, over one-third also experienced time overruns of 200 to 300%. The average overrun is 222% of the original time estimate.

Content Deficiencies % of Features/Functions % of Responses Less Than 25% 4.6% % 27.2% % 21.8% % 39.1% 100% 7.3% On average, only 61% of originally specified features and functions were available on these projects.

Costs (circa 1995) $250 billion spent on application development nationwide $81 billion wasted on cancelled projects Lost opportunity costs could be in the trillions

WHY?

Project Success Factors Hard-Working, Focused Staff Executive Management Support Clear Statement of Requirements Realistic Expectations Smaller Project Milestones Ownership Executive’s surveyed... what were key factors for success? Project Success Factors Competent Staff User Involvement Proper Planning Clear Vision & Objectives

Project Success Factors Project Success Factors % of Responses 1. User Involvement 15.9% 2. Executive Management Support 13.9% 3. Clear Statement of Requirements 13.0% 4. Proper Planning 9.6% 5. Realistic Expectations 8.2% 6. Smaller Project Milestones 7.7% 7. Competent Staff 7.2% 8. Ownership 5.3% 9. Clear Vision & Objectives 2.9% 10. Hard-Working, Focused Staff 2.4% Other 13.9% Executive’s surveyed... what were key factors for success?

Project Challenged Factors Executive’s surveyed... what were key factors for challenges? Project Challenged Factors Lack of User Input Incomplete Requirements & Specifications Technology Incompetence Lack of Resources Unclear Objectives Project Challenged Factors New Technology Changing Requirements & Specifications Unrealistic Expectations Unclear Objectives Unrealistic Time Frames Lack of Executive Support

Project Challenged Factors Executive’s surveyed... what were key factors for challenges? Project Challenged Factors % of Responses 1. Lack of User Input 12.8% 2. Incomplete Requirements & Specifications 12.3% 3. Changing Requirements & Specifications 11.8% 4. Lack of Executive Support 7.5% 5. Technology Incompetence 7.0% 6. Lack of Resources 6.4% 7. Unrealistic Expectations 5.9% 8. Unclear Objectives 5.3% 9. Unrealistic Time Frames 4.3% 10. New Technology 3.7% Other 23.0%

Project Impaired Factors Executive’s surveyed... what were key factors for impairment? Project Impaired Factors % of Responses 1. Incomplete Requirements 13.1% 2. Lack of User Involvement 12.4% 3. Lack of Resources 10.6% 4. Unrealistic Expectations 9.9% 5. Lack of Executive Support 9.3% 6. Changing Requirements & Specifications 8.7% 7. Lack of Planning 8.1% 8. Didn't Need It Any Longer 7.5% 9. Lack of IT Management 6.2% 10. Technology Illiteracy 4.3% Other 9.9%