Agile & Hybrid Delivery
The PMP now tests both predictive and agile delivery equally. Agile is not just a methodology — it's a mindset backed by the Manifesto's 4 values and 12 principles. Most real projects today use a hybrid blend.
PMBOK 7 Shift: The 7th edition moved from process-based (5 process groups, 49 processes) to principles-based — 12 project management principles and 8 performance domains. Agile, hybrid, and predictive approaches are all valid; the right method depends on the project environment.
Requirements are fully defined upfront. Phases are sequential: Initiation → Planning → Execution → Monitoring → Closing. Best when scope is stable and changes are costly. Strong governance, formal change control.
Requirements evolve through collaboration. Delivery in short iterations (sprints). Responds to change over following a plan. Best when requirements are uncertain or customer feedback is critical to success.
Combines both approaches. Predictive for stable, compliance-driven deliverables (infrastructure, contracts); agile for evolving, customer-facing features. Most enterprise projects use some form of hybrid.
| Factor | Predictive | Agile | Hybrid |
|---|---|---|---|
| Requirement clarity | Well-defined, stable | Uncertain, evolving | Mixed — some fixed, some fluid |
| Stakeholder availability | Limited involvement after planning | Active, continuous collaboration | Selective engagement by workstream |
| Risk tolerance | Low — change is controlled | High — change is expected | Moderate — risk segmented by approach |
| Team experience | Structured, specialist roles | Cross-functional, self-organizing | Varies by workstream |
| Delivery cadence | Single final deliverable | Frequent incremental releases | Phased delivery with agile increments |
The PMP exam (since 2021) allocates approximately 50% of questions to agile or hybrid approaches. Questions test situational judgment — which approach fits the scenario — not just vocabulary. Servant leadership, team empowerment, and iterative planning are highly tested.
Increment: A potentially releasable slice of product value delivered each sprint.
Iteration: A time-boxed period of work (synonymous with sprint in Scrum).
Backlog: A prioritized list of all work to be done on the product.
User Story: Short, user-centered requirement: "As a [user], I want [goal] so that [benefit]."
Agile Foundations
The Agile Manifesto (2001) established 4 values and 12 principles. The PMP tests your understanding of these directly — especially which value pairs take precedence.
Key Rule: The Manifesto says "we value the items on the LEFT more." Both sides have value — it's about priority, not exclusion. Knowing what goes on which side is an exam staple.
The 4 Agile Manifesto Values
12 Agile Principles — Key Groups
P1: Highest priority = satisfying the customer through early and continuous delivery of valuable software.
P2: Welcome changing requirements, even late in development.
P3: Deliver working software frequently — weeks rather than months.
P4: Business people and developers work together daily throughout the project.
P5: Build projects around motivated individuals. Give them the environment and trust they need.
P6: Face-to-face conversation is the most efficient and effective method of conveying information.
P7: Working software is the primary measure of progress.
P8: Agile processes promote sustainable development — constant pace indefinitely.
P9: Continuous attention to technical excellence and good design enhances agility.
P10: Simplicity — the art of maximizing the amount of work NOT done — is essential.
P11: The best architectures, requirements, and designs emerge from self-organizing teams.
P12: At regular intervals, the team reflects on how to become more effective and adjusts accordingly.
| INVEST Letter | Meaning | What It Means in Practice |
|---|---|---|
| Independent | Self-contained | Can be developed and delivered without depending on another story |
| Negotiable | Flexible scope | Details can be discussed and refined — not a rigid contract |
| Valuable | Delivers value | Has clear benefit to the user or business |
| Estimable | Can be sized | Team can estimate effort in story points or time |
| Small | Right-sized | Fits within a single sprint; can be completed in one iteration |
| Testable | Verifiable | Acceptance criteria can be written and tested |
Scrum Framework
Scrum is the most widely used agile framework. It structures work into Sprints with defined Roles, Events, and Artifacts — all governed by three pillars: Transparency, Inspection, and Adaptation.
Scrum's 3 Pillars (TIA): Transparency — everyone sees the work as it is. Inspection — frequent review of progress. Adaptation — adjust plans based on what you learn.
Scrum Sprint Flow
The 3 Scrum Roles
- Owns and prioritizes the Product Backlog
- Defines acceptance criteria for stories
- Represents stakeholder needs
- Accepts or rejects sprint work
- One person — not a committee
- Facilitates Scrum events
- Removes impediments for the team
- Coaches team on Scrum practices
- Protects team from outside distractions
- Does NOT assign tasks or manage people
- 3–9 members (ideal)
- Cross-functional — all skills needed to build
- Self-organizing — decides HOW to do the work
- Collectively accountable for the Sprint
- No sub-teams or titles within team
The 5 Scrum Events
Scrum Artifacts & Commitments
| Artifact | Commitment | Owner | Purpose |
|---|---|---|---|
| Product Backlog | Product Goal | Product Owner | Ordered list of all work needed for the product; single source of truth |
| Sprint Backlog | Sprint Goal | Development Team | Selected PBI items + plan for delivering the Sprint Goal |
| Increment | Definition of Done | Development Team | Sum of all completed PBIs — must be useable, potentially releasable |
Definition of Done: A team-level quality checklist applied to ALL increments (e.g., code reviewed, unit tested, integrated, documentation updated). Ensures consistency across sprints.
Acceptance Criteria: Story-specific conditions defined by the Product Owner that a particular user story must meet to be accepted. Varies per story.
Exam tip: If a story meets its Acceptance Criteria but violates the DoD, it is NOT Done.
Kanban & Agile Metrics
Kanban is a flow-based method focused on visualizing work and limiting work-in-progress (WIP). Agile metrics like velocity and burn charts help teams forecast and improve.
Kanban Board — WIP Limits in Action
Visualize: All work is visible on the board — no hidden queues.
Limit WIP: Caps on in-progress work prevent multitasking and expose bottlenecks. When WIP limit is hit, the team must finish existing work before pulling new items.
Manage Flow: Monitor how work moves through stages. Blocked items are highlighted.
Explicit Policies: Define clear rules for each stage (e.g., "Review requires peer approval").
Lead Time: Total time from when a request is made (item enters Backlog) to when it is delivered. Customer's perspective — "How long did I wait?"
Cycle Time: Time from when work STARTS (item pulled into In Progress) to when it is Done. Team's perspective — "How long did we take?"
Lead Time ≥ Cycle Time (always). Reduce both to improve flow.
Burn-Down vs Burn-Up Charts
📊 Velocity-Based Release Forecast
The CFD is Kanban's primary metric. It shows the number of items in each workflow stage over time as stacked bands. A widening band = items accumulating = bottleneck. A narrowing gap between "started" and "done" lines = flow is improving.
Exam tip: CFD = Kanban. Burn-down/burn-up = Scrum. Both are agile metrics but associated with different frameworks.
Scaling Agile & Hybrid Delivery
Single-team Scrum works up to ~9 people. Larger programs need scaling frameworks. Hybrid blends predictive rigor with agile flexibility — the dominant real-world approach.
Agile Scaling Frameworks
The Delivery Approach Spectrum
Most enterprise projects fall in the middle. Choose based on requirement stability, team capability, and organizational constraints.
Phase 1 (Predictive): Business case, regulatory approvals, infrastructure procurement — fixed requirements, formal sign-offs.
Phase 2 (Agile): Application development in 2-week sprints — evolving features, continuous stakeholder feedback.
Phase 3 (Predictive): Final UAT, compliance validation, go-live cutover — scripted, change-controlled.
Water-Scrum-Fall: Running sprints but still requiring full upfront documentation and sign-off before any work starts — agile in name only.
Scrumfall: Using Scrum for development but delivering one big release at the end like waterfall — no iterative feedback loop.
The PMP exam tests whether you recognize genuine hybrid value delivery vs. superficial adoption.
| Aspect of the Project | Use Predictive | Use Agile |
|---|---|---|
| Requirements | Stable, well-defined | Unclear, evolving |
| Stakeholder involvement | Limited, formal reviews | Continuous collaboration needed |
| Risk profile | Low change risk, high failure cost | Exploratory, can pivot quickly |
| Team structure | Specialists, hierarchical | Cross-functional, self-organizing |
| Regulatory / compliance | Heavily regulated deliverable | No formal compliance burden |
| Customer feedback | Defined at contract | Iterative validation needed |
PMBOK 7 & the PMP Exam: PMI's 7th edition replaced the 5 process groups and 49 processes with 12 principles and 8 performance domains. Projects are expected to tailor their approach. The exam rewards situational judgment: pick predictive when stability and control are needed, agile when learning and adaptation matter — and hybrid when you need both.
Practice Quiz — Agile & Hybrid Delivery
10 PMP-style scenario questions. Select your answer to see instant feedback and explanation.
Review explanations above for any missed questions.
Memory Hooks & AI Advisor
Mnemonics and visual anchors to lock in the most exam-tested agile concepts. Then use the Advisor for deep-dive guidance by category.
Flashcards
Click each card to flip and reveal the answer.
What are the 4 Agile Manifesto values (left side — higher priority)?
Individuals & interactions; Working software; Customer collaboration; Responding to change — each valued OVER its right-side counterpart
What is the Scrum Master's primary responsibility?
Servant leadership: facilitate Scrum events, remove impediments, coach the team on Scrum — does NOT assign tasks or manage team members
Sprint Review vs Sprint Retrospective — what's the difference?
Review = inspect the PRODUCT with stakeholders (demo); Retrospective = inspect the PROCESS with the team (continuous improvement)
How is velocity used for release forecasting?
Sprints needed = Total remaining story points ÷ Average velocity. Use last 3–4 sprints for the average to forecast delivery date
What does a WIP limit control, and why does it matter?
Caps items allowed in a workflow stage at once. Prevents multitasking, exposes bottlenecks, and improves flow. Rule: stop starting, start finishing
What is the Definition of Done (DoD), and who owns it?
Shared quality checklist applied to ALL increments (e.g., coded, reviewed, tested, integrated). Owned by the Development Team. A story meeting its AC but failing DoD is NOT Done
What is PI Planning in SAFe, and how often does it occur?
Program Increment Planning — a 2-day face-to-face event every 8–12 weeks where all Agile Release Train teams align on objectives, dependencies, and risks for the next PI
When is a hybrid approach recommended over pure agile or pure predictive?
When some deliverables have fixed/regulated requirements (→ predictive) while others need iterative customer feedback (→ agile). Apply the right method to each workstream
AI Advisor
Select a category for focused exam guidance.
Agile Values & Principles
- Both sides have value: The Manifesto says we value the LEFT side MORE — not that the right side is worthless. Documentation matters; working software matters more.
- Most tested value: "Responding to change over following a plan" appears frequently in hybrid/change-control PMP scenarios.
- Principle 1 — the north star: Highest priority = satisfying the customer through early and continuous delivery. When in doubt, choose the option that delivers value to the customer sooner.
- Principle 10 — simplicity: "Maximizing the amount of work NOT done" means don't gold-plate. Build what delivers value, not everything imaginable.
- Principle 12 — retrospectives: At regular intervals the team reflects on how to become more effective. This is the Scrum Retrospective in practice.
- Sustainable pace (Principle 8): Agile processes promote working at a constant pace indefinitely. Avoid crunch; burnout kills agility.
- INVEST mnemonic: Independent, Negotiable, Valuable, Estimable, Small, Testable. Use to evaluate whether a user story is ready for a sprint.
Scrum Framework
- PO ≠ project manager: The Product Owner maximizes product value, owns the backlog, and defines acceptance criteria. They do NOT assign daily tasks or manage team members.
- SM ≠ manager: The Scrum Master is a servant leader and coach. They remove impediments but do NOT control what the team works on or how they do it.
- Dev Team is self-organizing: The team decides HOW to do the work. No sub-teams, no titles within the team. Size: 3–9 members.
- Sprint commitment: The Dev Team commits to the sprint backlog — not mandated by PO or SM. Only the Dev Team can change the Sprint Backlog mid-sprint.
- Review vs Retro: Sprint Review = inspect the PRODUCT with stakeholders. Sprint Retrospective = inspect the PROCESS with the team. This distinction is heavily tested.
- Daily Scrum misconception: It is NOT a status meeting for the manager. It is a 15-minute planning meeting for the Dev Team to synchronize and identify impediments.
- DoD vs Acceptance Criteria: DoD applies to ALL increments (team-wide quality standard). Acceptance Criteria are story-specific (defined by PO). Story must meet BOTH to be Done.
Kanban & Metrics
- WIP limit hit → stop starting: When WIP limit is reached, the right action is to finish existing work — not raise the limit or start anyway.
- Lead time vs cycle time: Lead = customer wait (backlog entry → done). Cycle = team work time (in progress → done). Lead ≥ Cycle always.
- CFD = Kanban metric: Cumulative Flow Diagram shows items in each stage over time. Widening bands signal bottlenecks. CFD is NOT a burn chart.
- Burn-down — above ideal = behind: Actual remaining work ABOVE the ideal line means the team is burning down slower than planned. Below ideal = ahead of schedule.
- Burn-up advantage: Shows scope changes explicitly — total scope line rises when new items are added. Burn-down hides scope creep by only showing remaining work.
- Velocity is a forecast tool: Average velocity (story points/sprint) from last 3–4 sprints divided into remaining backlog gives sprint forecast. Velocity cannot be mandated — it emerges from the team's sustainable pace.
- Story points ≠ hours: Story points are relative sizing units (complexity + effort + uncertainty). They don't convert directly to hours — resist pressure to do so.
Scaling Agile
- SAFe = PI Planning + ARTs: Scaled Agile Framework is the most popular enterprise framework. Agile Release Trains (ARTs) of 50–125 people. PI Planning every 8–12 weeks. Release Train Engineer (RTE) is the SAFe Scrum Master equivalent.
- LeSS = minimal added structure: One PO, one backlog, multiple dev teams. Avoids creating new roles and ceremonies. Suitable for companies wanting to scale Scrum without heavy overhead.
- Nexus = Scrum.org's framework: 3–9 teams. Adds a Nexus Integration Team to manage cross-team dependencies and integration issues. Very close to standard Scrum.
- Disciplined Agile = PMI's toolkit: Not prescriptive — provides methods for teams to choose their own way of working (WoW). Highly context-driven. Endorsed by PMI since 2019 acquisition.
- PMP exam scaling focus: Expect questions about when to use scaling (team size > 9, multiple teams, complex dependencies) and characteristics of SAFe vs LeSS conceptually.
- Agile vs Scale: Scaling adds coordination overhead. The first question should always be: can we restructure to keep teams small and independent rather than scaling?
Hybrid Delivery
- Right tool for the job: Hybrid is not a compromise — it's intentional. Apply predictive where requirements are stable and change is costly; apply agile where learning and adaptation are essential.
- Common hybrid triggers: Regulatory/compliance work (predictive) + customer-facing features (agile). Infrastructure builds (predictive) + application layers (agile).
- Water-Scrum-Fall anti-pattern: Agile in the middle but waterfall gates at the start and end. Teams do sprints but must write full requirements upfront and do big-bang releases — defeats the purpose of agile feedback loops.
- PMBOK 7 endorses tailoring: No single approach is prescribed. PMI expects PMs to tailor the methodology to the project context (Principle of Tailoring).
- Servant leadership in hybrid: Even in hybrid projects, agile portions require a servant leader mindset — remove obstacles, protect the team, don't command-and-control the sprint.
- Exam tell: If a scenario mentions "some requirements are clear and others are not yet defined," the answer is almost always hybrid — predictive for the known, agile for the unknown.
Ready to Test Your Knowledge?
Practice with full-length PMP exam simulations on FlashGenius — timed, scored, and mapped to exam domains.
Unlock Full Practice Tests on FlashGenius →