SkarpChapter 12 of 21
Agile Mindset and Empirical Process Control
Shift from plan‑driven thinking to an agile mindset grounded in transparency, inspection, and adaptation, and see why agile thrives when change is constant and early feedback is essential.
From Plan-Driven to Agile Mindset
Connecting to What You Know
Predictive planning locks scope, time, and cost early and uses baselines and formal change control. Agile assumes uncertainty and uses short cycles and feedback instead of heavy upfront plans.
Key Canonical Definitions
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."
What Is an Agile Mindset?
Agile is not "no planning." It is customer and value focused, experiment-friendly, change-embracing, and team-centered with cross-functional, self-organizing teams making local decisions quickly.
Why It Matters for CAPM
Exam questions will ask you to choose predictive, adaptive, or hybrid approaches. Agile thinking changes how you manage risk, scope, and control: you inspect and adapt, not just enforce the original plan.
Adaptive Life Cycle and Empirical Process Control
Adaptive Life Cycle Recap
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."
What Is Empirical Control?
Empirical process control means you manage work based on observation and measurement instead of assuming your initial plan is accurate in a changing environment.
Pillar 1: Transparency
Transparency means the true state of the product and process is visible: boards, Definition of Done, open defect lists, and clear progress metrics support honest decision making.
Pillar 2: Inspection
Inspection is frequent examination of product and process: sprint reviews, daily scrums, and Kanban flow reviews help detect problems and learning opportunities early.
Pillar 3: Adaptation
Adaptation means changing scope, plans, or process in response to what you inspect. Agile teams adjust backlogs, priorities, and practices quickly when reality changes.
Exam Signal
If a scenario mentions short iterations, evolving scope, and frequent feedback, you are in adaptive/agile territory using empirical control, not long-term fixed baselines alone.
Iterative vs Incremental Delivery, MVPs, and Small Slices
Iterative Delivery
Iterative means refining the same part of the product in cycles. You build something, get feedback, and improve it repeatedly, like redesigning a UI several times.
Incremental Delivery
Incremental means adding new, complete pieces of functionality over time. Each increment is usable, like releasing login, then profile, then messaging features.
Using Both Together
Most agile work is both iterative and incremental: each iteration delivers at least one usable increment, and you refine and extend what already exists over time.
Minimum Viable Product (MVP)
An MVP is the smallest set of features that delivers real value and lets you learn from users. It is intentionally small but coherent, not a broken or low-quality product.
Small Usable Slices
Small vertical slices cut through UI, logic, and data so each slice is fully usable, such as "search by name only" instead of a large technical component with no user value.
Exam Angle
When early feedback, high risk, or unclear requirements appear in scenarios, expect iterative, incremental delivery with MVPs and small slices to be the best-fit approach.
Agile Roles and Empirical Planning
Product Owner
The Product Owner owns vision and value. They manage the product backlog: "An ordered list of everything that is known to be needed in the product, managed by the product owner."
Scrum Master
The Scrum Master is a servant-leader, not a command-and-control boss. They coach on Scrum and empirical control, facilitate events, and remove impediments.
Developers
Developers include everyone who builds the increment, not just coders. They are cross-functional and self-organizing, deciding how to accomplish the work.
Empirical Planning Cycle
Before an iteration: select backlog items and plan. During: inspect progress daily and adapt. After: review the increment and process, then adapt the backlog and ways of working.
Exam Traps
Wrong patterns: Scrum Master collecting status for management; managers reordering the backlog. Correct: PO orders backlog, Scrum Master coaches, developers decide how to do the work.
When to Use Predictive, Adaptive, or Hybrid
When Predictive Fits
Use predictive when requirements are stable, technology is familiar, and cost of change rises steeply, such as in construction or tightly regulated physical projects.
Predictive Definition
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."
When Adaptive Fits
Use adaptive when requirements are uncertain or volatile, markets change quickly, and you can keep cost of change flatter with automation and modular design.
Adaptive Definition
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."
Hybrid Situations
Hybrid mixes predictive and adaptive: for example, predictive for fixed infrastructure and adaptive sprints for software, or predictive milestones with agile teams inside.
Exam Keywords
Predictive: fixed price, detailed upfront requirements. Adaptive: unclear requirements, MVP, frequent feedback. Hybrid: some elements fixed, others evolving together.
Worked Scenarios: Choosing the Right Life Cycle
Scenario 1: Hospital Wing
Strict building codes, complete drawings, fixed-price contract, and high cost of change point to a predictive life cycle with detailed upfront planning and baselines.
Scenario 2: Startup App
Unclear features, fast-moving market, and cheap frequent releases point to an adaptive life cycle with MVPs, small slices, and user feedback.
Scenario 3: Smart Building
Physical structure is costly to change, while IoT software will evolve. This mix suggests a hybrid approach: predictive for construction, adaptive for software.
Decision Pattern
In all cases, base your choice on requirement stability, uncertainty, and cost of change, then check which life cycle pattern best matches those conditions.
Thought Exercise: Transparency, Inspection, Adaptation in Your Context
Use this reflection to make the three empirical pillars concrete. Imagine you are leading a small agile team building a new feature for your university's learning portal.
Work through these prompts (you can jot notes on paper or in a doc):
- Transparency
- List 3 things your stakeholders would want to see at any time (e.g., which features are in progress, current defects, demo environment URL).
- For each, write how you would make it transparent (e.g., online Kanban board, automated dashboard, weekly demo video).
- Inspection
- Identify at least 3 regular events where people can inspect the product or process.
- For each event, note who participates and what they inspect.
- Example events: daily team check-in, end-of-iteration demo, monthly metrics review.
- Adaptation
- For each inspection event above, write 1–2 typical adaptations you might make.
- Examples: reordering the product backlog, changing the Definition of Done, adjusting WIP limits, adding tests.
- Connect to CAPM
- Now phrase one of your adaptation examples as if it were an exam scenario: “After inspecting X, the team decides to Y. Which agile principle or pillar does this illustrate?”
- Make sure you can clearly point to transparency, inspection, or adaptation as the main concept.
This kind of mental practice makes it easier to recognize empirical control patterns quickly when you see them in exam questions.
Quick Check: Empirical Process Control
Test your understanding of transparency, inspection, and adaptation.
During a sprint review, stakeholders see the working increment and request a change in priorities for upcoming features. The Product Owner reorders the product backlog based on this feedback. Which empirical pillar is MOST directly illustrated by the Product Owner's action?
- Transparency
- Inspection
- Adaptation
- Predictive control
Show Answer
Answer: C) Adaptation
The sprint review itself is inspection, but the key action described is the Product Owner reordering the product backlog based on what was learned. Changing the plan in response to inspected information is adaptation. Transparency made the state visible, inspection gathered feedback, and adaptation updated the plan.
Quick Check: Choosing a Life Cycle
Apply life cycle selection to a CAPM-style scenario.
A company is upgrading an internal HR system. Legal requirements for data retention are fully documented and stable. However, employee-facing features (self-service, mobile access) are not well understood, and leadership wants frequent feedback from pilot users. What is the MOST appropriate overall approach?
- Fully predictive life cycle for both back-end and front-end components
- Fully adaptive life cycle for both back-end and front-end components
- Hybrid approach: predictive for compliance-critical back-end, adaptive for user-facing features
- Delay the project until all requirements are fully documented
Show Answer
Answer: C) Hybrid approach: predictive for compliance-critical back-end, adaptive for user-facing features
The compliance-critical back-end has stable requirements and high risk if changed incorrectly, so predictive planning is suitable. The user-facing features have uncertain requirements and need feedback, favoring an adaptive approach. A hybrid life cycle that combines both is the best fit.
Key Terms Review
Use these flashcards to reinforce core definitions and concepts you will see on the CAPM.
- 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.
- Empirical process control
- A way of managing work that relies on transparency, inspection, and adaptation so decisions are based on observed reality rather than detailed upfront predictions.
- Product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- Iterative delivery
- An approach where the same part of the product is refined through repeated cycles to improve quality or understanding.
- Incremental delivery
- An approach where new, complete pieces of functionality are added over time, with each increment being usable and potentially releasable.
- Minimum Viable Product (MVP)
- The smallest set of features that delivers real value to early users and allows the team to learn about product-market fit.
- Small usable slice
- A thin vertical piece of functionality that is fully usable by a user, typically cutting across UI, logic, and data layers.
- Transparency (agile pillar)
- Making the true state of the product and process visible to those who make decisions, using tools like boards, definitions of done, and clear metrics.
- Inspection (agile pillar)
- Frequent examination of the product and process to detect problems, risks, or learning opportunities early.
- Adaptation (agile pillar)
- Adjusting scope, plans, or ways of working in response to what inspection reveals, such as reordering the backlog or changing team practices.
Pulling It Together and Next Steps in Your Study Path
Life Cycle Summary
Predictive fixes scope, time, and cost early and suits stable, high-cost-of-change work. Adaptive defines detailed scope per iteration and suits volatile needs and frequent feedback.
Empirical Pillars Recap
Agile relies on transparency, inspection, and adaptation: make work visible, inspect product and process often, and change course quickly when reality disagrees with the plan.
Delivery and Roles
Iterative and incremental delivery with MVPs and small slices lowers risk. Product Owner orders the product backlog, Scrum Master coaches, and developers self-organize.
Choosing an Approach
Select predictive, adaptive, or hybrid by analyzing requirement stability, uncertainty, and cost of change in each scenario.
Skarp Next Steps
Next in this course: take the agile diagnostic, attempt the mock exam, then use your spaced review queue and gap guide to deepen any weak spots on these concepts.
Key Terms
- adaptation
- Adjusting scope, plans, or ways of working in response to what inspection reveals.
- inspection
- Frequent examination of the product and process to detect problems, risks, or learning opportunities.
- transparency
- Making the true state of the product and process visible to those who make decisions.
- product backlog
- An ordered list of everything that is known to be needed in the product, managed by the product owner.
- hybrid life cycle
- A combination of predictive and adaptive approaches used within a single project, aligning different components to their uncertainty and change profile.
- iterative delivery
- An approach where the same part of the product is refined through repeated cycles to improve quality or understanding.
- small usable slice
- A thin vertical piece of functionality that is fully usable by a user, typically including UI, logic, and data.
- 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 new, complete pieces of functionality are added over time, with each increment being usable and potentially releasable.
- 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.
- empirical process control
- A way of managing work that relies on transparency, inspection, and adaptation so decisions are based on observed reality.
- Minimum Viable Product (MVP)
- The smallest set of features that delivers real value to early users and allows the team to learn about product-market fit.