A project manager is a professional* in the field of project management.
A project manager’s main duty is to ensure the success of a project by minimizing risk throughout the lifetime of the project.
This is done through a variety of methods, both formal and informal**. A project manager will usually have to ask penetrating** questions, detect unstated** assumptions, and resolve interpersonal conflicts**, as well as use more systematic management skills.
According to Wikipedia statistics: 69% of project failures*** are due to lack and/or improper implementation of project management methodologies.
I didn’t have the pleasure of being a project manager but I did see some good project manager implementations and this is my recommendation:
Risk Management – Identifying, managing and mitigating project risk
Issues Management – Identifying, tracking managing and resolving project issues
Reporting – Proactively disseminating project information to all stakeholder s(a good web based project dashboard will do the trick)
Scope Management – Proactively managing scope to ensure that only what was agreed to is delivered, unless changes are approved through scope management
Forecasting project trends – Defining and collecting metrics to give a sense for how the project is progressing and whether the deliverables produced are acceptable
Tracking – Managing the overall work-plan to ensure work is assigned and completed on time and within budget
Monitor resources (e.g. allocation, movement, skill matrix, roles and responsibilities)
Define Development Methodology
Managing integrations & dependencies (documentation, shared infrastructure etc.)
Standardization, rationalization and training of processes & procedures (e.g. customer escalations & patches, customer enhancement request, beta or EA plans etc.)
Manage projects postmortem reviews
There are many things to be said on the project manger role and I know god is in the details Kalish but I was told that my blog posts should be much shorter so I will end it here and I reserve the right to post about it again if needed… (e.g. Scrum-Master vs. PMO post will come real soon)
Good Luck Yonit! ;-)
* The term “Professional” should imply that this role isn’t trivial or intuitive as it might sounds or implemented in many organizations
** All the ‘bold**’ words should have “rang the complexity bell” – it will never be easy (or straight forward) and will require a bundle of emotional intelligence
*** When according to the same statistics 90% of projects do not meet time/cost/quality targets.