SkarpChapter 10 of 20
Agile Mindset and Adaptive Approaches: From Principles to Practice
Shift gears into adaptive thinking by exploring the agile mindset, values, and principles that underpin modern iterative and incremental delivery. You’ll see how adaptive approaches respond to change and uncertainty in ways predictive methods cannot.
From Predictive to Adaptive: Why Agile Matters
Switching Gears
You previously studied predictive projects: plan-driven work where scope, time, and cost are fixed early and controlled using baselines and measures like schedule variance.
Two Life Cycle Families
PMI distinguishes a predictive life cycle (scope, time, cost set early) and an adaptive life cycle: "A development life cycle that is agile, iterative, or incremental."
Adaptive in Practice
Adaptive is an umbrella: it includes agile frameworks (Scrum, Kanban) and iterative or incremental approaches that do not use the full agile toolkit.
Exam Angle
CAPM questions often describe a scenario and ask which response fits best: predictive or adaptive. You must recognize when adaptive thinking is more appropriate.
Agile Mindset, Values, and Principles (High Level)
What Is the Agile Mindset?
The agile mindset is a way of thinking that emphasizes customer value, learning, collaboration, transparency, and responding to change instead of resisting it.
Core Agile Values
Four key value pairs: individuals and interactions, working product, customer collaboration, and responding to change are prioritized over their traditional counterparts.
Principles in Practice
Agile principles include frequent delivery of small increments, welcoming change, close collaboration with business stakeholders, and regular reflection and adaptation.
Exam Trap
If a team claims to be agile but forbids change and delays delivery, CAPM questions expect you to see this is not aligned with the agile mindset.
Adaptive Life Cycle and PMI Definition
PMI's Adaptive Definition
PMI defines adaptive life cycle as: "A development life cycle that is agile, iterative, or incremental. The detailed scope is defined and approved before the start of an iteration."
What This Implies
Adaptive is an umbrella: it includes agile, iterative, and incremental. Work is done in short cycles with detailed scope agreed before each iteration.
Rolling Wave Planning
Adaptive teams plan just enough for the near term, then refine plans as they learn. Scope evolves; timeboxes and team capacity are more stable.
Recognizing on the Exam
If a scenario shows evolving requirements and short, repeating cycles with detailed scope per cycle, the best label is usually "adaptive life cycle."
Iterative vs Incremental vs Agile Delivery
Incremental Delivery
Incremental delivery releases the product in usable pieces. Each increment adds new functionality that can be used or tested right away.
Iterative Delivery
Iterative delivery refines the same product through repeated cycles. Each iteration improves quality or detail, but may not be fully usable alone.
Agile Delivery
Agile combines iterative and incremental: each short iteration delivers a potentially shippable increment and includes feedback and adaptation.
Exam Traps
Multiple non-usable prototypes suggest iterative. Usable pieces never revisited suggest incremental. Both together with feedback loops point to agile.
Worked Examples: Classifying Delivery Approaches
Scenario 1: Park Redesign
Sketches → 3D renderings → detailed blueprint. Public only sees the final design. This is iterative: repeated refinement of one design, not usable increments.
Scenario 2: Banking App
Version 1: balances; Version 2: transfers; Version 3: deposits. Each release is usable. This is incremental: adding pieces that users can use.
Scenario 3: Learning Platform
Two-week sprints deliver catalog, then improved catalog plus video, then refined video plus quizzes, based on feedback. This is agile.
Link to Exam
When reading CAPM questions, look for clues about usability of increments and whether previous work is being refined to classify the approach.
Adaptive Life Cycle in Practice: Planning, Execution, Control
Planning in Adaptive
Adaptive teams keep a high-level roadmap but plan details only for the next iteration, often by selecting work from a product backlog or similar list.
Executing Iterations
Cross-functional teams work in short cycles, self-organizing around an iteration goal and demonstrating a usable increment at the end.
Controlling Adaptively
Control emphasizes delivered value and feedback, using tools like burn-down charts and backlog tracking, not just baseline comparisons.
Comparing to Predictive
Predictive control relies on baselines and measures like schedule variance. Adaptive control relies on frequent delivery and continuous re-planning.
Thought Exercise: Choosing Adaptive vs Predictive
Apply what you know about adaptive life cycles by classifying projects. There are no strict right answers here, but your reasoning should be consistent with PMI-style thinking.
Exercise 1: Hospital Patient-Record System Upgrade
- The hospital must comply with strict regulatory requirements already documented in detail.
- Downtime must be minimized, and the go-live date is fixed due to a contract with an external vendor.
- Requirements are stable and approved by a steering committee.
Ask yourself:
- Would a predictive life cycle or an adaptive life cycle fit better? Why?
- Which risks would adaptive help manage? Which might it introduce?
Exercise 2: New Social Media Feature for a Startup
- The product team has a vision but is unsure which specific features users will love.
- The market changes quickly and competitors release new features every month.
- The startup wants to test ideas with real users and pivot if needed.
Ask yourself:
- Which life cycle family (predictive vs adaptive) fits best? Why?
- Would you favor more iterative, incremental, or fully agile delivery?
How to use this exercise
- Pause and write a 2–3 sentence justification for each scenario.
- Check your answers against key criteria: uncertainty level, requirement stability, regulatory constraints, and stakeholder involvement.
- Try to phrase your reasoning in exam language: "Because requirements are evolving and stakeholder feedback is critical, an adaptive life cycle is most appropriate."
Quiz 1: Mindset and Life Cycles
Check your understanding of agile mindset and adaptive life cycles.
A project team is working in two-week cycles. Before each cycle, they agree on a detailed set of items to complete. Requirements are expected to evolve throughout the project. Which PMI term best describes this approach?
- Predictive life cycle
- Adaptive life cycle
- Work breakdown structure
- Requirements traceability matrix
Show Answer
Answer: B) Adaptive life cycle
**Adaptive life cycle** is correct because the team works in short cycles (iterations), defines detailed scope before each iteration, and expects evolving requirements, which matches PMI's definition. A predictive life cycle would fix scope, time, and cost early. Work breakdown structure and requirements traceability matrix are artifacts, not life cycle types.
Quiz 2: Iterative vs Incremental vs Agile
Test your ability to classify delivery approaches.
A design agency creates a series of prototypes for a new product. Each prototype is tested with users, then significantly revised in the next cycle. Users cannot actually use the product in real life until the final version is released. What BEST describes this delivery approach?
- Incremental delivery
- Iterative delivery
- Agile delivery
- Predictive life cycle
Show Answer
Answer: B) Iterative delivery
**Iterative delivery** is correct because the team repeatedly refines the same product through prototypes that are not fully usable in real life until the end. Incremental delivery would provide usable pieces along the way. Agile combines iterative and incremental with frequent, potentially shippable increments. "Predictive life cycle" is a broader life cycle category and does not specifically describe this refinement pattern.
Key Terms Review: Predictive vs Adaptive
Flip these cards to reinforce key definitions and contrasts you will see on the CAPM exam.
- 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.
- Agile mindset
- A way of thinking that prioritizes customer value, collaboration, learning, transparency, and responding to change over rigidly following a pre-set plan.
- Incremental delivery
- An approach where the product is delivered in usable pieces (increments), each adding new functionality that can be used or tested immediately.
- Iterative delivery
- An approach where the team repeatedly refines the same product or component through cycles, improving quality or detail with each iteration.
- Agile delivery
- An adaptive approach that combines iterative refinement and incremental delivery in short cycles, providing potentially shippable increments and incorporating frequent feedback.
- When to favor adaptive approaches
- When requirements are uncertain or evolving, stakeholder involvement is high, feedback cycles are critical, and the organization can accept changing scope.
- Control in adaptive projects
- Emphasizes delivered value, feedback, and frequent re-planning, using tools like completed backlog items and burn-down charts rather than only baseline variance.
When to Use Adaptive Approaches (and When Not To)
When Adaptive Fits
Use adaptive when requirements are unclear or changing, stakeholders can give frequent feedback, the environment is fast-moving, and early value is important.
When Predictive Fits
Use predictive when requirements are stable, constraints like time and budget are fixed, and feedback is limited or formalized through sign-offs.
Reading Exam Signals
High uncertainty, evolving requirements, and collaboration point to adaptive. Detailed up-front specs and strict baselines point to predictive.
Practice the Justification
On questions, mentally state: "Because of these characteristics, an adaptive (or predictive) life cycle is most appropriate." This sharpens your exam instincts.
Key Terms
- 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.
- Agile mindset
- A way of thinking that prioritizes customer value, collaboration, learning, transparency, and responding to change over rigidly following a pre-set plan.
- agile delivery
- An adaptive approach that combines iterative refinement and incremental delivery in short cycles, providing potentially shippable increments and incorporating frequent feedback.
- iterative delivery
- An approach where the team repeatedly refines the same product or component through cycles, improving quality or detail with each iteration.
- 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.
- incremental delivery
- An approach where the product is delivered in usable pieces (increments), each adding new functionality that can be used or tested immediately.
- 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.