Premium Essay

Software Project Failure and Solutions

In: Computers and Technology

Submitted By bumet
Words 1125
Pages 5
Software Project Failure and Solutions

According to Krigsman, (2007) business-critical and services project are not completed on time, cost too much, contain a lot of defects and fail to satisfy the business requirements they set out to achieve. Clancy, (1995) states that United States spend more than $250 billion each year on approximately 175,000 IT development project of which most will fail and that software development projects are in chaos. This paper aim to explain the reason why a significant amount of software projects fail and what make software projects succeed by reviewing evidence from a few reports and surveys.

Research conducted by Standish Group in 1995, shows that 31.1% of project will fail before they are completed and 52% of project will cost 189% of their original cost. On average only 16.2% of software projects are finish on time and on-budget and 9% of software projects are finish on time within budget for large companies. Similarly failure figures for project failure due to restarts, cost overruns, tie overruns were disheartening and to make things worst nothing change since then (Clancy, 1995).

The Standish Group survey of IT executive manager reveals that user involvement, executive management support and clear statement of requirements are the three major reasons why project succeed. Incomplete requirements and lack of user involvement are the main opinion why projects are impaired, eventually cancelled and hence fail.

Table 1: Some of the result of Clancy, 1995 Standish Group survey results

Rank

Project Success Factors

% of Response

Projects Impaired Factors

% of Response

1

User Involvement

15.9%

Incomplete Requirement

13.1%

2

Executive Management Support

13.9%

Lack of User Involvement

12.4%

3

Clear Statement of Requirement

13.0%…...

Similar Documents

Premium Essay

It Project Failures

...Gorby Case Study: IT Project Implementation Failures The case study of the Memorial Health System and their CPOE implementation poses many issues that contributed to their IT failure. The first issue I noticed was the unrealistic timeline developed by the original champions Dryer and Roberts. Dryer and Roberts planned to execute their new IT among eight hospitals in less than eighteen months. With their failure to respect uncertainty from members of the discussion board, they demanded and rushed results from their clinical and IT team. This resulted in a rushed out requirements analysis, request for proposal quickly issued, and a rush to select the vendor and signing the contract. When the original champions were replaced by Lu and Sparks, I initially thought they were capable of successfully pulling off implementing this system even in the short timeframe. They would probably have been successful if Sparks did not lack candor. The executive project manager, Martin, had a perfectly thorough and detailed a project plan that most likely would have guided the organization to success if they followed her suggestions. Spark’s lack of candor and anger to Martin’s project plan lead her to lie about the truth and withhold important progress information on the project. At the end of the eighteen month timeline, the go live date resulted in failure due to all of these issues. With an organization like ours, there are several ways to reduce an IT failure like the......

Words: 441 - Pages: 2

Premium Essay

Software Project

...Global Bank ATM PROJECT REVISIONS HISTORY TABLE Date Version Description Author February 20, 2013 ATM se5 Software development for ATM machines Sindiso Suzzy Moyo 1. Project Plan Overview Project Goals 1.1 Project Summary 1.1.1 Purpose, Scope, and Objectives This project was designed to study the requests, designs, implementation and maintenance of the software for both the bank server and the ATM client devices which will include the Global Bank ATM network, in accordance with the requirements specified by the client. Every activity directly linked to the purpose is measured to be in scope. Any activity that is not directly related to the purposes is obviously considered out of scope. Let take for instance, issues concerning: The availability of ATM hardware and network are out of the scope of the project. Please find below the objectives of the project are: •Project to be completed by project due date • Project to be completed within its budget • All deliverables will be provided as identified in section 1.1.3 by the project due date •All stated request should be fulfill as in the SRS of the software product deliverable, and it falls within any of the below categories — The modification of Global Bank customer database — The interface with the bank’s computerized account system — ATM transactions of customers — Customer ATM statement — Periodic numerical report of ATM operations 1.1.2 Assumptions and Constraints This project is planned with......

Words: 808 - Pages: 4

Premium Essay

Project Failures

...factors lead to software project failure? June Verner NICTA Alexandria Sydney Australia june.vemer@nicta.com.au Jennifer Sampson NICTA Alexandria Sydney Australia jennifer.sampson@nicta.com.au Narciso Cerpa University olTalca Talca Chile n.cerpa@utalca.cl. It has been suggested that there is more than one reason for a software development project to fail. However, most of the literature that discusses project failure tends to be rather general, supplying us with lists of risk aod failure factors, and focusing on the negative business effects of the failure. Very little research has attempted an in-depth investigation of anum ber of failed projects to identify exactly what are the factors behind the failure. In this research we analyze data from 70 failed projects. This data provides us with practitioners' perspectives on 57 development and management factors for projects they considered were failures. Our results show that all projects we investigated suffered from numerous failure factors. For a single project the number of such factors ranges from 5 to 47. While there does not appear to be any overarching set of failure factors we discovered that all of the projects suffered from poor project management Most projects additionally suffered from organizational factors outside the project manager's control. We conclude with suggestions for minimizing the four most common failure factors. Abstract - Index terms software project failure, software project......

