PMBOK 7th Edition – Comprehensive Study Notes

Evolution from PMBOK 6th → 7th Edition

  • Paradigm shift
    • 6th Ed.: Prescriptive, process-oriented, compliance-driven ("how"-focused)
    • 7th Ed.: Principle-based, descriptive, outcome/value-focused ("why & what"), embraces full value-delivery landscape
  • Design basis changes
    • From 49 Process Groups ⇒ 8 Performance Domains (interacting, inter-dependent areas of activity with desired outcomes)
    • Adds a dedicated Tailoring section + extensive “Models, Methods & Artifacts” catalog
  • Audience broadened
    • From primarily Project Managers ⇒ anyone involved in projects (team, sponsor, product owner, etc.)
  • Development approaches explicitly recognized
    • Predictive, adaptive, agile, hybrid, lean, customer-centered design, etc.

Content Architecture (7th Ed.)

  • Introductory Chapters
    • System for Value Delivery
    • 12 Project Management Principles (mindset & behaviors)
  • Eight Project Performance Domains
    1. Stakeholders
    2. Team
    3. Development Approach & Life Cycle
    4. Planning
    5. Project Work
    6. Delivery
    7. Measurement
    8. Uncertainty
  • Tailoring Guidance
  • Models, Methods, & Artifacts (MMA) library

System for Value Delivery

  • Why projects exist: to create or sustain value
    • New product/service/result satisfying customer need
    • Positive social/environmental contribution
    • Efficiency, productivity, effectiveness, responsiveness improvements
    • Enable organizational transition to desired future state
    • Sustain previously delivered benefits
  • Typical components of a value-delivery system (sample diagram referenced)
  • Product management considerations & sample product life cycle (idea → retirement)
  • Project Environment
    • Internal
    • Process & knowledge assets, governance docs, data, IT, infrastructure, org culture, resource availability, employee capability, security & safety, etc.
    • External
    • Marketplace, socio-cultural factors, regulations, standards, academic research, financial conditions, physical environment

12 Project Management Principles

  1. Stewardship – act with integrity, care, trustworthiness, compliance; consider financial+social+environmental\text{financial} + \text{social} + \text{environmental} impacts
  2. Team – foster collaborative, diverse, capable teams (agreements, structures, processes)
  3. Stakeholders – engage proactively to ensure success & satisfaction
  4. Value – continuously align project to business objectives & intended benefits; business case = need + justification + strategy
  5. Systems Thinking – holistic view, challenge assumptions, model system dynamics, proactively manage integration
  6. Leadership – adapt styles/behaviors to meet people & situational needs
  7. Tailoring – design "just-enough" processes for context to maximize value, manage cost, increase speed
  8. Quality – focus on deliverables that meet objectives & stakeholder acceptance; quality dimensions: performance, conformity, reliability, resilience, satisfaction, uniformity, efficiency, sustainability
  9. Complexity – navigate human/system behavior, uncertainty, ambiguity, innovation
  10. Risk – maximize opportunities & minimize threats
  11. Adaptability & Resiliency – build capacity to absorb change & recover from setbacks
  12. Change – prepare people to adopt & sustain new behaviors/processes

Principles ↔ Performance Domains

  • Principles provide mindset; Domains organize work. Mapping ensures each domain’s activities reflect the 12 principles.

Performance Domain: Stakeholders

  • Definition: individual/group/org that may affect or be affected by the project
  • Examples: customers, sponsors, functional managers, suppliers, regulators, communities, etc.
  • Engagement activities
    • Identify → Analyze (power, impact, attitude, beliefs, expectations, influence, proximity, interest) → Plan → Engage → Monitor

Performance Domain: Team

  • Team development aspects
    • Vision & objectives, roles & responsibilities, operations, guidance, growth
  • Traits of high-performing teams
    • Open communication, shared understanding/ownership, trust, collaboration, adaptability, resilience, empowerment, recognition
  • Tailoring leadership style depends on project type, team maturity, governance, distribution

