Suggested steps when assuming an already started project?
John LeTourneauSenior Project Manager| MSUEast Lansing, Mi, United States
Is there a good reference document or book for a project manager that assumes a project that has already been started and is somewhere in the middle of the schedule? Saving Changes...
I have never seen a beginner's book written this way, but it is a great idea. Sometimes as a trainer, I address the audience this way.
My advice is to take a beginner's book, but start in the middle, or jump around in it. I tend to approach books this way anyway -- I skim the whole thing in about an hour, then I jump into the parts that I care about.
Usually the topics that are most important mid-project are:
* Status reporting
* Overall communication
* Change control
* Scope control and scope documentation
I would recommend "Project Management for Small Projects" by Sandra Rowe as a good book to take this skim-and-read-selectively approach with. It is much thinner than most PM textbooks, and it gets to the heart of your most critical issues quickly. It also has some solid templates that you could use right away.
Of course it is focused on smaller projects, but in my experience, the inexperienced PMs are often assigned to these types of projects at first. Also, she focuses on the most critical issues first. You could always buy a more comprehensive text book, like Kerzner, in addition to Sandra's book.
(Full disclosure: Sandra is a friend. I mention the book in part because I know her and respect her work, but more importantly I really do think it would be a great resource for what you are describing.) Saving Changes...
Hans RobbersSenior Director| SalesforceVlissingen, Netherlands
John
What you are asking for is pretty imilar to take over a project in the middle due to issues in the past. The reason a proejct manager is replaced is often a project performance which is not line with the expectation.
This becomes apparent in progress reports and most often the project sponsor requests for an audit to bring the project back on track. When Itake over a projecgt I will allways apply an audit and based on the findings decide to dig deeper.
Therefore my recommendation is to approach the project from an audit perspective. There are tons of books out there which deal with this topic.
good luck Saving Changes...
Warwick KowalczykEngineering Manager| Scentre GroupNorth Ryde, Nsw, Australia
Further to Hans' post, the audit will also help you get across the project quickly and understand the objectives, issues and real status.
If it's an IT project that you're working on and you've come from a hands on background, be careful that when you are getting up to speed that you don't get too wrapped up in the detail. I did this once and ended up creating way to much work for myself whilst becoming a block for everyone else. Try to keep high level and don't become and expert in db schemas or code.
Another piece of advice is to spend time talking to the people involved in the project. This is a good way to get to know the skill sets you're dealing with, and get an idea of the mistakes that have been made so that you don't repeat them.
Anyway, taking over an existing project can be seen as a poisoned challice at times so good luck with it!
Warwick Kowalczyk Saving Changes...
John LeTourneauSenior Project Manager| MSUEast Lansing, Mi, United States
Thanks all for the great advice. It is an IT project and I have been getting a little too wrapped up in the technical details. It's tough not to do that because the technology is intriguing. Saving Changes...
Regarding Warwick's "poisoned chalice" comment: Taking over a troubled project can be a great career move. When everyone thinks the project is in trouble, they expect more problems. If you cannot fix the problems, many people will say, "Too bad, but it was doomed from the start." If you can fix it, then you will be a hero.
My early assignments as a project manager were almost all situations where I took over a troubled project, and I learned to love them. Good luck! Saving Changes...
