Develop Project Management Plan

Develop Project Management Plan

0 1132

Understanding the development of a project management plan

To develop a project management plan it is important to understand that the very term initiates the planning process of the project which simply means that, the project management plan is a part of the planning process. There are certain inputs, tools and output available for our understanding of the process. Under inputs, there is the project charter. Then you have the enterprise environmental factors and organizational process asset. These factors become crucial in the process. In the next category of tools and techniques, expert judgement and facilitation techniques remain the same.

A project communication plan results into an output of communication management plan, similarly develop project management plan results into an output of project management plan. The emphasis on various inputs and outputs will enable you to co-relate why the process is needed and what the process is all about. This understanding will help in excelling PMP® exams with sheer assurance.

What is a Project Management Plan?

A project management plan very clearly defines how the project will be done and how it can be executed, monitored, controlled and closed. It’s a plan on how to manage, coordinate and integrate all the different knowledge areas and processes within a project.

In order to create a project management plan there are different outputs which are a collection of subsidiary project plans. They are namely,

  • Scope Management Plan– A Scope management plan defines how the project will be planned, managed and controlled.
  • Requirement Management Plan– It defines how the project requirements will be defined, gathered and managed.
  • Schedule Management Plan– It defines how the project schedule will be created and managed.
  • Cost Management Plan– It details how the project cost will be planned for, estimated, budgeted and then monitored and controlled.
  • Quality Management Plan– This defines what quality means to the project and it how it can achieve the desired quality.
  • Process Improvement Plan– It aims to eliminate non-added value activity, eliminate waste and how there can be improvements in terms of execution and management.
  • Human Resource Plan– It defines how the project team members will be brought on the project,managed and released from the project. It also defines team training, safety issues, roles and how the project’s reward and recognition system will operate
  • Communication Management Plan-This defines who will get what information, and in what modality the communication will take place.
  • Risk Management Plan-It is an uncertain event or condition that may affect the project’s outcome. It defines how the project will manage risk.
  • Procurement Management Plan-It controls how the project will be allowed to contract goods and services.
  • Change Management Plan– It is part of the control scope process which details the procedures for entertaining change requests and how they are managed and controlled.
  • Configuration management plan-This defines how changes to the features and functions of the project deliverable, the product scope may enter the project.
  • Staffing Management Plan-This specifically addresses how human resource requirements will be met in the project. It can address staffing, procurement of resources, etc.
  • Risk response plan– It defines the risk responses that are to be used in the project for both positive and negative risks.
  • Milestone list– It details the project mile stone and their attributes.
  • Resource calendar– It defines when people, facilities and equipment are available to contribute to the project.
  • Cost baseline– It is the aggregated cost of all the work packages with a project.
  • Quality baseline– It documents the quality objectives of the project including metrics for stakeholder acceptance.
  • Scope baseline– This is a blend of 3 project documents- Project scope statement, the WBS, WBS dictionary.
  • Risk register– This is a centralized database consisting of outcome of all the other risk management process.
  • Issue log– This is a log that has issues registered by the issue owner along with a deadline to resolve. In time, the outcome is also updated.
  • Assumption log– An assumption is believed to be true but it hasn’t been proved yet.
  • Change log– It has project changes recorded in the log. Time, cost and risk details of each change is also entered in the log.

In order to carry out any kind of project, it is crucial to understand the above mentioned plans as these ultimately play a role in different areas of the project.