Performance Domain: Development Approach & Life Cycle

  • Key terms
    • Deliverable, Development Approach, Cadence
  • Delivery cadence options: single, multiple, periodic
  • Development approaches: Predictive, Adaptive, Hybrid
  • Life-cycle examples
    • Pure predictive (sequential)
    • Predictive with incremental delivery
  • Alignment triad: Delivery cadence ↔ Development approach ↔ Life cycle

Performance Domain: Planning

  • Estimating concepts
    • Estimate, Accuracy, Precision
    • Schedule compression
    • Crashing: add resources for min Δcost\text{min}\ \Delta \text{cost} to shorten duration
    • Fast-tracking: parallelize sequential activities
  • Schedule artifacts: fast-tracking examples
  • Budget development & roll-up

Performance Domain: Project Work

  • Core activities
    • Manage flow of work & changes, focus team, install systems & processes, comms, logistics, procurements, change monitoring, learning/knowledge transfer
  • Key definitions
    • Bid documents (RFI, RFQ, RFP), Bidder conference, Explicit vs. Tacit knowledge

Performance Domain: Delivery

  • Key concepts
    • Requirement, WBS, Definition of Done (DoD), Quality, Cost of Quality (COQ)
  • COQ components
    • Prevention, Appraisal, Internal failure, External failure
  • Cost of Change – increases as project progresses; poor quality ⇒ sub-optimal outcomes

Performance Domain: Measurement

  • Fundamental terms
    • Metric, Baseline, Dashboard
  • Designing measures
    • KPI=quantifiable metric tied to critical success factor\text{KPI} = \text{quantifiable metric tied to critical success factor}
    • Leading vs. Lagging indicators
    • SMARTER metrics (Specific, Meaningful, Achievable, Relevant, Timely, Evaluate, Re-evaluate)
  • What to measure
    • Deliverables (defects, performance)
    • Flow metrics: WIP, lead time, cycle time, queue size, batch size, process efficiency
    • Schedule
    • SV=EV−PVSV = EV - PV
    • SPI=EVPVSPI = \frac{EV}{PV}
    • Feature completion rate
    • Cost
    • CV=EV−ACCV = EV - AC
    • CPI=EVACCPI = \frac{EV}{AC}
    • Resources (utilization & cost)
    • Business value
    • ROI=Net BenefitCost\text{ROI} = \frac{\text{Net Benefit}}{\text{Cost}}
    • NPV=∑<em>t=0nC</em>t(1+r)tNPV = \sum<em>{t=0}^{n} \frac{C</em>t}{(1+r)^t}
    • Cost-benefit ratio
    • Stakeholders: Net Promoter Score®, mood charts/boards, morale, turnover
  • Measurement pitfalls: Hawthorne effect, vanity metrics, demoralization, misuse, confirmation bias, confusing correlation vs. causation
  • Guiding rule: Only measure/report if it drives learning, decisions, improvement, issue avoidance, or prevents decline

Performance Domain: Uncertainty

  • Vocabulary
    • Uncertainty, Ambiguity, Complexity, Volatility, Risk
  • General response options
    • Gather information, plan for multiple outcomes, set-based design, build resilience
  • Addressing ambiguity: progressive elaboration, experiments, prototypes
  • Complexity handling
    • Systems-based: decoupling, simulation, reframing
    • Diversity-based: balance teams/processes
    • Process-based: iterate, engage, fail-safe
  • Volatility tactics: alternatives analysis, reserves/buffers

Tailoring

  • Definition: deliberate adaptation of PM approach, governance & processes to fit context
  • Tailoring Process (iterative)
    1. Assess context & environment
    2. Select approach(es) & performance domain emphases
    3. Decide specific practices, tools, artifacts, cadence, governance needs
    4. Implement & monitor
    5. Review & adjust
  • Tailoring suggestions provided for common situations (size, complexity, life-cycle type, regulatory, distributed teams, etc.)

