27 · Agile & Hybrid Delivery

POSTER 27

Extension · Adaptive & Hybrid Delivery

Agile & Hybrid Delivery

Adaptive (agile) delivery embraces change through short iterations and frequent value; hybrid blends predictive and adaptive. PMBOK 7 is approach-agnostic — tailoring (Poster 5) picks the approach. Deliver iteratively & incrementally, inspect & adapt, and lead as a servant.

Visual Map — The Scrum Sprint Cycle

Product Backlog
ordered by value▸ Sprint Planning
pick & commit▸ Sprint (1–4 wks)
Daily Scrum ↻ build▸ Increment
"done" & usable▸ Review
demo & feedback▸ Retrospective
inspect & adapt↺

Iterative = refine the same thing each pass; incremental = add a usable slice each pass. Agile does both, delivering value early and adjusting on real feedback.

The Agile Manifesto — 4 Values

We value the items on the left more (the right still has value):

Individuals & interactions > processes & tools
Working product > comprehensive documentation
Customer collaboration > contract negotiation
Responding to change > following a plan

+ 12 principles · servant leadership · sustainable pace · technical excellence.

Scrum — 3 · 5 · 3

3 accountabilities
· Product Owner — owns & prioritises backlog
· Scrum Master — servant leader, clears blocks
· Developers — build, self-organise
3 artifacts
· Product Backlog · Sprint Backlog · Increment

5 events
· Sprint (timebox)
· Sprint Planning
· Daily Scrum (15 min)
· Sprint Review
· Retrospective
+ Definition of Done

Kanban & Flow

Visualise the workflow on a board.
Limit WIP — pull, don't push; expose bottlenecks.
Manage flow; make policies explicit; improve.
Metrics: lead time · cycle time · throughput · cumulative flow.
Continuous — no fixed iterations.

Stories, Estimation & Metrics

User story: "As a <role>, I want <goal>, so that <benefit>."
INVEST + acceptance criteria; MVP first.
Relative estimation: story points · planning poker · t-shirt sizes.
Velocity = points / sprint; burndown / burnup charts.
Prioritise: MoSCoW · WSJF (weighted shortest job first).

Predictive vs Agile (→ Hybrid)

Dimension	Predictive	Agile
Requirements	fixed upfront	evolving
Delivery	single, at the end	incremental, frequent
Change	controlled, costly	embraced, cheap
Customer	milestone-based	continuous
Success	on plan (scope/time/cost)	value delivered
Leadership	directive	servant

Hybrid — When & How

Predictive shell + agile core — stage-gate governance around iterative build.
Use when work is regulated and uncertain.
Common split: hardware predictive · software agile.
Balances assurance with adaptability.

Exam Concepts

Manifesto 4 values; Scrum 3-5-3 & timeboxing.
PO owns backlog priority; team self-organises.
Scrum Master = servant leader, not a boss.
WIP limits (Kanban); velocity & story points.
Retrospective = continuous improvement.

Executive View

Faster feedback & value, lower risk on uncertain work.
Empower teams; measure outcomes over outputs.
Hybrid bridges governance with agility.

Industry Example

Regulated SaaS: agile sprints inside predictive compliance gates. On a production line, the control software ships agile while the hardware build runs predictive — a clean hybrid.

Relationships

Tailoring (Poster 5) selects predictive / hybrid / adaptive.
Realises PMBOK 7's Development Approach & Life Cycle domain (Poster 3).
Burn charts & CFD are artifacts from Poster 6.

Memory Hooks

Manifesto = left over right (4 value pairs).
Scrum = 3-5-3 (roles · events · artifacts).
Iterative = refine · Incremental = add.

60-sec Review The 4 Manifesto values Scrum 3-5-3 Kanban: limit WIP Iterative vs incremental When to go hybrid

PMI Visual Wall · Poster 27 · Agile & Hybrid Delivery · original instructional design · A3 landscape