2.3 The Five Process Groups

Where the Process Groups Live Now

PMI moved the 49 processes, the five process groups, and the ten knowledge areas out of the PMBOK Guide (the 7th edition is principles-based) and into a companion standard, Process Groups: A Practice Guide. They are still squarely on the CAPM exam, so you must know them. The five process groups are Initiating, Planning, Executing, Monitoring & Controlling, and Closing.

The Most-Missed Concept: Groups Are Not Phases

Exam alert: Process groups are NOT project phases. This single confusion costs candidates points.

A multi-phase construction project runs all five process groups inside each phase: the build phase has its own initiating, planning, executing, monitoring & controlling, and closing.

The Five Process Groups

1. Initiating

Define a new project or phase and obtain authorization to start. Core processes: Develop Project Charter and Identify Stakeholders. The project charter formally authorizes the project and grants the project manager authority to apply organizational resources — without it, the project does not officially exist.

2. Planning

Establish scope, refine objectives, and define how to achieve them. Planning is the largest group with 24 processes. It produces the project management plan (the master integrating document) plus the subsidiary plans and baselines: scope (with the WBS), schedule, cost, quality, resource, communications, risk (with the risk register), procurement, and stakeholder engagement.

3. Executing

Do the work in the plan to satisfy requirements. This is where most of the budget and effort are spent.

4. Monitoring & Controlling

Track, review, and regulate progress and performance, and manage change. This group is unique because it spans the entire life cycle and interacts with every other group. Key processes include Monitor and Control Project Work, Perform Integrated Change Control (evaluate and approve/reject change requests before any baseline changes), Validate Scope (the customer formally accepts deliverables), Control Quality (internal inspection that deliverables are correct), and the control processes for schedule, cost, resources, communications, risk, procurements, and stakeholders.

Trap: Control Quality (inspecting for correctness, Monitoring & Controlling) precedes Validate Scope (customer acceptance). Control Quality is internal; Validate Scope is the formal customer sign-off.

5. Closing

Finalize all activities and formally close the project or phase. It has just one process — Close Project or Phase — which confirms acceptance, releases resources, archives records, captures lessons learned, and obtains formal sign-off.

How the Groups Interact

The groups are not a strict sequence; they overlap and loop:

• Initiating produces the charter that triggers Planning.
• Planning produces plans that guide Executing.
• Executing produces results reviewed by Monitoring & Controlling.
• Monitoring & Controlling produces change requests that may loop back into Planning.
• Closing formalizes the accepted outputs.

Process Distribution

Memorize the order by count — Planning > M&C > Executing > Initiating > Closing — because the exam often asks you to rank groups by number of processes.

Tailoring the Process Groups

The practice guide stresses tailoring: not every project runs all 49 processes. A small, low-risk project may use a handful, while a large regulated program uses nearly all. The five process groups, however, are conceptually always present — even an agile project initiates, plans, executes, monitors, and closes, just in shorter loops. On the exam, if a scenario describes a tiny project skipping detailed planning, that reflects tailoring of processes, not the elimination of a process group.

Inputs, Tools & Techniques, and Outputs (ITTO)

Every one of the 49 processes is documented as inputs, tools & techniques, and outputs (ITTO). You do not need to memorize all ITTOs for the CAPM, but you should grasp the flow logic: the output of one process is frequently an input to another. For example, the project charter (output of Develop Project Charter) is an input to Identify Stakeholders and Develop Project Management Plan. Recognizing these handoffs answers many "what do you need before you can…" questions.

A Common Sequencing Trap

A frequent CAPM item gives a change request and asks the next step. The correct flow is: a change request is documented, then routed through Perform Integrated Change Control, evaluated (often by a change control board), and only an approved change updates the baseline and the plan. You never change a baseline directly, and you never implement an unapproved change. This protects the scope, schedule, and cost baselines from uncontrolled "scope creep."