A blog from the Professor of Practical Project Management

Month: April 2014

Staff management planning is important to prevent or minimize the battle for resources, which is the number one problem for most Project Managers. The Staff Management section of the Project Management Plan addresses the following:

• Describes how the project team will be formed, developed, and managed. This includes procedures on releasing and adding team members

Identification of roles can occur even before you know the specific names that will fill those roles. It is based on the parameters and demands of the project. Examples of roles are “Executive Sponsor”, “Project Manager”, “Business Analyst”, “Tester”, “Contract Reviewer”, etc.

Defining the responsibilities of each role is important to minimize the chance of two unwanted outcomes: (1) two or more people are duplicating effort because they all think they own it; (2) key responsibilities are not taken on by anyone because they think it is owned by someone else.

Defining the reporting relationships is important as you will need to know who to go to for permissions and escalations.

Understanding how the project team will be formed is important to make sure you will have the roles filled on time, for the time needed, and with the skill sets required to meet the schedule.

The Project Manager also has a responsibility to develop the project team members soft and hard skills so they become more valuable to the organization and increase their personal job satisfaction. This development can take many forms. It can be formal training, coaching or show by example. You can discuss who will be targeted for development with the managers of the project team members and define what form it will take.

Advertisements

Share this:

Like this:

Depending on the organization you work for and the project you are working on, the Project Manager may or may not be managing the project budget and costs. If you are tasked to do this, include Cost Management as part of your Project Management Plan.

The Cost Management Plan addresses the following:

• Defines what resources (human, hardware, software, services, facilities) will be considered part of the project costs and when it will be base-lined

• Defines how costs will be reported and who will approve invoices and internal costs

• Defines the magnitude of cost changes that will be subject to formal change management

• Includes a plan for change management: How change is requested, authorized, and documented

• Reference the Project Charter for the priority of Cost in the triple constraints

If cost is the highest priority in your project triple constraints, Cost Management becomes a critical activity. You want to not only record and track costs that have already been incurred, but you also must do new cost projections on a regular basis. As more is known about a project, cost projections will become more accurate.

A former manager of mine once told me that if your costs incurred + future projected costs exactly equals your budget, then you are not doing accurate cost projections. This is based purely on the laws of probability. The probability of your actual and projected costs EXACTLY matching a budget created before the project began is very low.

Like this:

Before I dive into Schedule Management I want to note the difference between the schedule and what many refer to as “the project plan”. You will often hear the Microsoft Project artifact referred to as “the project plan”. In reality, it is only the project schedule. The Project Plan is the combination of the Project Management Plan (being discussed here) and the Project Activity Plan (or Work Breakdown), which will be discussed in future posts. I encourage you to use this terminology correctly.

The Schedule Management Plan addresses the following:

• Indicates how the project schedule will be created (who will be the sources of start/end dates and effort), when it will be base lined and lists any scheduling constraints