Words: 5556 - Pages: 23

Premium Essay

Software Project Management Plan

...Software Project Management Plan August 27, 2012 IT Management System Luvianka Olivares Table of Contents Scope Statement.........................................................................................3-4 Work breakdown structure..........................................................................5 Network diagram...........................................................................................6 Risk management plan............................................................................7-10 Resource management plan..................................................................11-12 Communication management plan......................................................13-14 Scope Statement Project Name: IT Management System Project Manager: Luvianka Olivares Project Objectives: To design and install a computer network for a small business. Deliverables: Software package will manage: * Running of all computers in the business * Training and extensive end-user documentation * Technical support self-service website * Full backup process * Security of IT development tools * Project Management- Project charter, project scope statement, status reports, final project report, lessons-learned report, and any other document required to manage this project Milestones: Training digital video files Preliminary......

Words: 1828 - Pages: 8

Premium Essay

Project Management Software

...Leader: Matric No: MUHAMAD KAMARUDDIN BIN MAT MAIDI 2013609712 | Assignment Title : PROJECT MANAGEMENT SOFTWARE | Due date of Assignment : 14/8/2013 Submission Date : 14/8/2013 | DECLARATION : We declare that no part of of this assignment has been copied from other person’s work except where due acknowledgement is made in the text, and no part of this assignment has been written for me by any other person except where such collaboration has been authorised by the lecturer concerned Group’s Leader Signature............................................................. Date........................................ A lecturer/tutor has and may exercise a right not to mark this assignment if the the above declaration has not been signed. If the above declaration is found to be false, no mark will be awarded for this assignment Copyright@Estate Management Dept, UiTM Perak TABLE OF CONTENT No | Content | Page | 1. | Acknowledgement | 3 | 2. | Introduction | 4 | 3. | Definition | 5 | 4. | Types of Project Management Software | 5~6 | 5. | Characteristics | 7~8 | 6. | Advantage and Disadvantages | 9 | 7. | Project Management Application | 10 | 8. | Conclusion | 11 | 9. | References | 12 | ACKNOWLEDGEMENT First of all, thanks to Allah S.W.T for his mercy & guidance in giving us full......

Words: 2246 - Pages: 9

Premium Essay

London Ambulance Service Software Failure

...London Ambulance Service Software Failure The London Ambulance Service (LAS) responds between 2000 and 2500 calls per day with a fleet of 750 vehicles, in less than three minutes. Their system was originally manually operated where details of an incident call taken by a control assistant is used to ascertain the location of an incident scene through the use of a map book. This information is then passed to a dispatch team who direct the appropriate ambulance to the incident scene through a radio call. Due to the short comings of this manual system, the LAS thought to computerize its dispatch system in 1987. The first attempt was started in the 1980’s, abandoned in 1990 and failed after spending £7.5 million. The second attempt by LAS was signed in May 1991. On the morning of Monday 26th October 1992 the LAS CAD system went live for the first time. Unfortunately there were 81 known bugs in the system at that time and it had been 10 months since the control room staff were first trained to use the software. The system had 4 primary flaws when it went live; it did not function well. Furthermore, the user interface had black spots which meant that the user could not see all the information on screen and finally, additionally, the system stored incident information even after it was not needed, which caused the system to fill up memory and fail. The first of these problems began to show during the morning rush of calls; there were a number of duplicate calls which led to a...

Words: 1738 - Pages: 7

Free Essay

Project Failure

...Doyne Mc Nally Project Failure Essay Title: International Airport Baggage Handling System Why the project was established: Denver International Airport, often called DIA, is an airport in Denver, Colorado. By land size, at 140 km2, it is the largest international airport in the United States, and the third largest international airport in the world. Back in late 1980’s the city of Denver felt they needed a larger airport to deal with the increasing amount of air traffic through the city, so they elected to construct a highly efficient, fully automated airport. The predicted passenger handling was an outstanding 50 million annually. It was envisioned as a state of the art airport mainly due to its luggage handling system. This system of automated baggage-handling would greatly reduce aircraft turnaround time. Faster turnaround meant more efficient operations and was a cornerstone of the airports competitive advantage. Project Sponsors and Stakeholders: The Airport Project Management team on behalf of the City of Denver was the major stakeholder but funding was also received from United and Continental Airlines as they would eventually use terminals as major hubs for their respective organisations. The company BAE Automated systems was employed by DIA to design a conveyor system to meet the airports needs. Ultimately the majority of funding came from the pockets of the citizens of Colorado. The overall cost of the project was $ Success Criteria: The airport's......

