This blog post is part of a chapter from an e-book that we are working on at this time. The e-book is a simulation of how to apply a project management method (CAM2P
Project planning is a challenging topic for many reasons. Consequently, it is important to understand this chapter and concepts before one can move into the sample project.
- Some practitioners think planning is a phase, yet planning is more about repeated processes rather than a once-off time-bound phase.
- Other practitioners think there is only one plan per project; however, there should be at least one plan for every phase or stage since the planning processes do repeat with every stage.
The earlier chapter addressed these points, however, there is one more area of potential confusion.
Is there one plan, the ‘… … plan’ per phase, or more?
If we are not mistaken, the first version of the PMBOK® Guide considered two plans, a project management plan and a project plan. In later versions, the two plans merged. The current fifth edition of the PMBOK® Guide has one ‘project management plan’, which is for the project or phase. This project management plan include subsidiary plans in each knowledge area.
If one considers the PMBOK® Guide planning processes and truly understand them, one will notice that there are two types of planning processes, two sub-groups.
There are processes (one in each knowledge area) that focuses on the management of the knowledge area. For example “Plan Scope Management” (The Project Management Institute, 2013) is about how to collect requirements, how to develop the scope statement, how to create the work breakdown structure, how to validate scope, and how to control scope. In other words, the planning process address ‘how to’ do the other processes within the same knowledge area.
The same applies for all knowledge areas. Consequently, there are ten management planning processes; out of the twenty four in the planning process group.
Each of the other fourteen planning processes is about ‘doing’ and producing an ‘output’.
For example, staying with scope management, ‘doing’ the “Collect Requirements” process is about performing analysis, talking with stakeholders, and collecting all of the requirements for the phase, or the project, then documenting these requirements.
Next, consider “Define Scope” process; ‘doing’ the process is to develop the scope statement. The same applies to all of the other knowledge areas and planning processes.
The Two Sub-Groups
Bringing in the concepts of the two sub-groups together, let’s consider the risk management area.
The “Plan Risk Management” process is about ‘how to’ identify, analyze, respond, and monitor and control risks on the project, or phase. Therefore, this process is a management planning process from Sub-Group 1.
Next, there are four risk management processes that are part of Sub-Group 2 and these are the ones for identifying, analyzing, and responding to risks. Zooming in on the “Identify Risks” process it is about ‘doing’ the work to identify all potential risks on the phase, or the project. The same is true for the other processes, they are about ‘doing’ the work of those processes.
 There are also “Project Documents” that related to planning (The Project Management Institute, 2013).
 There are ten knowledge areas in the fifth edition of the PMBOK® Guide.
 There are 24 planning processes (out of a total of 47) per the PMBOK® Guide, fifth edition.
 All the names of the processes that are used here are per the PMBOK® Guide fifth edition, copyright and all rights reserved to PMI (The Project Management Institute, 2013).
 ‘How to’ may include who, when, what … if applicable.
 There are two processes related to analyzing risks, one is qualitative analysis and the second is quantitative analysis.