Top Ten Obstacles To Project Success

“ Top Ten” Countdown of Obstacles to Project Success and ways to mitigate them PRESENTED BY: Lou Gasco MüTō Performance Corp. [email_address] 212-842-0508 xt 3

Use of this presentation ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

data sources ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

format ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

The Top Ten Obstacles to Project Success a countdown

#10. A skill set challenged team Explanation The team is unable to support the project from whole, or partial lack of technical skill-set. Symptoms - Code is completely redone from scratch. - Delivery dates are constantly moved as “new information” becomes available. - Team mates say, “I don’t know how to do this.” Potential Mitigation ,[object Object],[object Object],[object Object],‘ I know we are supposed to be finished tomorrow, but we had a question… Did you say “Three” or “Tree”?’ a supplier to the project manager when construction was stalled due to a requirements question.

#9. Delegated responsibility unrelated to authority. Explanation Project manager (or team) lacks the authority to match their responsibility. Symptoms - The PM is taking minutes while someone else manages the project meetings. - Team mates constantly require approvals from their management to deliver on their responsibilities. Potential Mitigation ,[object Object],[object Object],“ You are only authorized to complete the project, for anything else, you have to get written approval, but I’m not sure from who.” Clear instructions on the modus operandum from the sponsor to the project manager

#8. Challenging schedule. Explanation The date for delivery of the project’s solution makes it difficult to deliver on time. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],[object Object],“ The deadline for this project is Tuesday, January 11 th , because we started on November 1 st , and that makes it all One’s.” a sponsor to the project team

#7. Minimal or non-existent testing. Explanation The testing (Q&A) process is either non-existent, or reduced greatly beyond any planned duration. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],[object Object],“ We just saved 22% of the budget by cutting out QA, entirely. After all, we could test Monday morning in Production!” a Project Manager to his Sponsor with a rationale

#6. Tardy delivery of project tasks. Explanation Suppliers are not delivering their tasks on time. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],[object Object],“ No problem, we can have it for you by when you want it, mostly … I’m sure, give or take a few things, or a week, maybe.” a Supplier, guaranteeing delivery to the Project Manager

#5. The resource challenge Explanation Not enough resources to complete the project as desired. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],[object Object],“ If everybody stayed in the office, worked around the clock, took no breaks, and stopped everything else we could finish the job by this Tuesday.” A Project Manager to his sponsor when asked to do more with less.

#4. The finance challenge Explanation Not enough funding to complete the project as desired. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],[object Object],“ Don’t worry about the budget, we have no budget, just do the project, we’ll figure it out after.” A Sponsor to the project manager after being told, they had no budget code.

#3. A disappearing sponsor. Explanation The sponsor cannot be reached. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],“ I never actually gave you permission to go ahead with the project.” The sponsor to the project manager, when asked to mediate a situation with another team.

#2. Invisible requirements. Explanation The project has a ‘goal’, but no finalized requirements. Symptoms ,[object Object],[object Object],Potential Mitigation ,[object Object],[object Object],“ Well, if you are not going to be constructive we’ll just have to replace you.” a sponsor to a project lead, when the lead asked “What are we doing?”

#1. Spontaneous requirements. Explanation Scope creep. Symptoms - “We have a change control.” - “Say…while we are doing that…why don’t we do this other thing too?” Potential Mitigation ,[object Object],[object Object],“ Since we have the patient open, why don’t we also remove the appendix, he’s not using it, is he?” a surgeon who is no longer practicing.

One final thought… Success is not by chance.

summary ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],What’s your team’s temperature? Do you? Who are you attempting to communicate with, and how do they perceive you?

Top Ten Obstacles To Project Success

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Top Ten Obstacles To Project Success

Similar to Top Ten Obstacles To Project Success (20)

Recently uploaded

Recently uploaded (20)

Top Ten Obstacles To Project Success