← PMP Exam Prep: Agile & Hybrid Project Management

PMP Project Management Professional Exam Study Guide

Key concepts, definitions, and exam tips organized by topic.

36 cards covered

PMP Exam Prep: Agile & Hybrid Project Management

Comprehensive Study Guide


---


Overview


This study guide covers the Agile and Hybrid Project Management domains tested on the PMP exam, including frameworks, Scrum ceremonies, planning techniques, metrics, and team dynamics. Agile questions now represent approximately 50% of the PMP exam, making this material critical for success. Mastery of both agile mindset and practical application — not just terminology — is essential.


---


Table of Contents

1. [Agile Frameworks & Methodologies](#1-agile-frameworks--methodologies)

2. [Scrum Roles & Ceremonies](#2-scrum-roles--ceremonies)

3. [Agile Planning & Estimation](#3-agile-planning--estimation)

4. [Hybrid Project Management](#4-hybrid-project-management)

5. [Agile Metrics & Reporting](#5-agile-metrics--reporting)

6. [Agile Team Dynamics & Mindset](#6-agile-team-dynamics--mindset)

7. [Quick Review Checklist](#quick-review-checklist)


---


1. Agile Frameworks & Methodologies


Summary

Agile is an umbrella term for iterative, incremental approaches to project delivery. Multiple frameworks exist under the agile umbrella, each with distinct practices, but all rooted in the Agile Manifesto. The PMP exam tests your ability to recognize which framework fits a given scenario and understand their core mechanics.


---


The Agile Manifesto — Four Core Values


| Agile Values | Over |

|---|---|

| Individuals and interactions | Processes and tools |

| Working software | Comprehensive documentation |

| Customer collaboration | Contract negotiation |

| Responding to change | Following a plan |


> ⚠️ The right-hand items still have value — the left-hand items are simply valued more.


---


Key Frameworks Compared


| Framework | Primary Focus | Distinctive Feature |

|---|---|---|

| Scrum | Iterative delivery via sprints | Defined roles, ceremonies, artifacts |

| Kanban | Continuous flow | WIP limits, visualized workflow |

| XP (Extreme Programming) | Engineering excellence | TDD, pair programming, CI |

| SAFe | Enterprise-scale agile | Program Increments (PIs), Agile Release Trains |

| Lean | Waste elimination | Value stream, pull systems |


---


Key Concepts


  • • Sprint: A fixed-length iteration (1–4 weeks) in Scrum during which a potentially shippable increment is delivered. Sprints have a fixed end date and are never extended.
  • • WIP Limit (Kanban): Restricts the number of items in any workflow stage simultaneously. This reduces multitasking, exposes bottlenecks, and improves flow efficiency.
  • • Timeboxing: Fixing a set duration for any activity or event. Creates urgency, limits scope creep, and drives regular delivery.
  • • Program Increment (SAFe): An 8–12 week timebox in which Agile Release Train (ART) teams plan, build, and deliver incremental value. Think of it as a "sprint of sprints."

    • ---


    Key Terms

  • • Agile Manifesto — Foundational document with 4 values and 12 principles
  • • Kanban Board — Visual tool showing workflow stages
  • • Test-Driven Development (TDD) — Writing tests before writing code (XP practice)
  • • Pair Programming — Two developers work at one workstation (XP practice)
  • • Continuous Integration (CI) — Frequently merging code to a shared repository (XP practice)
  • • Agile Release Train (ART) — Long-lived team of teams in SAFe
  • • Timebox — A fixed, non-negotiable duration for an event or iteration

    • ---


    Watch Out For

    > ⚠️ Kanban ≠ Scrum: Kanban has no sprints, no roles, and no ceremonies. It uses continuous flow with WIP limits. Don't confuse the two on scenario questions.


    > ⚠️ SAFe PI ≠ Sprint: A PI contains multiple sprints and spans 8–12 weeks. PIs include an Innovation and Planning (IP) iteration at the end.


    > ⚠️ XP is engineering-focused: If a scenario mentions TDD, pair programming, or CI as primary practices — the answer is XP, not Scrum.


    ---


    2. Scrum Roles & Ceremonies


    Summary

    Scrum is built on three roles, five ceremonies (events), and three artifacts. The PMP exam heavily tests the boundaries and accountabilities of each role, and the purpose of each ceremony — not just their definitions.


    ---


    The Three Scrum Roles


    | Role | Primary Accountability |

    |---|---|

    | Product Owner (PO) | Maximizing product value; owns and orders the Product Backlog |

    | Scrum Master (SM) | Servant-leader; removes impediments; coaches team on Scrum |

    | Development Team | Delivering a "Done" increment each sprint; self-organizing |


    ---


    The Five Scrum Ceremonies


    | Ceremony | Timing | Duration (for 2-week sprint) | Purpose |

    |---|---|---|---|

    | Sprint Planning | Start of sprint | Up to 8 hours | Select backlog items; create Sprint Goal & Sprint Backlog |

    | Daily Scrum | Daily | 15 minutes | Synchronize work; identify impediments |

    | Sprint Review | End of sprint | Up to 4 hours | Inspect the increment; gather stakeholder feedback |

    | Sprint Retrospective | After Sprint Review | Up to 3 hours | Inspect the process; identify improvements |

    | Backlog Refinement | Mid-sprint (ongoing) | ~10% of sprint capacity | Clarify, estimate, and prioritize upcoming backlog items |


    ---


    Critical Distinctions: Review vs. Retrospective


    | | Sprint Review | Sprint Retrospective |

    |---|---|---|

    | Focus | The product (what was built) | The process (how the team works) |

    | Attendees | Team + Stakeholders | Team only (internal) |

    | Output | Updated Product Backlog | Improvement action items |


    ---


    Daily Scrum — Three Key Questions

    1. What did I do yesterday that helped the team meet the Sprint Goal?

    2. What will I do today to help the team meet the Sprint Goal?

    3. Are there any impediments blocking me or the team?


    ---


    Definition of Done (DoD)


  • • A shared, formal understanding of what criteria must be met for an increment to be considered complete.
  • • Created by the Development Team (with input from the organization).
  • • If a DoD does not yet exist organizationally, the team must create one appropriate for the product.
  • • Not the same as Acceptance Criteria — DoD applies to all items; Acceptance Criteria are story-specific.

    • ---


    Key Terms

  • • Product Backlog — Ordered list of all desired product work; owned by Product Owner
  • • Sprint Backlog — Items selected for current sprint + Sprint Goal + delivery plan; owned by Development Team
  • • Increment — The sum of all completed Product Backlog items at the end of a sprint
  • • Sprint Goal — The single objective set for the sprint during Sprint Planning
  • • Impediment — Any obstacle preventing the team from making progress; removed by Scrum Master
  • • Servant Leadership — Leading by serving: enabling, coaching, facilitating rather than directing

    • ---


    Watch Out For

    > ⚠️ Product Owner is ONE person, not a committee. The PO may represent stakeholder needs but has sole authority over the Product Backlog ordering.


    > ⚠️ The Scrum Master does NOT manage the team. They are a coach and facilitator. Management/direction comes from the team itself (self-organization).


    > ⚠️ Sprint length must remain consistent. Sprints are not extended to accommodate unfinished work — items return to the Product Backlog.


    > ⚠️ Backlog Refinement is NOT an official Scrum event in the Scrum Guide but is widely accepted practice and may appear on the exam as a legitimate agile activity.


    ---


    3. Agile Planning & Estimation


    Summary

    Agile planning is iterative and progressive — detailed plans are made close to execution, not months in advance. Estimation is relative and collaborative, using techniques that capture team consensus rather than individual expert judgment.


    ---


    User Stories


    Standard Format:

    > "As a [role/persona], I want [goal/feature], so that [benefit/value]."


    INVEST Criteria — a well-formed user story is:


    | Letter | Meaning | Why It Matters |

    |---|---|---|

    | I | Independent | Can be built without depending on another story |

    | N | Negotiable | Details can be discussed and adjusted |

    | V | Valuable | Delivers value to the user or customer |

    | E | Estimable | Team can size/estimate the effort |

    | S | Small | Can be completed within a sprint |

    | T | Testable | Clear acceptance criteria exist |


    ---


    Estimation Techniques


  • • Story Points: Relative units of measure for effort, complexity, and uncertainty. Not hours or days.
  • • Planning Poker: Consensus-based technique; team members simultaneously reveal estimates using numbered cards (Fibonacci sequence: 1, 2, 3, 5, 8, 13…). Outliers are discussed until consensus is reached.
  • • Relative Estimation: Comparing items to each other rather than assigning absolute time. Faster, reduces anchoring bias, and increases team consistency.
  • • T-shirt Sizing: Categorizing stories as XS/S/M/L/XL — a quick relative estimation approach.

    • ---


    Velocity & Capacity Planning


  • • Velocity: Average story points completed per sprint. Calculated after several sprints of data. Used to forecast future delivery, not as a performance target.
  • • Capacity: The actual availability of team members in an upcoming sprint (accounts for holidays, PTO, etc.).
  • • Forecast = Velocity × Number of Sprints

    • ---


    Backlogs & Charts


    Product Backlog vs. Sprint Backlog:


    | | Product Backlog | Sprint Backlog |

    |---|---|---|

    | Owner | Product Owner | Development Team |

    | Scope | All work for the entire product | Work selected for current sprint |

    | Stability | Continuously refined | Fixed once sprint starts (sprint goal stays) |


    Burndown Charts:

  • • Sprint Burndown: Shows remaining work within a sprint (day by day). Ideal line runs diagonally from total points to zero.
  • • Release Burndown: Shows remaining backlog work across multiple sprints. Helps forecast whether the release target will be met.

    • ---


    Key Terms

  • • Backlog Refinement (Grooming) — Process of clarifying, estimating, and prioritizing backlog items
  • • Spike — A time-boxed research task to reduce uncertainty before estimating or committing to a story
  • • Epic — A large user story that needs to be broken down into smaller stories
  • • Theme — A collection of related user stories or epics
  • • Acceptance Criteria — Specific conditions a story must satisfy to be accepted by the Product Owner
  • • Rolling Wave Planning — Progressive elaboration: near-term work planned in detail; future work at a high level

    • ---


    Watch Out For

    > ⚠️ Velocity is descriptive, not prescriptive. Management should never use velocity as a performance metric to pressure teams to increase output — this degrades quality and inflates estimates.


    > ⚠️ A spike is NOT a user story. It produces knowledge, not a deliverable feature. It has a time-box, not a story point estimate.


    > ⚠️ Burndown charts track remaining work (going down to zero), while Burnup charts track completed work (going up toward the target). Both are valid — know the difference.


    > ⚠️ INVEST is for evaluating stories, not writing them. If a story fails INVEST criteria, it needs to be revised before being sprint-ready.


    ---


    4. Hybrid Project Management


    Summary

    Hybrid project management blends predictive (waterfall) and agile approaches to optimize fit for a given project's unique context. The PMP exam increasingly presents hybrid scenarios, requiring you to assess which approach or combination is most appropriate given constraints such as regulation, team maturity, and requirement clarity.


    ---


    When to Use Each Approach


    | Approach | Best For |

    |---|---|

    | Predictive (Waterfall) | Fixed scope, well-defined requirements, regulated industries, low uncertainty |

    | Agile | High uncertainty, evolving requirements, need for frequent customer feedback |

    | Hybrid | Projects with some fixed and some evolving components |


    ---


    Common Hybrid Patterns


  • • Phased Hybrid: Predictive phases (e.g., planning, procurement) combined with agile delivery sprints.
  • • Component Hybrid: Stable components delivered predictively; innovative/uncertain components delivered agilely.
  • • Governance Hybrid: Agile team practices within a predictive program or portfolio structure.

    • ---


    Scope Management in Hybrid


    | | Pure Agile | Hybrid | Pure Predictive |

    |---|---|---|---|

    | Scope Definition | Emergent, evolving | High-level fixed; details flexible | Fully defined upfront |

    | Change Management | Changes welcomed | Controlled flexibility | Formal change control |

    | Documentation | Minimal/just-enough | Risk-based | Comprehensive |


    ---


    Rolling Wave Planning

  • • Near-term work is planned in detail (sprint-ready backlog items).
  • • Future work is planned at a high level (epics, themes, roadmap milestones).
  • • Supports hybrid by combining predictive milestones with iterative delivery.
  • • Enables progressive elaboration — requirements are refined as more is known.

    • ---


    Stakeholder Engagement Comparison


    | | Agile | Predictive |

    |---|---|---|

    | Frequency | Continuous — every sprint | Milestone-driven — phase gates |

    | Role of Stakeholder | Active collaborator, reviewer | Requirements provider, approver |

    | Feedback loops | Short (sprint-by-sprint) | Long (phase-to-phase) |

    | Change response | Built into process | Requires formal change requests |


    ---


    Key Terms

  • • Predictive (Waterfall) — Sequential phases; scope fixed upfront
  • • Progressive Elaboration — Continuously refining plans as more information becomes available
  • • Rolling Wave Planning — Detailed near-term planning with high-level future planning
  • • Phase Gate (Stage Gate) — A decision point between project phases in predictive approaches
  • • Tailoring — Adapting the project management approach to fit the project's specific context
  • • PMI's PMBOK Guide 7 — Principle-based; explicitly recognizes the spectrum from predictive to agile

    • ---


    Watch Out For

    > ⚠️ Hybrid is NOT just "doing both at the same time" randomly. It requires deliberate tailoring based on risk, requirements clarity, stakeholder needs, and organizational constraints.


    > ⚠️ Regulatory environments often require predictive elements even when the team uses agile delivery. Documentation, traceability, and formal approvals may be non-negotiable.


    > ⚠️ Rolling wave planning is NOT the same as not planning. It is a disciplined approach to progressive elaboration — not an excuse to skip planning.


    ---


    5. Agile Metrics & Reporting


    Summary

    Agile metrics focus on flow, quality, and value delivery rather than traditional measures like hours spent or percentage complete. The PMP exam tests your ability to interpret these metrics in context and select the right tool for a given information need.


    ---


    Core Agile Metrics


    | Metric | What It Measures | Used For |

    |---|---|---|

    | Velocity | Story points completed per sprint | Sprint capacity planning; release forecasting |

    | Sprint Burndown | Remaining work within a sprint | Daily tracking of sprint progress |

    | Release Burndown | Remaining backlog across sprints | Forecasting release date/scope completion |

    | Cycle Time | Time from work start to completion | Process efficiency; delivery predictability |

    | Lead Time | Time from work request to delivery | End-to-end customer responsiveness |

    | Cumulative Flow Diagram (CFD) | Work volume in each workflow stage over time |

    📝

    Take a Practice Test

    Test yourself with multiple choice questions
    📇

    Study with Flashcards

    Flip through all 36 cards

    Want more study tools?

    Subscribe for $7.99/mo and turn your own notes into personalized flashcards and study guides.

    View Pricing