Just gone through Anish Mathai Mathew’s post on project failure reasons and thought to reply there but I think due to some technical issues I was not able to post anything on that website. So I thought to post it here:
Answers based on my experience.
#1. Lacking Sponsor’s Involvement/Ownership
>> Indeed. But again, you must be a solution provider and should not be waiting for your cusomer to explain the requirements. It must be your job to tell him ‘what he want!’.
#2. Halo Effect (Wrong Man for the Job)
>> Agreed
#3. Poor HR Management
>> I agree – assuming, it have connection wit #2. Otherwise disagreed.
#4. Poor/Inadequate Project Communications
>> Agreed 100%. Communication! yea, communication, communication and communication
#5. Ignoring Project Stakeholders
>> Agreed, but would like to rename it to ‘Proper Project Management’
#6. Absence of Risk Management
>> Again, something to do with ‘Proper Project Management’
#7. Scope Creep/Unrealistic Expectations
>> Disagreed, as this can be rectified at the initial stages of project planning. Someting to do with ‘Proper Project Management’
#8. Lack of Monitoring of Plan
>> Agreed, again – ‘Proper Project Management’
#9. Absence of a Project Management Methodology
>> 50%. A properly defined ‘methodology’ can only speedup the process. Every projects use some kind of methodology unknownly. We had projects before we invented terms ‘agile’ etc.
#10. Simply BAD LUCK
>> Disagreed. It is we who decide whether the project need to be a success or failure.
VN:F [1.9.18_1163]
Rating: 0.0/5 (0 votes cast)
Recent Comments