In our Plan-Do-Check-Act (PDCA) series, we’ve seen how the cycle adapts to different domains—Lean for business, Agile for software, and PACE for data science. Another field where PDCA shows up clearly is project management, through the PMBOK Guide published by the Project Management Institute (PMI). PMBOK organizes projects into five process groups that align closely with PDCA. At this site we have a series of posts on project management startig with Project Management Introduction.

The Five PMBOK Process Groups

PMBOK (Project Management Body of Knowledge) structures projects into these groups:

• Initiating: Define the project, identify stakeholders, and secure approval to begin.
• Planning: Develop scope, schedule, cost estimates, risk management, communications, procurement, and quality plans.
• Executing: Carry out the plan by managing teams, resources, and deliverables.
• Monitoring & Controlling: Track progress, manage changes, and ensure objectives are being met.
• Closing: Formally complete the project, deliver the results, and capture lessons learned.

Mapping PMBOK to PDCA

When viewed through the PDCA lens, PMBOK becomes a scaled-up version of the cycle:

• Plan: Initiating and Planning
• Do: Executing
• Check and Act: Monitoring & Controlling, and Closing

This mapping shows that PDCA is not just a simple cycle but the foundation of structured project management methodologies. PMBOK expands on the details, adding rigor in areas like risk management, stakeholder communication, and quality assurance.

Why It Matters

Projects—especially large and complex ones—require more detail than a simple PDCA loop. PMBOK provides that detail while still following the same rhythm: plan thoroughly, execute effectively, monitor constantly, and adapt as needed. By framing PMBOK within PDCA, we can see the continuity between simple improvement cycles and professional project management standards.

An Example in Action

Consider an IT department rolling out a new company-wide software tool. They initiate the project by defining goals and gaining leadership approval. In planning, they establish scope, timelines, and risk strategies. Execution is the rollout itself—training staff, migrating data, and launching the tool. Meanwhile, the team monitors and controls by tracking adoption rates, resolving issues, and managing changes. Finally, during closing, they evaluate outcomes, document lessons learned, and formally hand over responsibility to operations.

Closing Thoughts

PMBOK illustrates how PDCA underpins even the most formal project management approaches. By expanding and formalizing the cycle, it ensures that projects stay aligned with objectives, risks are managed, and learning is captured for future work. This makes PMBOK a natural extension of our PDCA series—showing how a simple cycle can scale up to guide complex, real-world projects.