The five process groups are a model of how project work is organised in PMBOK language: initiating, planning, executing, monitoring and controlling, and closing. They are not five phases you march through once — and they are not the same thing as the exam's scoring domains.
The five groups as a process model
Initiating authorises the work and names the manager: charter, high-level stakeholders, a reason the project exists. Planning builds the baselines and the approach — scope, schedule, cost, quality, risk, resources, communications, procurement, and how you will engage people. Executing is the doing and the leading. Monitoring and controlling compares reality to the plan and triggers change. Closing confirms acceptance, hands over, and releases the team.
In a predictive project the groups are easier to see as a sequence. In agile work the same ideas still happen: you still authorise, still plan the next slice, still deliver, still inspect, still close an increment or a release. The cadence is shorter. The names in the room may be backlog, sprint, and review. The exam expects you to recognise the purpose, not to demand a Gantt.
Monitoring and controlling is not a phase after executing. It runs alongside. If you only 'control' when a milestone explodes, you were not controlling. You were surprised. The model puts that loop in parallel on purpose.
They overlap; they are not a staircase
Planning does not end on a date. A change to scope re-enters planning. A new stakeholder in month six re-enters initiating work for that person. Closing one phase can sit next to executing another. Drawing five boxes in a line is a training poster. Real projects loop.
When a question describes work, ask which group's purpose is in play. A sponsor asking for a new product line mid-project is not 'just execute.' You are back in initiating and planning for that slice, plus change control if a baseline exists. Candidates who only see the loudest activity pick the loudest wrong answer.
Do not force every scenario into a group name if the question is really about a domain behaviour — coaching a team, navigating a compliance change, choosing a hybrid approach. The process model helps you structure delivery. The exam also tests whether you can lead people and read the business context.
Process groups versus exam domains
Process groups describe a flow of work. Domains describe what the exam scores: people skills, process skill, and business-environment skill. A single scenario can sit in Executing as a process-group idea and in People as a domain item. Study both maps. Do not collapse them into one list to memorise.
If you trained on older materials that treated the exam as 'know the 49 processes,' update your mental model. Those processes are still a useful catalogue of what PMs do. The current sitting is built from the ECO. Match your practice questions to domains and life cycles, not only to process-group trivia.
Use the groups as a checklist when a scenario feels messy: has this work been authorised? Is there a plan for this change? Are we delivering or still debating? Are we comparing to a baseline? Has anyone accepted the output? That sequence finds the missing step more reliably than rereading a definition.
Summary & next steps
Five groups: initiate, plan, execute, monitor and control, close. They overlap and repeat. They are a process model, not the exam's domain structure — learn both.
Next: knowledge areas — the other half of the PMBOK map, and how to use them without turning study into a flashcard factory.