Key takeaway
- Learn the five project management process groups, a reusable checklist and how the PMBOK Guide changed in its seventh and eighth editions. Plain guide.
What are project management processes?
Project management processes are the repeatable steps a team uses to take work from an idea to delivery. The five groups most people mean are initiating, planning, executing, monitoring and controlling, and closing. A checklist turns those groups into questions someone must answer before the next step starts.
This guide gives you the five groups, a checklist you can reuse, and a note on how the standard has changed. If you lead product work, read it alongside our guide to project and product management with agentic AI.
What are the five project management process groups?
Each group has one job. The table shows what it produces and the question it answers.
| Group | What happens | Question it answers |
|---|---|---|
| Initiating | Agree the purpose, sponsor and high-level goals | Why are we doing this, and who decides? |
| Planning | Define scope, schedule, budget, resources and risks | What exactly will we deliver, and how? |
| Executing | Do the work and coordinate the team | Is the work getting done as planned? |
| Monitoring and controlling | Track progress and handle changes | Are we on track, and what must change? |
| Closing | Hand over deliverables and review lessons | Did we deliver, and what do we keep for next time? |
Initiating
Initiation sets the direction. The sponsor and project manager agree the purpose, the main stakeholders, and what success means. Write down the goals and the time and resources the organisation is willing to commit before any detailed planning begins.
Planning
Planning documents the objectives, scope, timeframe, resources and deliverables, and the risks that could affect them. Keep the plan short enough that people read it. A requirement traceability matrix helps by linking each requirement to the deliverable built to meet it, and a functional specification document records what users expect the system to do.
Executing
Executing is where the team builds. The manager assigns work, removes blockers and keeps stakeholders informed. Poor execution wastes time and budget even when the plan is good, so agree early how the team reports progress.
Monitoring and controlling
Monitoring means observing progress against the plan. Controlling means acting when the numbers drift, for example by changing scope, adding people or moving a date. Run this alongside execution, not after it. When a delivery problem becomes an outage or a security event, hand it to your incident management process.
Closing
Closing hands the deliverables to stakeholders and records what happened. Compare the result with the original goals, scope and timeline. Capture lessons learned while the team still remembers them.
Is there a project management checklist you can reuse?
Yes. Use the list below and assign one owner and one review date to every line.
| Checklist item | What to confirm | Typical owner |
|---|---|---|
| Vision, goals and objectives | Problem statement, mission, expected outcome and who is affected most | Sponsor and project manager |
| Stakeholders | Everyone with an interest is named, including the project manager | Project manager |
| Requirements | Specifications are gathered and fit the type of project | Business analyst or product lead |
| Project plan | Tasks, deliverables, risks and the chosen delivery framework | Project manager |
| Budget | Estimates start broad and are refined; inclusions and exclusions are explicit | Project manager and finance |
| Resource allocation | Skills match the work, with a plan for any gap such as hiring or contract staff | Delivery lead |
| Schedule | Dates follow the plan and the resources actually available | Project manager |
| Team communication | Channels, cadence and escalation path are agreed | Project manager |
| Health check of progress | Regular review of scope, schedule, budget and risk | Project manager and sponsor |
How do you plan resources when skills are short?
If the plan needs six developers and you have four with the right skills, decide early. Options are to hire, bring in contract staff, narrow the scope or move the date. Raise it at planning, not during execution.
Which delivery framework should you choose?
Choose the framework after you understand the project. The Agile Manifesto principles call for early and continuous delivery, and for the team to reflect and adjust at regular intervals. Work with stable, well-understood scope often suits a plan-driven approach, while uncertain scope suits short iterations.
How has the PMBOK Guide changed?
The five groups above are the classic structure. PMI has since moved away from presenting the guide only as process groups, so check which edition your organisation follows.
| Edition | What PMI says | Source |
|---|---|---|
| Sixth edition | Process-group based; PMI stopped selling it after 31 March 2022, though owners may keep using it | PMI public FAQs, July 2021 |
| Seventh edition (ANSI/PMI 99-001-2021) | Centres on principles and performance domains; references process groups but no longer fully includes them | PMI public FAQs, July 2021 |
| Eighth edition (ANSI/PMI 99-001-2025) | Six principles and seven performance domains; initiating, planning, executing, monitoring and controlling, and closing appear as focus areas | PMI table of contents for the PMBOK Guide, Eighth Edition |
The seven performance domains in the eighth edition are governance, scope, schedule, finance, stakeholders, resources and risk. The same table of contents lists an appendix on artificial intelligence. Confirm the current edition and wording on the official PMI page before you cite it in a policy.
What are the trade-offs, and when is a checklist not enough?
A checklist stops steps being missed, but it does not judge quality. It will not tell you that a requirement is wrong or that two teams disagree about scope. For larger programmes add a risk review, a change-control rule and one named decision owner.
Teams that deliver in sprints can keep the same checks and run them each cycle. ElixirClaw Agent Scrum describes itself, according to its site, as agentic AI for Agile delivery. For routine status work, see our guide to agentic workflows and keep a person accountable for each decision.
What should you do next?
Adopt the sequence in order. First, agree goals and the sponsor. Second, build the plan, budget and resource view. Third, set the review rhythm. Fourth, run the health check at every review. Fifth, hold a short closing review and keep the lessons.
If AI agents will take part in your delivery, record which decisions they may make and what policy and context they rely on. ElixirData Context OS keeps governed context, versioned policy and decision traces in one decision layer above AI agents. To map one project decision your agents should make, and the context and policy it depends on, book a Context Workshop. See what happens in the workshop.
Frequently asked questions
What are the five project management processes?
Initiating, planning, executing, monitoring and controlling, and closing. The PMBOK Guide, Eighth Edition lists these same five as focus areas, according to the PMI table of contents.
Does the PMBOK Guide still use process groups?
The seventh edition references process groups but no longer fully includes them, according to PMI's public FAQs. The eighth edition (ANSI/PMI 99-001-2025) lists the same five names as focus areas. Confirm the current wording on the official PMI page.
Do agile projects need these processes?
They need the same questions answered, usually in shorter cycles. The Agile Manifesto principles call for early and continuous delivery and for regular reflection and adjustment by the team.
What should a project management checklist cover?
Vision and goals, stakeholders, requirements, plan, budget, resources, schedule, communication and regular health checks. Add a named owner and a review date to each item.
When is a checklist not enough?
When the project has uncertain scope or many dependent teams. Then add risk reviews, change control and a clear decision owner, not only a longer list.
Follow XenonStack on LinkedIn: XenonStack on LinkedIn for new guides on agentic AI, data and platform engineering.
Ready to put AI agents to work? Explore ElixirClaw, the agentic OS platform to build, orchestrate and govern AI agents.
Explore the XenonStack platform family: ElixirData · ElixirClaw · ElixirHub · NexaStack · MetaSecure · Neural AI · AgentGRC · AgentSRE · AgentAnalyst · AgentInstruct · AgentRAI · AgentScrum · AgentSearch · AgentForce · AI Aviator · SAIF Aviator · CohortIQ · XenonStack AI · XenonStack UAE