Project Management Process Groups
Open in the Padhaiko app4.1 Project management processes
A process is a set of interrelated actions and activities performed to create a pre-specified product, result, or service. Every project management process is described by its Inputs, Tools and Techniques, and Outputs (ITTO).
The Five Project Management Process Groups (PMI)
PMI organizes project management processes into five logical Process Groups, linked closely to the Deming Plan–Do–Check–Act (PDCA) quality cycle:
- Initiating Process Group: Defines a new project or a new phase by obtaining authorization to start (e.g., creating the Project Charter and identifying stakeholders).
- Planning Process Group: Establishes the total scope, refines objectives, and defines the course of action (WBS, schedule, budget, quality, risk, procurement, and communication plans). Aligns with Plan.
- Executing Process Group: Completes the work defined in the project management plan to satisfy project specifications, coordinating people, resources, and vendors. Aligns with Do.
- Monitoring and Controlling Process Group: Tracks, reviews, and regulates progress and performance; identifies areas needing changes and initiates corresponding corrective/preventive actions. Aligns with Check & Act.
- Closing Process Group: Formalizes acceptance of the product/phase, closes contracts, archives lessons learned, releases resources, and brings the project or phase to an orderly end.
| Process Group | Core Objective | Typical Time / Effort Share | Key ICT Project Outputs |
|---|---|---|---|
| 1. Initiating | Authorize project/phase and align stakeholders | Project Charter, Preliminary Stakeholder Register | |
| 2. Planning | Define scope, schedule, budget, risks, and baselines | Project Management Plan, WBS, Network Schedule, Cost Baseline, Risk Register | |
| 3. Executing | Build deliverables, manage team, assure quality, procure | Working Software/System Deliverables, Quality Audit Results, Vendor Contracts | |
| 4. Monitoring & Controlling | Measure variance, control changes, validate scope | (continuous) | Work Performance Reports, Approved Change Requests, EVM Forecasts |
| 5. Closing | Obtain formal sign-off, close contracts, capture lessons | Final Product Acceptance, Closed Procurements, Lessons-Learned Archive |
4.2 Overlaps of process groups in a phase
A common exam misconception is treating the five Process Groups as sequential project phases (like Waterfall stages). In reality, Process Groups are NOT project phases—they are overlapping streams of activity that repeat inside every phase of a multi-phase project.
Process Group Interactions Within a Phase
Within any single project phase (e.g., Requirements, Architecture, Build, or Rollout):
- Initiating peaks near the start of the phase to authorize phase entry, then tapers off.
- Planning ramps up early, peaks before full execution, and continues via progressive elaboration when changes arise.
- Executing rises steadily and consumes the largest share of effort and resources during the middle of the phase.
- Monitoring and Controlling spans the entire phase from start to finish, wrapping around all other groups to track baselines and process change requests.
- Closing ramps up near the end of the phase to verify exit criteria and hand over deliverables to the next phase (or final operations).
Level of
Activity
^
| *************** <-- Executing (highest peak)
| **** ****
| ***--- Planning ----*** ***
| *** **** **** *** ***
| **Initiating** --Monitoring & Controlling (spans whole phase)--
| * **** **** Closing **
+----------------------------------------------------------> Time
Start of Phase End of PhaseIterative Feedback Loops Across Process Groups
- Planning Executing Monitoring & Controlling: As the team executes tasks, Monitoring & Controlling compares actual progress against baselines; variances trigger change requests or rolling-wave replanning, feeding updated plans back into Executing.
- Phase-to-Phase Handoffs: The Closing outputs of Phase (e.g., signed-off System Architecture Specification) become key inputs to the Initiating processes of Phase (e.g., Software Construction).
4.3 Mapping of project management process groups to area of knowledge
Every project management process belongs to one Process Group (when it happens in the management cycle) and one Knowledge Area (what subject domain it manages). This two-dimensional matrix forms the core map of PMBOK.
| Knowledge Area | Initiating | Planning | Executing | Monitoring & Controlling | Closing |
|---|---|---|---|---|---|
| Integration | Develop Project Charter | Develop Project Management Plan | Direct & Manage Project Execution | Monitor & Control Project Work; Integrated Change Control | Close Project or Phase |
| Scope | — | Plan Scope Management; Collect Requirements; Define Scope; Create WBS | — | Scope Verification (Validate Scope); Scope Control | — |
| Time (Schedule) | — | Plan Schedule Management; Define Activities; Sequence Activities; Estimate Resources; Estimate Durations; Develop Schedule | — | Schedule Control | — |
| Cost | — | Plan Cost Management; Estimate Costs; Determine Budget | — | Cost Control (EVM) | — |
| Quality | — | Plan Quality Management | Quality Assurance | Quality Control | — |
| Resource (HR) | — | Plan Resource Management; Estimate Activity Resources | Acquire, Develop & Manage Project Team | Control Resources | — |
| Communications | — | Plan Communications Management | Manage Communications (Information Distribution) | Monitor Communications (Performance Reporting) | — |
| Risk | — | Plan Risk Management; Identify Risks; Qualitative & Quantitative Risk Analysis; Plan Risk Responses | Implement Risk Responses | Monitor & Control Risks | — |
| Procurement | — | Plan Purchases & Acquisitions; Plan Contracting | Request Seller Responses; Select Sellers | Administer Procurements (Contract Administration) | Close Procurements (Contract Closure) |
| Stakeholder | Identify Stakeholders | Plan Stakeholder Engagement | Manage Stakeholder Engagement | Monitor Stakeholder Engagement | — |
Worked Out Examples
4.1
Process Group Effort Distribution Across a Two-Phase ICT Project: A university ERP rollout is divided into two sequential phases:
- Phase 1 (Requirements & Architecture): total budget
- Phase 2 (Development & Deployment): total budget
The PMO's historical benchmark splits management and delivery effort inside every phase across the five Process Groups as follows: Initiating , Planning , Executing , Monitoring & Controlling , and Closing .
- Calculate the person-hours allocated to each Process Group in Phase 1 and Phase 2.
- Compute total Planning hours and total Monitoring & Controlling hours across the entire project, and explain why Monitoring & Controlling hours must be budgeted continuously in both phases.
Allocating Phase 1 () and Phase 2 () across Process Groups:
Computing project totals and explaining continuous M&C:
- Total Planning hours .
- Total Monitoring & Controlling hours .
- Why M&C runs in both phases: Process Groups overlap inside each phase rather than running once for the whole project. Continuous M&C in Phase 1 prevents incomplete requirements from leaking into Phase 2, and continuous M&C in Phase 2 tracks coding velocity, quality defects, and change requests through deployment.
- Phase 1 (): Initiating , Planning , Executing , M&C , Closing .
- Phase 2 (): Initiating , Planning , Executing , M&C , Closing .
- Totals: Planning , M&C . Both phases repeat all five overlapping Process Groups so defects and scope drift are caught early in each phase.
4.2
Tracing a Mid-Project Requirement Change Across Process Groups & Knowledge Areas: During the coding phase of a mobile banking app (Executing), the central bank issues a new mandate requiring two-factor biometric login. Trace the exact sequence of Process Groups and Knowledge Areas triggered to handle this mandate properly without breaking project baselines.
Monitoring & Controlling (Change Intake & Impact Analysis):
- The PM logs a formal Change Request under Monitor & Control Project Work (Integration).
- Under Perform Integrated Change Control (Integration), the PM and Change Control Board (CCB) evaluate impacts across Scope (new biometric stories), Time (schedule delay), Cost (extra developer hours), and Risk (OS compatibility issues).
Planning (Updating Baselines) Executing Monitoring & Controlling:
- Once the CCB approves the change, Planning processes update the WBS (Create WBS, Scope), activity sequence/schedule (Schedule Development, Time), budget (Cost Budgeting, Cost), and test plans (Quality Planning, Quality).
- Executing (Direct & Manage Project Execution, Integration) implements and tests the biometric module.
- Monitoring & Controlling (Scope Verification, Scope; Quality Control, Quality) verifies the deliverable against acceptance criteria before phase closure.
The change moves iteratively: Executing (mandate surfaces) Monitoring & Controlling (Integrated Change Control assesses impact & CCB approves) Planning (updates Scope, Time, Cost, and Quality baselines) Executing (builds the feature) Monitoring & Controlling (verifies quality and scope acceptance).
Exercises
Practice Exercises — Project Management Process Groups
Name and briefly explain the five Project Management Process Groups defined by PMI, and map them to the Plan–Do–Check–Act (PDCA) cycle.
Five Process Groups:
- Initiating: Authorizes the project or a new phase and identifies key stakeholders.
- Planning: Establishes scope, objectives, and detailed action plans across schedule, cost, quality, and risk (Plan).
- Executing: Performs the planned work and coordinates teams/vendors to produce deliverables (Do).
- Monitoring & Controlling: Tracks performance, compares actuals to baselines, and manages change requests (Check & Act).
- Closing: Formalizes acceptance, closes contracts, archives lessons learned, and releases resources.
The five Process Groups are Initiating, Planning (PDCA Plan), Executing (PDCA Do), Monitoring & Controlling (PDCA Check & Act), and Closing.
Explain why Process Groups are not project phases, and describe how the five Process Groups overlap within a single project phase.
Why Process Groups are not phases: Project phases (e.g., Feasibility, Design, Implementation, Testing) are chronological divisions of the life cycle, whereas Process Groups are logical management groupings that repeat inside each phase.
Overlapping behavior inside a phase: Initiating peaks at phase entry; Planning peaks early and continues iteratively; Executing consumes the highest effort mid-phase; Monitoring & Controlling spans the entire phase from start to end; Closing peaks near phase exit to verify deliverables and feed inputs to the next phase.
Process Groups are overlapping management activities repeated inside every project phase—not sequential stages. Within each phase, Executing peaks mid-phase while Monitoring & Controlling runs continuously across Initiating, Planning, Executing, and Closing.
Using the PMI Process Group–Knowledge Area mapping matrix, identify:
- Which Knowledge Area has processes in all five Process Groups?
- Which two processes belong to the Initiating Process Group?
- Why do Scope, Time, and Cost have no processes in the Executing column?
Answering from the PMI mapping matrix:
- Integration Management is the only Knowledge Area spanning all five Process Groups (Develop Project Charter, Develop PM Plan, Direct & Manage Execution, Monitor & Control Work / Integrated Change Control, Close Project or Phase).
- Initiating contains Develop Project Charter (Integration) and Identify Stakeholders (Stakeholder).
- Scope, Time, and Cost establish baselines during Planning and track/control variances during Monitoring & Controlling; physical work execution is coordinated centrally under Integration's Direct and Manage Project Execution.
- Project Integration Management.
- Develop Project Charter and Identify Stakeholders.
- Physical task execution is coordinated under Integration (Direct and Manage Project Execution), while Scope, Time, and Cost focus on Planning baselines and Monitoring & Controlling variances.
Map each of the following ICT project activities to its Process Group and Knowledge Area: (a) Signing the formal project authorization document; (b) Breaking deliverables into a Work Breakdown Structure (WBS); (c) Running automated regression tests on a completed module; (d) Evaluating a vendor proposal and awarding a cloud contract; (e) Archiving lessons learned after final client sign-off.
Mapping each activity:
- (a) Formal authorization Initiating / Integration (Develop Project Charter).
- (b) Creating WBS Planning / Scope (Create WBS).
- (c) Testing completed module Monitoring & Controlling / Quality (Quality Control).
- (d) Selecting cloud vendor Executing / Procurement (Select Sellers).
- (e) Archiving lessons learned after sign-off Closing / Integration (Close Project or Phase).
(a) Initiating / Integration; (b) Planning / Scope; (c) Monitoring & Controlling / Quality; (d) Executing / Procurement; (e) Closing / Integration.
An ICT infrastructure upgrade phase is budgeted at engineering hours distributed across Process Groups as: Initiating , Planning , Executing , Monitoring & Controlling , and Closing .
- Compute the hours allocated to Planning, Executing, and Monitoring & Controlling.
- What percentage and total hours of the phase budget are devoted to Planning plus Monitoring & Controlling combined?
Computing individual Process Group hours:
Combined Planning + Monitoring & Controlling share:
- Planning , Executing , Monitoring & Controlling .
- Combined Planning + M&C ().