Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Some Key Reasons Project Fail include:
Unidentified risks
Unidentified stakeholders
Poorly designed project schedule (Using Microsoft Project and not linking the tasks correctly, for example)
Scope creep
...
1 reply by Mahalmadane Touré
Jul 18, 2017 7:35 AM
Mahalmadane Touré
...
Thanks Mr Simms for your help.
Saving Changes...
Mahalmadane TouréEngineer| National Headquarters of Geology and Mines of Mali (Bamako)Mali
Jul 18, 2017 7:28 AM
Replying to Eric Simms
...
Some Key Reasons Project Fail include:
Unidentified risks
Unidentified stakeholders
Poorly designed project schedule (Using Microsoft Project and not linking the tasks correctly, for example)
Scope creep
Thanks Mr Simms for your help. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The problem is most of the projects are considered failure because the incorrect project objectives definition. For example "growth in market share 5% in the current year". Most of the objectives are related to the product, not to the project. The only objetives you must define for a project is related to scope, time, cost and quality. Obviously you must derive them from the business or strategic objectives like I stated before.
...
1 reply by Mahalmadane Touré
Jul 18, 2017 5:01 PM
Mahalmadane Touré
...
Thanks for your help I really appreciate it.
Saving Changes...
S RajasekarSenior Project Manager| AllscriptsBangalore, Karnataka, India
People - Every thing created for people by people , It is important to have right people in right place to success
Right Product Manager/Analyst - Create right business/project objective
Right Project Manager - Plan and Execute project with in agreed/acceptable constraints
Right Team with right skills execute/perform the task
Right Stakeholders - Support/co-operate for project success
...
1 reply by Mahalmadane Touré
Jul 18, 2017 5:01 PM
Mahalmadane Touré
...
Thanks for your help I really appreciate it.
Saving Changes...
Amany NuseibehSpeaker, Global Leader | Optimal ConsultingSydney, Nsw, Australia
Depending on the definition of success (scope, cost and time as well as achieving business outcomes and delivering benefits). In Australia we always give the Opera House Project as an example; while the project exceeded its budget, and was late, it yet delivered its intended outcomes and benefits.
If you look at a project in a similar fashion to cooking/preparing a meal, you need the right ingredients at the right time with the right amount. It is quite a delicate science and art. Hence, to ensure success the team needs a solid understanding of what needs to be achieved and how it will be achieved. Stakeholders expectations need to be set and managed throughout the project. Customer (end product user) need to be engaged and having a sense of ownership. The team needs to work collaboratively and be open and honest about any risks and issues. And the most important factor is the right level of sponsorship.
...
1 reply by Mahalmadane Touré
Jul 18, 2017 5:02 PM
Mahalmadane Touré
...
Thanks for your help I really appreciate it.
Saving Changes...
KAMAL SABNANIAccount Delivery Manager| L&T - Technology Services Limited.Gautambudh Nagar, Uttar Pradesh, India
Lack of connectivity in team members is also one of the reason of project failure. Other reasons are poor planning and unidentified risks.
Projects fail because the team/manager fails to identify requirements, fails to create deliverables around those requirements, and fails to utilize that various PM tools and knowledge areas to answer to both requirements and deliverables.
In regards to knowledge areas (risk, cost, time, scope, communication, stakeholders, quality, etc...) a lack of 1 of these might not be a death sentence, but it certainly hampers the project and makes it harder to reach deliverable acceptance.
If I had to rank my own list of why projects fail, I'd quickly highlight lack of communication, lack of proper scope identification, lack of quality standards to catch issues with acceptance, and lack of prioritization. I believe many projects can get by without an official WBS, especially in an agile environment, but the others included above are musts.
...
1 reply by Mahalmadane Touré
Jul 18, 2017 5:03 PM
Mahalmadane Touré
...
Thanks for your help I really appreciate it.
Saving Changes...
Mahalmadane TouréEngineer| National Headquarters of Geology and Mines of Mali (Bamako)Mali
Jul 18, 2017 7:58 AM
Replying to Sergio Luis Conte
...
The problem is most of the projects are considered failure because the incorrect project objectives definition. For example "growth in market share 5% in the current year". Most of the objectives are related to the product, not to the project. The only objetives you must define for a project is related to scope, time, cost and quality. Obviously you must derive them from the business or strategic objectives like I stated before.
Thanks for your help I really appreciate it. Saving Changes...
Mahalmadane TouréEngineer| National Headquarters of Geology and Mines of Mali (Bamako)Mali
Jul 18, 2017 8:09 AM
Replying to S Rajasekar
...
People - Every thing created for people by people , It is important to have right people in right place to success
Right Product Manager/Analyst - Create right business/project objective
Right Project Manager - Plan and Execute project with in agreed/acceptable constraints
Right Team with right skills execute/perform the task
Right Stakeholders - Support/co-operate for project success
Thanks for your help I really appreciate it. Saving Changes...
Mahalmadane TouréEngineer| National Headquarters of Geology and Mines of Mali (Bamako)Mali
Jul 18, 2017 11:33 AM
Replying to Amany Nuseibeh
...
Depending on the definition of success (scope, cost and time as well as achieving business outcomes and delivering benefits). In Australia we always give the Opera House Project as an example; while the project exceeded its budget, and was late, it yet delivered its intended outcomes and benefits.
If you look at a project in a similar fashion to cooking/preparing a meal, you need the right ingredients at the right time with the right amount. It is quite a delicate science and art. Hence, to ensure success the team needs a solid understanding of what needs to be achieved and how it will be achieved. Stakeholders expectations need to be set and managed throughout the project. Customer (end product user) need to be engaged and having a sense of ownership. The team needs to work collaboratively and be open and honest about any risks and issues. And the most important factor is the right level of sponsorship.
Thanks for your help I really appreciate it. Saving Changes...