This past week the tweets looked at how to handle taking over a project that is at high risk of failing or has already failed. The first thing to realize when taking over a failing project is that the rules for managing a project from the start don't apply.Another point on taking over a failing project is that you do not have a lot of time to get a handle on it. Management wants quick action.

• The first step is to determine exactly what the state of the project is. This is more than status. You need to know every detail.
• Start by getting the team together to explain how you're going to start getting the project realigned and what help you need from them
• Next, schedule interviews with key team members and stakeholders to assess where the project is and what the major issues have been.
• As you interview people you want to listen for clues such as scope changes, stakeholder involevment, technical issues etc.
• As you interview people take good notes and keep a list of issues and risks.
• You also want to review all of the project artifacts including status reports, risk logs, plans, resources, requirements docs, charters etc.
• After the interviews and doc reviews you want to take the notes and lists you created to perform an analysis of the data.
• For each issue or risk give it a severity score of 1 low - 5 high and an impact score of 1 - 5. Multiply the 2 scores for a composite score.

Part 2 of this series starts tomorrow at @tprusk1. I'll post the complete series at the end of the week.

This week I had several meetings with clients to review their projects and discuss next steps. What was most interesting about this week is that all of the clients not only like having solid project plans but that they want to help create and manage them. Teaming up with your customers, either internal or external to define and manage the plan is a great way to get buy in and support for the project. Keep this in mind when you start your next project.

Sometime in your PM career you will be asked to take over a project already underway. This week's tweets looked at how to do this effectively.

There are many reasons why a PM is being replaced. Be sure you know why for the project you are taking on to understand what you are getting.

• One of the first tasks for taking over a project is to introduce yourself to the team. Do this both individually and in a team meeting.
• The next task is to conduct an assessment of the project. This is important regardless of the status of the project.
• The project assessment has 2 purposes. 1) confirms or disporoves stated status 2) Gives you a detailed view of the project.
• The project assessment includes a review of the project plan, schedule, risks, issues, budget, and resource plan.
• If the assessment indicates the project status is not green you need to create a plan to remediate the issues. Leverage the team on this.
• As soon as possible after you take over the project, schedule a meeting with the sponsor and business owner to review their expectations.
• If possible meet with the previous project manager to discuss the project and review project artifacts.
• If the previous project manager is staying with the project for a transition period work with him/her and create a formal transition plan.
• If the previous project manager is staying with the project for a transition period work with him/her and create a formal transition plan.

Next week we will take the scenario of taking over an in-flight project to the extreme, taking over a project at high risk to fai

Monday Monday

The start of a new week is a perfect time to review last week's accomplishments and challenges for the project. Keep a log of these to help in preparing status reports and other project updates.

Terry (May 2012)