SkarpChapter 13 of 20
Planning and Delivering in Agile: Backlogs, Iterations, and Hybrid Life Cycles
See how adaptive teams plan just enough, just in time, using backlogs, iterations, and release planning—and how these patterns blend with predictive elements in hybrid life cycles. This is where agile theory turns into the practical exam scenarios you’ll face.
From Agile Theory to Planning Reality
Module Focus
This module turns agile theory into planning reality: how teams choose what to do next, how much to take on, and how this fits with predictive governance.
Three Anchors
We focus on: backlogs (capturing and ordering work), iterations (short timeboxed plans), and hybrid life cycles (mixing agile with predictive planning).
Exam Expectations
For CAPM, you must explain backlog evolution, follow iteration planning, distinguish iterative vs incremental vs adaptive life cycle, and spot hybrid patterns.
Agile Still Does Projects
Remember PMI’s definition of a project: "A temporary endeavor undertaken to create a unique product, service, or result." Agile changes how we plan and deliver, not what a project is.
Compare With Predictive
As you learn, compare agile tools with predictive tools like the work breakdown structure and Gantt charts. Exam items often ask you to choose the best approach.
The Product Backlog: Your Single Source of Work
Definition to Memorize
The product backlog is "An ordered list of everything that is known to be needed in the product, managed by the product owner." Focus on ordered, everything, and owner.
Ordered, Not Just Listed
Ordering reflects value, urgency, and risk. The Product Owner leads this business decision, with input from stakeholders and the team.
Everything in One Queue
Features, defects, technical work, research, and compliance tasks all live in the same backlog, avoiding multiple competing lists of work.
Backlog Item Qualities
Each item should represent value, have clear acceptance criteria, and be small enough for an iteration, or be broken down until it is.
Visual Picture
Imagine a vertical list: top items are detailed and estimated; lower items are rough ideas to refine later. This is your dynamic plan.
Backlog Creation, Ordering, and Refinement Over Time
Backlog Evolves, Not Freezes
Backlogs are created, ordered, and refined continuously as you learn. Think in three phases: create, order, refine.
Create the Initial Backlog
The Product Owner gathers high-level needs from stakeholders and sources like business cases or traceability matrices to form large, coarse items.
Order by Value and Risk
The PO orders items by value, risk, dependencies, and deadlines. Ordering is revisited often as new information appears.
Refinement Sessions
During refinement, the team breaks down big items, clarifies acceptance criteria, estimates effort, and identifies dependencies and risks.
Refinement vs Sprint Planning
Refinement gets items ready; sprint planning is when the team selects and commits to specific items for the next iteration.
Worked Example: Backlog Refinement in Action
University App Project
You are Product Owner for a university mobile app, a project: a temporary endeavor undertaken to create a unique product, service, or result.
Initial Epics
From stakeholders you capture epics: view course schedule, access grades, campus map, library search. These enter the product backlog as large items.
Ordering by Semester Needs
You order schedule and grades at the top due to semester deadlines; library and map are lower priority but still important.
Refinement Details
In refinement, you split "View course schedule" into smaller items, define acceptance criteria, estimate effort, and identify dependencies on campus APIs.
Exam Signal
On CAPM questions, actions that clarify, split, estimate, or reorder backlog items without freezing full scope indicate proper backlog refinement.
Iteration/Sprint Planning and Team Commitment
Purpose of Iteration Planning
Iteration or sprint planning turns ordered backlog items into a concrete short-term plan and forecast of work for the next timebox.
Inputs to Planning
Inputs include a prioritized product backlog slice, the team’s recent velocity, and their capacity considering holidays and other constraints.
Select and Goal-Set
The PO proposes top items; the team pulls what they believe they can complete and defines a clear iteration goal focusing on delivered value.
Task Breakdown
The team breaks selected items into tasks for internal planning. Tasks help manage work but usually do not appear in the product backlog.
Forecast and Commitment
The team offers a forecast, committing to the iteration goal and to doing their best to complete selected items; the PO cannot force extra work in.
Incremental Delivery, Iterative Improvement, and Definition of Done
Incremental vs Iterative
Incremental adds new usable slices of product over time; iterative revisits and improves existing slices based on feedback.
Adaptive Life Cycle
An adaptive life cycle is agile, iterative, or incremental. Detailed scope is defined and approved before each iteration, not all up front.
Definition of Done
The Definition of Done is a shared checklist of quality and completion criteria that every backlog item must meet to be considered done.
DoD Examples
Typical DoD items: code written, peer-reviewed, tested, integrated, documented, and deployed to a staging or demo environment.
DoD vs Acceptance Criteria
Acceptance criteria are specific to a single item; the DoD is global. If acceptance criteria pass but DoD steps are missing, the item is not done.
Release Planning and Forecasting With Velocity
What Is Release Planning?
Release planning looks across multiple iterations to forecast when a meaningful set of features will be ready for users or production.
Key Release Elements
Define a release goal, identify candidate backlog items, and use velocity-based forecasts to estimate how many iterations are required.
Velocity Example
If velocity is 30 points per 2-week iteration and MVP is 150 points, you forecast about 5 iterations, or roughly 10 weeks, under stable conditions.
Hybrid Alignment
In hybrid settings, release plans align with predictive milestones like quarterly reviews and are reported as ranges with clear risks and assumptions.
Forecast, Not Fixed
Release plans are forecasts. When velocity or scope changes, you reforecast and discuss trade-offs instead of treating the plan as a rigid baseline.
Hybrid Life Cycles: Blending Predictive and Agile
What Is Hybrid?
Hybrid life cycles mix predictive and adaptive elements, common when organizations cannot or do not switch fully to agile.
Predictive vs Adaptive
Predictive fixes scope, time, and cost early. Adaptive defines detailed scope iteration by iteration while using agile, iterative, or incremental delivery.
Pattern 1: Predictive Upfront
Management sets high-level scope, budget, and milestones; delivery teams use sprints and backlogs to implement within those constraints.
Pattern 2: Mixed Components
Some components (like construction) follow a predictive plan; others (like software) use agile, coordinated via integration milestones.
When Hybrid Fits
Hybrid suits cases with fixed regulatory dates, contractual baselines, or governance demands alongside uncertain, evolving solution details.
Interfaces Between Agile Teams and Predictive Governance
Why Interfaces Matter
Agile teams often work under predictive governance that expects baselines, milestones, and formal reports. You must know how to connect the two worlds.
Scope and RTM
Governance may require a requirements traceability matrix. Agile teams map backlog items to high-level requirements to show coverage without freezing detail.
Schedule and Milestones
Instead of task-level Gantt charts, agile teams share velocity-based release forecasts and milestone views like "MVP complete by end of Q3."
Reporting and Risk
Status is given via sprint reviews and visual charts, while risks are managed by reordering backlog items or adding investigative spikes.
Change Control Balance
Product Owners handle most scope changes via backlog ordering; major changes that affect budget or commitments still go through formal change control.
Quiz: Backlogs and Iteration Planning
Test your understanding of product backlogs and iteration planning.
A team is preparing for the next iteration. The Product Owner has ordered the product backlog. During iteration planning, what should the team do FIRST?
- Break all items in the product backlog into detailed tasks for the next three months.
- Select the highest-ordered items they believe they can complete, then define an iteration goal.
- Ask the steering committee to approve the detailed iteration task list.
- Freeze the product backlog so that no changes can be made during the iteration.
Show Answer
Answer: B) Select the highest-ordered items they believe they can complete, then define an iteration goal.
In iteration (sprint) planning, the team first pulls the highest-ordered product backlog items they believe they can complete, based on capacity and past velocity, and then defines an iteration goal. Breaking all backlog items into tasks months ahead, seeking steering committee approval for task lists, or freezing the entire backlog are predictive-style behaviors that do not match agile iteration planning.
Quiz: Hybrid and Governance Interfaces
Check your understanding of hybrid life cycles and governance interfaces.
In a hybrid project, executives require a requirements traceability matrix, but the software team works with a product backlog. What is the BEST way for the project manager to respond?
- Stop using the product backlog and switch entirely to the requirements traceability matrix.
- Tell executives that agile projects do not use any formal requirements documentation.
- Map high-level requirements in the traceability matrix to corresponding product backlog items.
- Ask the Product Owner to sign a document stating that the backlog replaces all governance requirements.
Show Answer
Answer: C) Map high-level requirements in the traceability matrix to corresponding product backlog items.
In a hybrid environment, the project manager should bridge agile and predictive practices. Mapping high-level requirements to backlog items in the requirements traceability matrix satisfies governance needs while preserving agile backlog usage. Abandoning the backlog, rejecting all documentation, or trying to override governance with a PO statement are inappropriate.
Thought Exercise: Choosing Predictive, Agile, or Hybrid
How to Use This Exercise
For each scenario, pick predictive, adaptive, or hybrid, then write one sentence explaining why. Compare your reasoning to the patterns you learned.
Scenario A: Bridge Project
Government bridge, strict safety standards, design approved up front, changes later are very costly. Predictive / Adaptive / Hybrid? Why?
Scenario B: New Mobile App
Startup app, unclear user preferences, desire to experiment and release frequently to learn. Predictive / Adaptive / Hybrid? Why?
Scenario C: Bank Regulation
Fixed regulatory deadline in 10 months, some mandatory features, flexible UX, PMO wants quarterly milestones. Predictive / Adaptive / Hybrid? Why?
Reflect on Patterns
Check if you chose predictive when change is costly, adaptive when learning is key, and hybrid when fixed constraints meet flexible solution details.
Key Term Flashcards: Backlogs, Life Cycles, Governance
Flip through these cards to reinforce core definitions and distinctions that often appear on the CAPM exam.
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- Definition of Done (DoD)
- A shared checklist of activities and quality criteria that must be met for a backlog item or increment to be considered complete and potentially releasable.
- hybrid life cycle (concept)
- An approach that combines predictive elements (such as fixed milestones or scope baselines) with adaptive delivery (such as sprints and backlogs) within the same project.
- backlog refinement
- An ongoing activity where the Product Owner and team clarify, split, estimate, and reorder backlog items so that high-priority work is ready for upcoming iterations.
Key Terms
- project
- A temporary endeavor undertaken to create a unique product, service, or result.
- velocity
- A measure of the amount of work an agile team completes in an iteration, often used to forecast future delivery.
- stakeholder
- An individual, group, or organization who may affect, be affected by, or perceive itself to be affected by a decision, activity, or outcome of a project, program, or portfolio.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- release planning
- An activity that looks across multiple iterations to define a release goal, select candidate backlog items, and forecast when a meaningful set of features will be ready.
- hybrid life cycle
- An approach that combines predictive elements such as fixed scope baselines or milestones with adaptive delivery practices such as sprints and product backlogs within the same project.
- backlog refinement
- An ongoing activity where the Product Owner and team clarify, split, estimate, and reorder backlog items so that high-priority work is ready for upcoming iterations.
- acceptance criteria
- A set of conditions that is required to be met before deliverables are accepted.
- adaptive life cycle
- A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration.
- predictive life cycle
- A development life cycle in which the project scope, time, and cost are determined in the early phases of the life cycle.
- Definition of Done (DoD)
- A shared checklist of activities and quality criteria that must be met for a backlog item or increment to be considered complete and potentially releasable.
- requirements traceability matrix
- A grid that links product requirements from their origin to the deliverables that satisfy them.