What are the common reasons software development projects fail?

Slides:



Advertisements
Similar presentations
Project What is a project A temporary endeavor undertaken to create a unique product, service or result.
Advertisements

W5HH Principle As applied to Software Projects
Software project management Module 1 -Introduction to process management Teaching unit 1 – Introduction Ernesto Damiani Free University of Bozen-Bolzano.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Change Request Management
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Project Closeout and Termination Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Chapter 14 Learning Objectives After completing.
© 2005 Prentice Hall14-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
Before we start construction, let’s lay the groundwork.
INFO 637Lecture #31 Software Engineering Process II Launching & Strategy INFO 637 Glenn Booker.
Systems Analysis and Design in a Changing World, 6th Edition
Applied Software Project Management Andrew Stellman & Jennifer Greenehttp:// Applied Software Project Management Chapter 1: Introduction.
Software Project Management Introduction to Project Management.
Copyright © 2014 McGraw-Hill Higher Education. All rights reserved. CHAPTER 15 Project Management McGraw-Hill/Irwin.
Project Management : Techniques and Tools (60-499) Fall 2014 / Winter 2015.
Software Project Failure Software Project Failure Night Two, Part One CSCI 521 Software Project Management.
Developing Software MGMT Summer 2012 Night #8.
Chapter 3 Project Management Concepts
Computer Calamities The University of California Berkeley Extension Copyright © 2007 Patrick McDermott Field, Tom, “When Bad Things.
1 Chapter 3 Project Management. 2 Project Management Concerns staffing? cost estimation? project scheduling? project monitoring? other resources? customer.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
The Software Development Life Cycle: An Overview Presented by Maxwell Drew and Dan Kaiser Southwest State University Computer Science Program.
Software Project Management Lecture # 2. Outline The 4 Ps in Project Management Detailed Insight of each P.
Software Project Management Lecture # 2 Originally shared for: mashhoood.webs.com.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
Dr. Rob Hasker. Avoiding failure  Standish Report, 2014 Standish Report 31% projects cancelled before completion 53% projects ~190% of original estimate.
New Supervisors’ Guide To Effective Supervision
Project Close-Out and Termination Chapter 14 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall14-1.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Project Management Why do projects fail? Technical Reasons
1 Project Management C13PM Session 2 Project Initiation & Definition Russell Taylor Business Department Staff Workroom
Software Project Management
Project Close-Out and Termination Chapter 14 © 2007 Pearson Education.
1 1 Effective Administration of Commercial Contracts Breakout Session # Session D06 Name: Holly Walker, CPCM Corporate Learning Solutions and Contract.
PROJECT MANAGEMENT Software Engineering CSE
Project Management Finals Lesson 1 - Principles - Techniques - Tools.
CHAPTER10 Project Human Resource Management
Chapter 11 Project Management.
The Art of delivering before time and within budget
Change Request Management
A Systems View of Project Management
Stacy Kowalczyk WIC Technical Hour 3/30/2005
Managing the Information Systems Project
Software Project Management
Project Integration Management
TechStambha PMP Certification Training
BUSINESS PLUG-IN B2 BUSINESS PROCESS.
Chapter 3 Managing the Information Systems Project
Software engineering Lecture 21.
Martha Grabowski LeMoyne College
Software Project Management
Chapter 3 Project Management
FOUNDATIONAL CONCEPTS
CHAPTER9 Project Human Resource Management
Performance Management
Project closeout and termination
SE 3800 Note 10 Project Management
Project Management Process Groups
Project Management Chapter 11.
Project Close-Out and Termination
Modern Systems Analysis and Design Third Edition
Projects, Assignments, and other Assessments
Software Project Management
Project Close-Out and Termination
Chapter 3 Managing the Information Systems Project
Project Close-Out and Termination
Chapter 2 Managing the Information Systems Project
Modern Systems Analysis and Design Third Edition
Presentation transcript:

What are the common reasons software development projects fail? Project Failure What are the common reasons software development projects fail?

Starter Question In terms of a software development project, define "success" and "failure". Cost, Time, Functionality, and Quality

Software Project Failure Standish Group: 90 percent of software projects are completed late 66 percent are deemed failures 30 percent are abandoned That figure is probably falsely too high. probably 70% are late probably 30% are significantly late probably over 80% do not fulfill 100% of requirements Everyone agrees the failure rate is too high.

“Critical Success Factors in Software Projects” Causes of Failure Source: “Critical Success Factors in Software Projects” by John Reel 10 signs of IS project failure: Project managers don’t understand users’ needs. The project’s scope is ill-defined. Project changes are managed poorly. The chosen technology changes. Business needs change. Deadlines are unrealistic. Users are resistant. Sponsorship is lost. The project lacks people with appropriate skills. Managers ignore best practices and lessons learned. 1 – 7 occur before even the design starts

Critical Success Factors Source: lots of reading by Dannelly Stable Requirements Accurate Estimations Teamwork and Unified Vision Attention to Risks So how do we get these on a regular basis?

34 Competencies Essential competencies employed by the most successful software project managers.

3 Categories Product Development Skills Project Management Skills People Management Skills blatantly stolen from "Quality Software Project Management" by Futrell, Shafer, Shafer Prentice Hall PTR

Product Develop Skills Awareness of Process Standards - best practices Evaluating Alternative Processes - Evaluating various approaches Tailoring Processes - Modifying standard processes to suit a project Assessing Processes - Defining criteria for reviews Defining the Product - Identifying customer environment and product requirements Managing Requirements - Monitoring requirements changes Managing Subcontractors - Planning, managing, & monitoring performance Performing the Initial Assessment - Assessing difficulty, risks, costs and schedule Selecting Methods and Tools - Defining selection processes Tracking Product Quality - Monitoring the quality of an evolving product Understanding Development Activities - Learning the software development cycle 34 Competencies

Project Management Skills Building a WBS - determining the relationships between the work to be done. Documenting Plans - describing how the work should be done. Estimating Costs - Estimating cost to complete the project Estimating Effort - Estimating effort required to complete the project Managing Risks - Identifying and determining the impact of risks Monitoring Development - Monitoring the production of software Scheduling Work - Creating a schedule and key milestones Selecting Metrics - Choosing and using appropriate metrics Selecting Project Management Tools - Knowing how to select PM tools Tracking Processes - Monitoring compliance of project team Tracking Project Progress - Monitoring progress using metrics 34 Competencies

People Management Skills Appraising Performance - Evaluating teams to enhance performance Handling Intellectual Property - business law Holding Effective Meetings - Planning and running excellent meetings Interaction and Communication - Dealing with developers, upper management, and other teams Leadership - Coaching project teams for optimal results Managing Change - Being an effective change agent Negotiating Successfully - Resolving conflicts and negotiating successfully Planning Careers - Structuring and giving career guidance Presenting Effectively - Using effective written and oral skills Recruiting - Recruiting and interviewing team members successfully Selecting a Team - Choosing highly competent teams Teambuilding - Forming, guiding, and maintaining an effective team 34 Competencies

Questions Which skill are you currently the best at? Which skill are you the worst at? Which skill is probably the most difficult to learn? Which skill is the most important? Which skill(s) is not very important?