Words: 769 - Pages: 4

Premium Essay

Software Failure

...Lecturer: Nick Gachui. Date Due: August 2014.   a) What are the tasks and activities involved in the development, integration and testing of information system? i. Development  Code and Test Software Code each module according to established standards.  Integrate Software Integrate the software units and software components and test in accordance with the integration plan. Ensure that each module satisfies the requirements of the software at the conclusion of the integration activity.  Conduct Software Qualification Testing. Conducting qualification testing in accordance with the qualification requirements for the software item. Ensure that the implementation of each software requirement is tested for compliance. ii. Integration  Conduct System Qualification Testing Ensures that the implementation of each system requirement is tested for compliance and that the system is ready for delivery  Install Software Install the software product in the target environment as designed, and in accordance with the Installation Plan. Ensures that the software code and databases initialize, execute, and terminate as specified in the contract.  Document Software Acceptance Support The developer shall complete and deliver the software product as specified. The developer shall provide initial and continuing training and support to the acquirer as specified.  Revise Previous Documentation Review and update previous phase......

Words: 2123 - Pages: 9

Premium Essay

It It Project Implementation Failures

...IT project implementation failures Annette HCS/483 March 16, 2015 Jose L. Rivera IT project implementation failures Introduction Memorial Health System is an eight-hospital health system in the Midwestern United States. The hospitals range in size from 200 to 700 beds. Four years ago, the health system began a board-approved computerized provider order entry (CPOE) implementation. The project was a major failure after having experienced poor support from leadership, a lack of appropriate resourcing, leadership and staffing changes, exceeding budget and time, and last minute changes to the scope of the project. There are processes that should be followed in an information system implementation. Not adhering to typical procedures can lead to project failure. This paper will describe reasons for failure, as well as ways to minimize project failure. IT Implementation. The typical information technology implementation process begins with an identification of a need. A committee can be formed and charged with finding a solution. This committee develops the project objectives including the methodology for selecting a system. Next, define the system goals and create a timeline for the committee activities. For example, the committee will be selecting a system for CPOE. The committee will meet weekly for the next eight weeks to create and document the goals of the project and what needs to occur at each step in the selection process. The committee then......

Words: 879 - Pages: 4

Free Essay

Types of Software Solutions

...Options for Solution and Recommendation After the initial investigations and scoping there are a few options available to providing the system to satisfy the requirements of Craggy Island Bookshop. 1. Off-the-Shelf: The requirements of Craggy Island are of a commercial nature, this functionality is now commonly found in Commercially available applications. One option is to carefully analyse the requirement and determine the suitability of the off-the-shelf package. The pros of this option; • If a suitable software can be identified, it is immediately available. There is no wastage of time on development. • Software is usually very comprehensive and can cater for way more functionality than currently required. Because it is feature rich additional functionality could be already part of purchased software. • Documentation and support is usually comprehensive • The software is usually very stable Cons for Off-the-shelf are; • The software is designed for a large audience and functionality is generic, hence it will not be an exact fit to the business. • Functionality is inflexible and usually business process may have to be adjusted to fit the software. • Additional features are not easy to get. • Generic nature of software makes it difficult to gain a competitive advantage. 2. Bespoke Software: The second option is to develop a customized system from scratch. Bespoke systems offer the following advantages; • Software is designed and developed to be an......

Words: 795 - Pages: 4

Premium Essay

Software Project Management

...Project Management for Information Systems A refreshingly readable, realistic and relevant view of project management within the context of information systems. This comprehensive and practical book is an excellent starting point for any practicing project managers or students of Project Management for Information Systems, whether they are from a computing or a business background, at undergraduate or masters level. In this book, the practical perspective and industry experience of the authors complements the clear explanation of project management theory and methodologies. The authors strike a good balance covering both the mechanics of project management and the human factors involved and plentiful case studies, exercises and good and bad examples from real life help the reader to put the theory into context and into practice. This fifth edition has new material on: • development life-cycles and approaches (including agile approaches) • different types of IS projects and how to manage them • implementing change through information systems • updated coverage of leadership and management. Project Management for Information Systems is all you need to plan every aspect of an IS project and ensure that it is implemented on time, within budget and to quality standards. ‘This is an excellent starting point: a practical down-to-earth and comprehensive guide to many facets of IS project management. Cadle and Yeates draw on a wealth of experience in......

Words: 178628 - Pages: 715

Free Essay

It Project Implementation Failures

