Rants
Questions
Soapbox
Best Practices
Apply today for a FREE subscription to CIO Magazine!
Mon, Nov 3, 2008 14:16 EST
|
Posted by: samhomer in Best Practices Topic: Development
Current Rating: |
How to Turn a Failing Project Around?
Have you ever been asked to takeover a failing project? The reasons for a project going to “code red” are numerous, but can usually be classified into seven areas:
1-Lack of crisp requirements
2-Insufficient resources
3-Unrealistic time-line
4-Lack of a clear business case
5-Poor project planning and/or inexperienced project leadership
6-Technical and/or process issues
7-Lukewarm project sponsorship – insufficient authority for the project leader
When taking over a project at risk, the first thing one can do is ask these questions:
-How compelling is the business case for the project?
-Do you have clear requirements?
-Is there a project plan, and is it up-to-date?
-Is there a change control process in place?
-Is the project’s status reporting reliable and transparent?
-Is the project sponsor supportive and effective?
-What are the top customer’s concerns?
-What is the project’s financial situation?
-Is the project on schedule or not?
Equipped with answers to these questions, the next step is to address these six areas:
1-The Project team:
a.Take inventory of teams’ strengths and weaknesses
b.Address resource sufficiency issues
c.Address morale issues - make resource changes if necessary
d.Create a sense of urgency (how does this project impact the company and the team?)
2-Customer
a.Manage customer expectations, refuse to be treated like a punching bag
b.Insist on dealing with the decision maker(s)
c.Insist on being given the authority to act. and the resources to succeed
d.Present the solution quickly (within 1-2 weeks)
e.Schedule short summary meetings for each day with the customer
f.Communicate success and challenges with high degree of transparency
3-Technology
a.Address any infrastructure problems
b.Address software and tools needs
c.Resolve implementation and logistical issues
4-Project:
a.Re-establish and assert control over the project
b.Tighten up the requirements
c.Update the project plan and act accordingly
d.Implement a change management process
e.Start project reporting immediately
f.Re-work the project plan and WBS into smaller chunks
g.Aim for quick wins to build credibility
5-Financial:
a.If the project is over budget, secure additional funds, or reduce scope, or increase time to completion
6-Operation:
a.Address logistical barriers
sam.homer@businessways.com
Great list for governing projects!
I would add one more action to this list; STOP all work until you you re-plan, and obtain the customer's agreement.
This list will be more useful if it is placed in a an "action item" list format
If the person coming on to engineer the turn-around on the project doesn't do these things, management will be concerned they don't have the right person.
You also need to get vendors and suppliers on your side. Many projects fail because of the antagonistic relationship between the vendor/supplier and the customer. This doesn't mean that you give in to anything. As a matter of fact, sometimes you may have to fire your vendor, and move on. But if you can get their support, this will be a big factor in the turning the project around.
Sometimes there is no other option but to kill the project. Salvaging a failing project can be too risky to the organization as well as the reputation of the Project Manager, killing the project will release the resources/funds allocated for the failed project. I have published a small article on when to kill a project, the article explains when and how projects get killed.