The Ten PMBOK Knowledge Areas | What Changed in Later Editions, and How to Use Them
Shusaku Yosa
Look up the ten PMBOK knowledge areas and you will run into the note that they were abolished in the 7th Edition. Yet the classification is still in daily use, and there is value in knowing it. This article lists the ten knowledge areas and sets out how their status has changed across editions.
First: This Is Not the Current Framework
Setting the context straight.
The ten knowledge areas belong to the PMBOK Guide up to the 6th Edition. The 7th Edition, published in 2021, dropped the concept and replaced it with eight performance domains and twelve principles.
The 8th Edition changed things again. The principles were reduced to six, the performance domains to seven, and processes and focus areas were reintroduced. It is a partial return to the specificity of the 6th Edition, prompted by feedback that the 7th was too abstract to apply.
Why they are still worth knowing
Abolished does not mean useless. There are three reasons.
- Conversations in practice still run on this classification.
- Many organisations still have internal standards and templates built on the 6th Edition.
- As a checklist of what needs managing, it still works.
The third is the practical one. To check which areas a project is neglecting, a ten-way split remains usable.
The Ten Knowledge Areas
As defined in the 6th Edition.
1. Integration management
Pulls the other nine together and keeps the whole coherent. Producing the project charter and deciding on change requests sit here.
2. Scope management
Defines what is in and what is out. Building the WBS belongs here.
3. Schedule management
Sets the order and duration of work and tracks progress. Renamed from time management in the 6th Edition.
4. Cost management
Estimates the budget and controls how it is spent, including contingency reserves.
5. Quality management
Confirms the deliverables meet the requirements. Settling the evaluation criteria up front is the core of it.
6. Resource management
Secures and allocates people and equipment. Broadened in the 6th Edition to cover more than human resources.
7. Communications management
Designs who is told what, and when. Deciding on meeting structures and reporting formats belongs here.
8. Risk management
Identifies what could go wrong and decides the response in advance. It covers opportunities as well as threats.
9. Procurement management
Manages what is bought externally and what is outsourced, including the choice of contract type.
10. Stakeholder management
Identifies the parties involved, understands their expectations, and secures agreement. A relatively recent area, split out in the 5th Edition.
Using Them in Practice
There is no need to manage all ten equally. Which areas carry weight depends on the nature of the project.
Projects with heavy outsourcing
Procurement and scope dominate. Place an order while the boundaries stay vague and the conversation turns to extra costs later.
Projects spanning departments
Stakeholder and communications dominate. When something is technically simple yet will not move, these two are usually the reason.
Projects without precedent
Risk and schedule dominate. Accepting that estimate accuracy will not improve, the work becomes designing where to place the slack.
Using it as a checklist
The most practical use is walking the ten areas once at the planning stage. Simply asking in turn — does this project involve procurement? are the quality criteria settled? — surfaces the gaps.
Even experienced PMs have areas they are strong and weak in. Keeping the list to hand stops you being pulled by your own tendencies.
What Changed in the 7th Edition
Knowledge areas gave way to performance domains.
The difference is a shift from what you manage to what state you are aiming for. Knowledge areas classified the objects of management; performance domains are defined as areas of activity for producing outcomes.
Behind it lies the spread of agile ways of working. The premise of settling a plan and then executing it in order broke down, and the guide moved from prescribing procedures to offering criteria for judgment.
The 7th Edition, though, drew comments that it was too abstract to apply. The reintroduction of processes in the 8th Edition is a response to that.
Frequently Asked Questions
Which edition should I learn now?
It depends on the purpose. If you are pursuing certification, check which edition the exam follows. If you are referring to it in practice, matching whichever edition your organisation's standards and templates assume is the realistic choice.
Are the knowledge areas unusable now?
As a classification they remain useful. They are simply no longer the current framework; the fact that a project has ten areas needing management has not changed. When explaining externally, though, say which edition you are referring to.
Do I have to cover all ten?
No. On a small engagement with no procurement, skip that area. Once filling in all ten becomes the objective in itself, all you generate is paperwork.
Which area gets missed most?
Stakeholder and communications. Schedule and cost are visible as numbers so they get attention naturally, but who needs to be told what tends to be deferred. The causes of stalled projects concentrate in these two.
What Knowing the Framework Will Not Solve
Memorising the knowledge areas will not make the project in front of you run. What a framework gives you is a checklist against oversights, and a shared vocabulary.
Whether you can actually see the progress depends on having a mechanism that collects the information. Xtrategy manages campaign schedules alongside budget and KPIs on a single screen.
Summary
- The ten knowledge areas belong to the 6th Edition. The 7th replaced them with eight performance domains.
- The 8th Edition reduced the principles to six, the domains to seven, and brought processes back.
- Even so, the list still works as a checklist of areas to manage.
- Do not weight all ten equally; let the nature of the project decide.
- The most commonly missed areas are stakeholder and communications.
- When explaining externally, state which edition you are working from.
PMBOK keeps being revised, but the fact that projects have areas people routinely overlook does not change. Rather than being pulled around by edition differences, use the list as an instrument for walking through everything once at the planning stage.