Models, Methods & Artifacts (MMA)

  • Model = thinking strategy/framework (e.g., Cynefin)
  • Method = how-to technique (e.g., Earned Value Analysis)
  • Artifact = template/document/deliverable (e.g., WBS)
  • Tailor MMA selection to project context & performance domains

Commonly Used Models

  • Leadership: Situational Leadership® II, OSCAR
  • Communication: Cross-cultural, channel effectiveness, Gulf of execution/evaluation
  • Motivation: Herzberg hygiene, intrinsic/extrinsic, McClelland needs, Theory X/Y/Z
  • Change: ADKAR®, Kotter 8-step, Satir, Bridges Transition
  • Complexity: Cynefin, Stacey matrix
  • Team dev.: Tuckman ladder, Drexler/Sibbet
  • Others: Conflict, Negotiation, Planning, Process Groups, Stakeholder Salience

Commonly Used Methods (selected groups)

  • Data Gathering & Analysis: alternative, assumption/constraint, benchmarking, payback, IRR, ROI, NPV, cost-benefit, check sheets, COQ, decision tree, EVM, EMV, forecast, influence diagram, LCA, make-or-buy, P&I matrix, regression, reserve, root-cause, sensitivity, simulation, SWOT, trend, VSM, variance, what-if
  • Estimating: affinity grouping, analogous, FP, multi-point, parametric, relative, single-point, story points, Wideband Delphi

Commonly Used Artifacts

  • Logs/registers: assumption, backlog, change, issue, lessons learned, risk-adjusted backlog, risk register, stakeholder register
  • Hierarchies: OBS, PBS, RBS, Risk BS, WBS
  • Visual & information radiators: affinity diagram, burndown/up, cause-effect, cumulative flow, cycle time, dashboards, flowchart, Gantt, histogram, lead time, prioritization matrix
  • Other: activity list, bid docs, metrics sheets, project calendar, requirements docs, team charter, user story

Key Definitions & Terms Recap

  • Deliverable, Definition of Done, Cadence, Estimate, Crashing, Fast-tracking, Explicit vs. Tacit knowledge, Metric, Baseline, Dashboard, etc.

Practical / Ethical / Philosophical Implications

  • Ethical stewardship obliges PMs to integrate social & environmental considerations with financial outcomes
  • Tailoring embodies respect for context over rigid compliance, reinforcing professional judgment & accountability
  • Systems thinking discourages local optimization by emphasizing holistic impact on value delivery
  • Measurement ethics: avoid vanity metrics & ensure data drives beneficial action, respecting team morale & stakeholder trust

Connections & Real-World Relevance

  • Agile practitioners will recognize principles like adaptability, stakeholder engagement, frequent delivery cadence
  • Lean & Six Sigma professionals see integration of COQ, value stream mapping, root-cause analysis
  • Hybrid managers can blend predictive budgeting/earned value with iterative delivery & adaptive planning
  • Regulatory projects (e.g., pharma, aerospace) must tailor rigor & documentation to compliance while preserving agility where feasible

Formula Appendix (commonly referenced)

  • Schedule Variance: SV=EV−PVSV = EV - PV
  • Schedule Performance Index: SPI=EVPVSPI = \frac{EV}{PV}
  • Cost Variance: CV=EV−ACCV = EV - AC
  • Cost Performance Index: CPI=EVACCPI = \frac{EV}{AC}
  • Return on Investment: ROI=Net BenefitsCostROI = \frac{\text{Net Benefits}}{\text{Cost}}
  • Net Present Value: NPV=∑<em>t=0nC</em>t(1+r)tNPV = \sum<em>{t=0}^{n} \frac{C</em>t}{(1+r)^t}
  • Internal Rate of Return: solves NPV=0NPV=0 for rr
  • Cost of Change Trend: COC↑exponentially as project phase advances\text{COC} \uparrow \text{exponentially as } \text{project phase advances} (conceptual)