There are quite a few candidates in my mind.
Members request for quitting the team
Unachievable schedule
Strongly over budget
Poor relationships with customer
To me, the team member requesting to leave seems the worse one. Not just impacting the current project, probably impacting the future too. Saving Changes...
In my opinion "member requesting to leave" speaks about conflict in the team and should be solvable; if handled timely and correctly shall not critically impact the project.
I would put lack of (adequate) risk management. Saving Changes...
RAJON BANERJEEKalyani, District: Nadia, West Bengal, India
Aug 29, 2019 2:48 AM
Replying to Deepesh Rammoorthy
...
I would put Scope Creep, Cost Overruns and Schedule Overruns on top of the list before Resource loss as primary reasons for Project Failure
Agreed with Deepesh... Very good point.. Saving Changes...
Tim PodestaDirector of PM/PMO| Former BP- now IndependentPenn, Bucks, United Kingdom
Team misalignment followed by gaps in front end planning, both of which can be measured by benchmarking, Saving Changes...
Paul AzanorProject Consultant| Lagos NigeriaIkoyi, Lagos, Nigeria
Ineffective communication is another one. ( Not following the communication plan )
Big source of project misalignment and conflict Saving Changes...
Harish RanganathaPgMP coach and Program Manager Consultant| ACEPROBangalore, Kar., India
In pure management terms, if CPI or SPI are going below 0.85, then it is the sign of project collapse. Unless you re-baseline again (mean you buy time or infuse more funds), it is increasingly difficult to retrieve the project back. Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
I suggest 'poorly defined business, functional and technical requirements'. Those are the first thing I look for when assessing the health of a project. Often the requirements are somewhat lacking, which almost always means the project will run into problems. The more complex the project, the most likely problems are to occur when its requirements aren't well defined. Saving Changes...
Justus NScrum Master| BCBSTXArlington, Tx, United States
A project that was scheduled to be completed in 2 years, takes 7 years and then in year #9 they killed it and went with a vendor product. (true story) Saving Changes...
I agree with Eric. When you discover that the team has not been working to complete or correct requirements, that is a strong indicator that extensive rework, or additional work is necessary. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Stakeholder disengagement is a strong sign that your project is not doing well. Saving Changes...
