PMBOK® Guide – Fifth Edition study map
Attribution and disclaimer
- Source structure: Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition, Newtown Square, PA: PMI, 2013. ISBN 978-1-935589-67-9.
- Marks: PMI, PMP, PMBOK, PgMP and related marks are registered trademarks of Project Management Institute, Inc.
- This page: Original educational summary for Learning Map study. Do not treat it as the standard text. For exams, audits or contractual method statements, use the official PMI publication and your organisation’s methodology.
How the Fifth Edition is organised
| Block | What it covers |
|---|---|
| Ch. 1 | Purpose, definition of a project, project management, portfolios/programmes/PMO, operations vs projects, business value, project manager role |
| Ch. 2 | Organisational influences, stakeholders and governance, team composition, project life cycle and phases |
| Ch. 3 | Process model, five Process Groups, project information flow, Knowledge Area role |
| Ch. 4–13 | Ten Knowledge Areas (47 processes): Integration through Stakeholder Management |
| Annex A1 | The Standard for Project Management (process groups with inputs/outputs) |
| Appendices | Fifth Edition changes, contributors, interpersonal skills |
| Back matter | References, glossary, index |
Good practice (Fifth Edition framing): practices that apply on most projects most of the time, tailored by the team—not a mandatory checklist for every project.
1. Introduction — core ideas
1.1 Purpose of the guide
The Fifth Edition:
- Identifies generally recognised good practice for managing individual projects.
- Promotes a common vocabulary (aligned with the PMI Lexicon).
- Distinguishes the guide (process detail, tools and techniques) from the standard in Annex A1 (process definitions, inputs and outputs).
- Points practitioners to PMI’s Code of Ethics (responsibility, respect, fairness, honesty).
Tailoring: The organisation and project team decide which processes and how much rigor apply.
1.2 What is a project?
A project is a temporary endeavour to create a unique product, service or result.
- Temporary ≠ short: it means a defined start and end (objectives met, terminated, or need gone).
- Unique ≠ no repetition: similar buildings or releases can still be distinct projects (location, stakeholders, design, constraints).
- Outcomes may be tangible or intangible; impacts can outlast the project.
Examples: new product, organisational change, systems change, research, construction, process improvement.
1.3 Portfolios, programmes and projects
| Layer | Focus |
|---|---|
| Portfolio | Collection of projects, programmes, sub-portfolios and operations managed for strategic objectives |
| Programme | Related projects managed together for benefits not available if managed alone |
| Project | Specific scope, deliverables and success criteria, often driven by programme/portfolio goals |
Organisational strategy drives prioritisation, funding and resource allocation across these layers.
1.4 What is project management?
Project management applies knowledge, skills, tools and techniques to meet requirements—via 47 processes grouped into five Process Groups:
- Initiating
- Planning
- Executing
- Monitoring and Controlling
- Closing
Typical work: requirements, stakeholder needs, communications, balancing constraints (scope, quality, schedule, budget, resources, risk). Changing one constraint usually affects others. Plans are progressively elaborated.
1.5 Organisational project management (OPM)
OPM links project, programme and portfolio practice with organisational enablers (structure, culture, technology, HR) so strategy is executed predictably.
Rough contrast:
| Dimension | Project | Programme | Portfolio |
|---|---|---|---|
| Scope | Defined, elaborated over life | Broader benefits | Org strategy–driven |
| Change | Managed/controlled | Expected inside and outside | Continuous environmental monitoring |
| Success | Quality, time, budget, satisfaction | Benefits realisation | Aggregate investment and benefits |
1.6 PMO types (Fifth Edition)
- Supportive — templates, training, lessons learned (low control).
- Controlling — compliance with frameworks and tools (moderate control).
- Directive — PMO manages projects directly (high control).
1.7 Business value and the project manager
Business value is organisation-specific (tangible + intangible). Portfolio/programme/project disciplines help convert strategy into realised value.
The project manager leads the team to achieve objectives—distinct from functional or operations managers. Competencies emphasised: knowledge, performance, personal effectiveness; interpersonal skills listed in Appendix X3 (leadership, team building, communication, negotiation, conflict, coaching, and more).
2. Organisational influences and project life cycle
2.1 Culture, communication and structure
- Culture and style are enterprise environmental factors; they shape decision rights and “how work gets done.”
- Communication capability (including remote/electronic) shapes how decisions and status flow.
- Structures affect PM authority and resource availability:
| Structure | PM authority (typical) |
|---|---|
| Functional | Little / none |
| Weak matrix | Low |
| Balanced matrix | Low to moderate |
| Strong matrix | Moderate to high |
| Projectized | High to almost total |
Composite organisations mix models (e.g. strong matrix plus occasional projectized “tiger” teams).
2.2 Organisational process assets (OPA) and enterprise environmental factors (EEF)
| OPA | EEF | |
|---|---|---|
| Nature | Plans, processes, policies, templates, lessons learned used by the organisation | Conditions not controlled by the team that constrain or enable the project |
| Examples | Change procedures, templates, historical databases | Culture, market, regulations, infrastructure, PMIS |
Both are inputs to most planning processes.
2.3 Stakeholders, governance and success
A stakeholder may affect, be affected by, or perceive themselves affected by the project. Identification is continuous. Examples: sponsor, customers/users, sellers, partners, functional managers, organisational groups, regulators.
Project governance aligns the project with organisational governance—decision rights, escalation, stage gates, acceptance criteria, change beyond PM authority.
Success is typically judged against approved baselines (scope, time, cost, quality, resources, risk)—not informal “feel.”
2.4 Project team
Roles may include PM staff, project staff, experts, customer representatives, sellers and partners. Composition: dedicated vs part-time; partnership/JV; virtual teams across time zones and cultures.
2.5 Project life cycle
A life cycle is the series of phases from start to close. Generic pattern: start → organise/prepare → carry out work → close.
Typical patterns:
- Cost/staffing rise then fall.
- Risk/uncertainty high early; cost of change rises later.
- Phases may be sequential or overlapping (fast tracking increases risk of rework).
Life-cycle styles:
| Style | Idea |
|---|---|
| Predictive | Scope, time and cost defined early; changes tightly controlled |
| Iterative / incremental | Cycles build understanding and functionality |
| Adaptive (agile) | Rapid fixed time/cost iterations; backlog; continuous stakeholder feedback |
3. Project management processes
3.1 Process idea
A process has inputs, tools & techniques, and outputs. Teams should:
- Select appropriate processes
- Adapt approach to requirements
- Engage stakeholders
- Balance competing constraints
Distinguish project management processes (this guide) from product-oriented processes (how the deliverable is built).
3.2 Process Groups (summary)
| Process Group | Intent |
|---|---|
| Initiating | Authorise project/phase; charter; identify stakeholders |
| Planning | Scope, objectives, plans, baselines; progressive elaboration |
| Executing | Perform work; manage team, quality, procurements, engagement |
| Monitoring & Controlling | Track performance; change control; forecasts |
| Closing | Formal completion; lessons learned; release resources |
Process Groups are not the same as life-cycle phases. In multiphase projects, Process Groups often recur each phase.
3.3 Project information
- Work performance data — raw observations from execution.
- Work performance information — analysed, contextualised.
- Work performance reports — packaged for decisions and awareness.
3.4 Knowledge Areas and the 47 processes
Fifth Edition maps 47 processes across 10 Knowledge Areas and 5 Process Groups. The matrix (Integration → Stakeholder × Initiating → Closing) is the navigation map for the rest of this study page and for Annex A1.
4. Project Integration Management
Purpose: Unify and coordinate all process groups and knowledge areas—trade-offs, resource allocation, consistency of plans and documents.
| Process | Process Group | One-line intent |
|---|---|---|
| 4.1 Develop Project Charter | Initiating | Authorise the project; give the PM authority |
| 4.2 Develop Project Management Plan | Planning | Integrate subsidiary plans and baselines |
| 4.3 Direct and Manage Project Work | Executing | Lead work; implement approved changes |
| 4.4 Monitor and Control Project Work | M&C | Track progress vs plan; recommend actions |
| 4.5 Perform Integrated Change Control | M&C | Review/approve/reject changes holistically |
| 4.6 Close Project or Phase | Closing | Formal end; transition; lessons learned |
Charter typical content: purpose, objectives, high-level requirements/risks, summary milestones/budget, stakeholders, success criteria, PM authority, sponsor.
Change types: corrective action, preventive action, defect repair, formal updates to controlled documents.
Practice: Keep one change log and a clear CCB (change control board) path for baseline-impacting changes.
5. Project Scope Management
Purpose: Include all work required—and only that work.
| Process | Intent |
|---|---|
| 5.1 Plan Scope Management | How scope and requirements will be defined, validated, controlled |
| 5.2 Collect Requirements | Stakeholder needs → documented requirements + traceability |
| 5.3 Define Scope | Detailed project/product description; exclusions |
| 5.4 Create WBS | Decompose to work packages; scope baseline |
| 5.5 Validate Scope | Formal acceptance of deliverables |
| 5.6 Control Scope | Prevent uncontrolled scope creep; variance analysis |
Scope baseline = approved scope statement + WBS + WBS dictionary.
Requirement classes (study aid): business, stakeholder, solution (functional/non-functional), transition, project, quality.
Practice: Maintain a requirements traceability matrix from business need → deliverable/test.
6. Project Time Management
Purpose: Timely completion via a schedule model (method + tool + data → schedule presentations).
| Process | Intent |
|---|---|
| 6.1 Plan Schedule Management | Policies, method, tool, control thresholds |
| 6.2 Define Activities | Activity list, attributes, milestones |
| 6.3 Sequence Activities | Network diagrams; dependencies; leads/lags |
| 6.4 Estimate Activity Resources | Types/quantities; resource breakdown structure |
| 6.5 Estimate Activity Durations | Analogous, parametric, three-point, reserves |
| 6.6 Develop Schedule | CPM, critical chain, resource optimisation, compression |
| 6.7 Control Schedule | Performance reviews, forecasts, updates |
Dependency types: mandatory vs discretionary; internal vs external.
PDM relationships: FS (most common), FF, SS, SF.
Compression: crashing (add cost/resources) vs fast tracking (overlap; more risk).
Agile note (Fifth Edition control): velocity, backlog reprioritisation, retrospectives.
Practice: Protect a clear critical path narrative for executives; separate contingency (known-unknowns) from management reserve (unknown-unknowns).
7. Project Cost Management
Purpose: Complete within the approved budget.
| Process | Intent |
|---|---|
| 7.1 Plan Cost Management | Policies for estimating, budgeting, control |
| 7.2 Estimate Costs | Activity cost estimates + basis of estimates |
| 7.3 Determine Budget | Cost baseline + funding requirements |
| 7.4 Control Costs | EVM, forecasts, TCPI, reserve analysis |
EVM core measures:
| Metric | Meaning |
|---|---|
| PV | Planned value |
| EV | Earned value |
| AC | Actual cost |
| SV / SPI | Schedule variance / performance index |
| CV / CPI | Cost variance / performance index |
| EAC / ETC / VAC | Estimate at/to complete; variance at completion |
| TCPI | Efficiency needed to hit BAC or EAC |
Practice: Never track spend without value of work accomplished—pair AC with EV.
8. Project Quality Management
Purpose: Meet stated needs; integrate with the organisation’s quality system and continuous improvement.
| Process | Intent |
|---|---|
| 8.1 Plan Quality Management | Standards, metrics, checklists, quality & process improvement plans |
| 8.2 Perform Quality Assurance | Audit processes; process analysis; improvement |
| 8.3 Control Quality | Inspect results; validated changes; verified deliverables |
Quality vs grade: low grade can be acceptable; low quality (defects) is a problem.
Precision vs accuracy: exactness vs correctness.
Cost of quality: prevention + appraisal (conformance) vs internal/external failure (nonconformance).
Themes: customer satisfaction; prevention over inspection; continuous improvement (PDCA); management responsibility.
Seven basic quality tools (study labels): cause-and-effect, flowchart, checksheet, Pareto, histogram, control chart, scatter diagram.
9. Project Human Resource Management
Purpose: Organise, manage and lead the project team.
| Process | Intent |
|---|---|
| 9.1 Plan Human Resource Management | Roles, org chart, staffing management plan |
| 9.2 Acquire Project Team | Negotiate, acquire, virtual teams, multi-criteria selection |
| 9.3 Develop Project Team | Skills, trust, colocation, training, rewards, Tuckman stages |
| 9.4 Manage Project Team | Performance, conflict, interpersonal skills, change requests |
RACI (responsible, accountable, consult, inform) clarifies ownership.
Conflict modes (study): withdraw, smooth, compromise, force, collaborate.
Practice: Release plan + recognition criteria written early—morale and cost both benefit.
10. Project Communications Management
Purpose: Timely, appropriate planning and flow of project information.
| Process | Intent |
|---|---|
| 10.1 Plan Communications Management | Who needs what, when, how; constraints |
| 10.2 Manage Communications | Create, distribute, store, retrieve information |
| 10.3 Control Communications | Ensure information needs remain met |
Dimensions: internal/external, formal/informal, vertical/horizontal, official/unofficial, written/oral, verbal/nonverbal.
Methods: interactive, push, pull.
Channels formula (study): (n(n-1)/2) potential paths for (n) stakeholders—limit who talks to whom.
Basic model: encode → transmit (noise) → decode → acknowledge → feedback.
11. Project Risk Management
Purpose: Increase likelihood/impact of positive events; decrease those of negative events.
| Process | Intent |
|---|---|
| 11.1 Plan Risk Management | Approach, roles, timing, categories, probability/impact definitions |
| 11.2 Identify Risks | Risk register; root causes; potential responses |
| 11.3 Perform Qualitative Risk Analysis | Prioritise by probability × impact; urgency |
| 11.4 Perform Quantitative Risk Analysis | Numeric analysis (EMV, simulation, sensitivity) |
| 11.5 Plan Risk Responses | Avoid/transfer/mitigate/accept; exploit/enhance/share/accept |
| 11.6 Control Risks | Reassess, audit, variance/trend, reserves, implement responses |
Risk attitude ingredients: appetite, tolerance, threshold.
Known risks → contingency reserve; unknown → management reserve.
Overall project risk ≠ simple sum of individual risks.
Practice: Every accepted high risk needs an owner, trigger and response—not just a register row.
12. Project Procurement Management
Purpose: Acquire products/services/results from outside the team; manage agreements.
| Process | Intent |
|---|---|
| 12.1 Plan Procurement Management | Make-or-buy; SOW; documents; source selection criteria |
| 12.2 Conduct Procurements | Bidder conferences; evaluate; negotiate; award |
| 12.3 Control Procurements | Performance, payments, claims, contract change control |
| 12.4 Close Procurements | Formal close; audits; lessons; archive |
Contract families (study):
- Fixed-price (FFP, FPIF, FP-EPA) — seller bears more cost risk when scope is clear.
- Cost-reimbursable (CPFF, CPIF, CPAF) — flexibility when scope is unclear.
- Time and materials — hybrid; control with ceilings.
Procurement shares/transfers selected risks via agreement terms.
13. Project Stakeholder Management
Purpose: Identify stakeholders; plan engagement; manage and control engagement throughout the life cycle. Stakeholder satisfaction is a key project objective.
| Process | Intent |
|---|---|
| 13.1 Identify Stakeholders | Register; analysis (e.g. power/interest) |
| 13.2 Plan Stakeholder Management | Engagement strategy vs current/desired levels |
| 13.3 Manage Stakeholder Engagement | Communicate, negotiate, resolve issues |
| 13.4 Control Stakeholder Engagement | Adjust strategies as the environment changes |
Engagement levels (study): unaware → resistant → neutral → supportive → leading.
Practice: Influence is usually highest early—invest in identification and engagement before execution peaks.
Annex A1 — The Standard for Project Management
Annex A1 restates Process Groups as the ANSI-style standard: process definitions with primary inputs and outputs (less narrative on tools than chapters 4–13). Use it when you need a compact process checklist for audits or method statements.
Process Group interactions still apply: overlapping, iterative, linked by outputs (e.g. charter → planning; accepted deliverables → closing).
Appendices (study orientation)
| Appendix | Use |
|---|---|
| X1 Fifth Edition changes | What changed vs Fourth Edition (e.g. stakeholder knowledge area emphasis, planning processes such as Plan Scope/Schedule/Cost/Stakeholder Management) |
| X2 Contributors | Attribution of volunteer development |
| X3 Interpersonal skills | Leadership, team building, motivation, communication, influencing, decision making, political/cultural awareness, negotiation, trust, conflict, coaching |
Figures and tables — how to study them
The official guide includes many ITTO (inputs, tools & techniques, outputs) figures, data-flow diagrams, org-structure charts, WBS examples, network diagrams, EVM curves, RACI, risk matrices and Process Group × Knowledge Area maps.
Learning Map approach: for each knowledge area, sketch one page: purpose → processes → 3 artefacts you will actually produce on your next engagement.
Practice pack (AI / enterprise delivery)
| Artefact | Primary Knowledge Area |
|---|---|
| Project charter + business case link | Integration |
| Scope statement, WBS, RTM | Scope |
| Milestone schedule + critical path narrative | Time |
| Cost baseline + simple EVM dashboard | Cost |
| Quality metrics + Definition of Done | Quality |
| RACI + staffing histogram | Human Resource |
| Communications matrix | Communications |
| Risk register + response owners | Risk |
| Make-or-buy + SOW outline | Procurement |
| Stakeholder register + engagement matrix | Stakeholder |
Related Learning Map pages
- Project Management overview
- Delivery and Programme Management
- Stakeholder Management
- Commercial and delivery
- Business Learning
External reference
- Project Management Institute — obtain the official PMBOK® Guide and current edition materials for formal study and certification.
Discussion
Comments
Share feedback or questions about this page. No account required.
Loading comments…