...IT Project Implementation Failures Mayelin Vargas HCS/483 03/01/2012 Michael Aiken University of Phoenix When implementing an IT project, many factors and indicators can play into failures of such a project. As seen in the case study of Memorial Health System, the CPOE implementation faced different issues indicating the project failure. In this paper, five reasons of project failure would be identified. It would show how these indicators manifested at Memorial Health System. I will describe what I have done differently to eliminate or minimize the effect of the indicator. Some of the reasons for project failure include; Organizational Baggage, Lack of Belief in the Project, Lack of Candor, Invisible Progress, and Failure to Respect Uncertainty. The first reason for project failure at Memorial was Organizational Baggage. When the Project was first introduced by Dryer and Roberts, a member asked if it was possible to finish this project on the time expected since they took two years just to set up emails at a previous project: therefore, previous project failures was still been questioned when it came to the timeline. The second reason for project failure at this organization was the lack of Belief in the project. Most individuals in the organization were opposed to the providers order entry system. When the IT project was first introduced many feared that the work -load would increment if verbal orders were substituted by computer entry orders. The third reason for...

Words: 1020 - Pages: 5

Premium Essay

Software Architecture Project

...Software Architecture Project Team A CSS 422 11-7-11 Mohammad Shakir Kamali Executive Summary This paper will discuss in detail the software currently in use at the four facilities of Riordan Manufacturing. Likewise, the paper will discuss the recommended software upgrades suggested by Team A in week 2. These recommendations will allow Riordan Manufacturing and its employee’s to work more efficiently and have greater overall productivity. This will ensure that Riordan Manufacturing will stay one step ahead of their competitors and have the ability to do business in a more professional manner. To do this, Riordan Manufacturing will need upgrades involving both hardware and software with minimal training and downtime. Introduction Riordan Manufacturing must update their current software and hardware systems to become up-to-date and competitive. Riordan Manufacturing consists of four separate locations, which all currently use dated software systems such as Microsoft 98 OS and Microsoft Office 2K, updating these outdated systems will increase efficiency with the advancements in newer systems. Riordan Manufacturing also has older outdated servers and switches that should be replaced to increase computing speed and transfer time. Updating the overall software architecture of Riordan will see gains overall for Riordan Manufacturing. Company Background Riordan Manufacturing is a global plastics manufacturer employing 550 people with projected annual earnings of $46......

Words: 1655 - Pages: 7

Free Essay

Software Failure

...[pic] MUHAMAD SUFRI BIN MUHAMMAD 158034 SOFTWARE VERIFICATION AND VALIDATION DR. SALMI BT. BAHAROM ESSAY ON SOFTWARE FAILURE (FAILURE OF RADIATION-THERAPY MACHINE) SOFTWARE FAILURE IN RADIATION THERAPY MACHINE Computer programmers spend a lot of time debugging software, yet end users like us still encounter bugs or problem while using those software. Computers bugs can result in many errors including unexpected program crashes or even can result in many troubles such as lost cost, reputation of the software product or even life. There are many software failures out there that we can find and learn from their mistakes. This is what happens at National Cancer Institute, Panama City on November 2000 which at least has eight unluckily patients die, while another 20 receive overdose concerned will get risk of health problems or serious complications from radiation. Twelve years ago, Victor Garcia considers himself lucky to be alive which a combination of cancer and miscalculation almost killed him. The software which created by Multidata System International, a U.S firm get trouble due to limitations of the computer program that guided use of a radiation-therapy machine. It is also miscalculates the proper dosage of radiation for patients undergoing radiation therapy. In order to use this software, it is allows a radiation therapist to draw on a computer screen then the placement of metal shields......

Words: 1174 - Pages: 5

Premium Essay

Hospital Software Solution Analysis

...HOSPITAL SOFTWARE SOLUTIONS ANALYSIS LEADERSHIP AND CHANGE MANAGEMENT PROFESSOR: LORRAINE NAVE, NANCY SANGIULIANO GEORGE BROWN COLLEGE 2012 RITESH PATEL STU ID: 100810509 3/24/2012 ---- Abstract This paper explore the problems and their solutions arising in a health care environment during conflict management. The case provides a good opportunity for the application of a number of theoretical concepts surrounding leadership, power/influence, motivation, corporate culture and conflict. Start with the HSS, In 1999 ten software engineering students found Hospital Software solution(HSS) when Ontario hospitals were facing challenges during integrating technology into their operation. This paper points out some problems faced by new employees when they enter in to the corporate world and they are assigned a work outside their job description. It also analyses the conflicts arises between managers and employee due to lake of communication and inappropriate office culture. Here the story of a employee, Natalie MacLachlan, a conscientious student of honour business management programme had joined a company in which she has been given a position for which her skills were not suitable and after entering in to company she had......

Words: 1199 - Pages: 5