Monday, June 4, 2007

Part 2 -- What can you do when a project goes terribly wrong?

In my previous blog I recommended steps to follow and pitfalls to avoid once a project is in trouble. Now that we have a strategy for change and have management buy-in, it is time to take action.

It is best to start by assembling the entire project team and communicating the change strategy. In order to turn-around a failing project effectively you need buy-in from all the team members --- even those not directly involved in implementing the change.

The project plan and schedule needs to be revised and shared with all team members. This is a good time to ask a few questions. Do we have enough or the right resources to move forward? Do we have the right tools? One common outcome I have noticed with projects that get into trouble, is that the original project team did not have the appropriate level of expertise in a new technology. To turn the project around you may need to add a temporary resource with special skills. Find this resource(s) - fast! Get the right tools. Then update the schedule.

Once the Team is assembled, start at the beginning. Review Requirements, Architecture, Design and Test Procedures, in that order. Make necessary modifications before starting development.

As you can see there is a lot of legwork before you can effectively change the course of a project, but you must do it for the project to be successful.

No comments:

Post a Comment