As an expert in the field of project management, you probably have experienced, seen or heard of fail projects story. Based on your experience, what are the 3 to 5 main project failure reasons? Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
There are many reasons of course but some that I’ve seen:
No or Poor Risk Management
Lack of User Engagement
Poor Controlling and Monitoring Saving Changes...
Luigi BELLIProject Manager, Consultant, Author| CENTURICALBruxelles, Belgium
On my experience 3 reasons mostly apply:
1) Sponsors buy-in: If the sponsor is "forced" to do the project - such as regulatory projects or - it is very likely that the project will loose its sustain and will go into miserable mode.
2) Budget cuts: when the budget cuts are around, there is nothing you can do, some projects will be doomed for failure
3) Low ROI: when the project is going to deliver very low return on investment, there is also a very high-probability that it will fail or get killed Saving Changes...
On top off above mentioned reasons:
Poor business analysis and requirements management
Poor requirements validation / solution validation
...
1 reply by Keith Hogan
Jan 30, 2019 4:17 PM
Keith Hogan
...
Define Failure = failed to meet all the requirements on schedule and on/under budget.
In dynamic business environments, circumstances may change faster than the team can adjust. Therefore, the rate of requirement change exceeds the rate of delivery.
Agile is a method for keeping pace of change as you go.
Traditionally, a snapshot of the business needs generates the initial requirements. Over the period of the project this may change. Shorter period is more likely to succeed. Long period is more likely to fail. We break the project into incremental deliveries allowing the requirements to be fixed at the beginning of the phase.
Poorly defined requirements result in rework that eats the schedule and budget.
This may even be due to poorly defined business terms e.g. price may be computed differently by different business units.
Saving Changes...
Joshua RenderProduct Owner| CognizantHarrisville, Ny, United States
While it is good to focus on the value to the business, sometimes that focus becomes to more tunnel vision and less product vision. Decisions are made that seem good for the business and they fail to consider that the business needs to invest money in the project for the project to be any good for the business. Short-term thinking at a time when long-term thinking is required.
Examples:
I was on a project once that chose to reuse old (physical) servers and modify them to suit our needs and save money. The end result was that we didn't save money and lost a lot of time.
I have been on a project that decided to save money by combining the purposes of virtual machines. None of the items placed on the VM's worked as well as they could have because decisions weren't made with IT in mind, but immediate needs of the business.
I had a project where we built a desktop application when a web application was what they needed. They didn't want to invest in the infrastructure to get the web application up and running. Now everyone needs to get the desktop application on their machines, the update process is a pain (but thankfully mostly automated), and the long term support costs are higher. They probably would have been better off if they had not bothered to even build this application. Saving Changes...
- Poor requirements or scope management
- Lack of effective sponsorship
- Ineffective risk management Saving Changes...
Jason KaiserIT Project Manager| Oregon Department of TransportationOr, United States
In no specific order…
1. Lack of contractual metrics/KPIs
2. SME & resource availability, turn over
3. Non-existent Conflict Resolution Techniques
4. Gold plating, scope creep
5. Lack of governance support Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
Really many reasons and it depends how to use project management and how is complying with project requirements. Almost poor communications and not all project requirements were collected...etc Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The measure to consider a project as successful or failure are incorrect defined. Saving Changes...
Biju KurienProject Manager| DEMTeachAbu Dhabi, Abu Dhabi, United Arab Emirates
In no specific order
1. Change of management - views & perceptions
2. Diversion of allocated funds
3. Poor holistic vision
4. Difference of opinion in awarding contracts.(What is in it for me?)
5. Schedules being reset by top management (unrealistic) Saving Changes...
Community Champion
