7.3 Kanban, XP, and SAFe

CAPM Certified Associate in Project Management Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & CAPM Exam Overview

1.1 About the CAPM Exam 1.2 PMBOK 7th Edition Overview 1.3 Exam Content Outline (ECO) 1.4 CAPM vs. PMP: Understanding the Differences

2 Chapter 2: Project Life Cycles and Processes (Domain 1, Tasks 1-2)

2.1 Projects, Programs, and Portfolios 2.2 Project Life Cycle Phases 2.3 The Five Process Groups 2.4 The Ten Knowledge Areas

3 Chapter 3: Project Management Planning (Domain 1, Task 2)

3.1 The Project Management Plan 3.2 Scope Management and the WBS 3.3 Schedule Management 3.4 Cost Management and Earned Value 3.5 Quality Management

4 Chapter 4: Project Roles, Responsibilities, and Ethics (Domain 1, Tasks 3-4)

4.1 Project Roles and Responsibilities 4.2 Leadership and Emotional Intelligence 4.3 Risk Management Fundamentals 4.4 PMI Code of Ethics and Professional Conduct 4.5 Problem-Solving Tools and Techniques

5 Chapter 5: Resource, Communication, and Stakeholder Management (Domain 1, Tasks 2-3)

5.1 Resource Management 5.2 Communications Management 5.3 Stakeholder Management 5.4 Procurement Management 5.5 Issues, Risks, Assumptions, and Constraints

6 Chapter 6: Predictive, Plan-Based Methodologies (Domain 2)

6.1 When to Use a Predictive Approach 6.2 WBS, Work Packages, and Activity Definition 6.3 Predictive Project Controls and Artifacts 6.4 Critical Path and Schedule Calculations

7 Chapter 7: Agile Frameworks and Methodologies (Domain 3, Tasks 1-3)

7.1 When to Use an Adaptive (Agile) Approach 7.2 The Scrum Framework 7.3 Kanban, XP, and SAFe 7.4 Agile Planning, Estimation, and Metrics 7.5 Agile Project Controls and Artifacts

8 Chapter 8: Business Analysis Roles and Stakeholder Communication (Domain 4, Tasks 1-2)

8.1 Business Analysis Roles and Responsibilities 8.2 Stakeholder Communication in Business Analysis 8.3 Business Case and Needs Assessment

9 Chapter 9: Requirements Gathering and Product Roadmaps (Domain 4, Tasks 3-4)

9.1 Requirements Gathering Approaches 9.2 Requirements Traceability Matrix 9.3 Product Roadmaps

10 Chapter 10: BA Methodologies and Requirements Validation (Domain 4, Tasks 5-6)

10.1 Business Analysis in Predictive and Agile Approaches 10.2 Acceptance Criteria and Requirements Validation 10.3 Business Analysis Tools and Techniques Summary

7.3 Kanban, XP, and SAFe

Key Takeaways Explain This Topic AI

Kanban prescribes no roles, iterations, or ceremonies; its defining feature is explicit Work-in-Progress (WIP) limits that pull work and expose bottlenecks

Little's Law links Kanban metrics: average Cycle Time = average WIP / average Throughput

Extreme Programming (XP) emphasizes engineering practices — pair programming, test-driven development, continuous integration, refactoring — guided by five values

SAFe scales agile across many teams using the Agile Release Train (50-125 people) and a Program Increment of typically 8-12 weeks set in PI Planning

Lean's seven principles (Poppendiecks) — eliminate waste, amplify learning, decide late, deliver fast, empower the team, build integrity in, optimize the whole — underpin all agile

Last updated: June 2026

Kanban

Kanban (Japanese for "signboard") is a lean, flow-based method for managing knowledge work. Unlike Scrum, it prescribes no roles, no fixed iterations, and no ceremonies — you overlay it on your existing process and improve evolutionarily.

The core practices

Practice What it means
Visualize the workflow A Kanban board shows every item and its stage
Limit Work in Progress (WIP) Cap items per column to stop overloading
Manage flow Optimize the smooth movement of work
Make policies explicit Document the rules (e.g., "Done = peer reviewed")
Implement feedback loops Cadenced reviews to inspect and adapt
Improve collaboratively, evolve experimentally Continuous, incremental change
WIP limits — the defining feature

A column with a WIP limit of 3 accepts no new item until one moves forward. This is a pull system : capacity, not a manager, decides when work starts. WIP limits expose bottlenecks (work piles up before the constrained stage) and shorten cycle time.

Flow metrics and Little's Law

Metric Definition
Lead Time Customer request to delivery
Cycle Time Work start to work finish
Throughput Items completed per period
Cumulative Flow Diagram (CFD) Items in each stage over time

Little's Law ties them together: average Cycle Time = average WIP / average Throughput . Cutting WIP (with everything else equal) reduces cycle time — a common CAPM/PMI-ACP fact. Kanban is the natural choice for support, maintenance, and operations work with a continuous, unpredictable intake.

Extreme Programming (XP)

Extreme Programming (XP) , created by Kent Beck, pushes technical excellence to the extreme for software teams. Its five values are Communication, Simplicity, Feedback, Courage, and Respect .

XP Practice Description
Pair Programming Two developers, one workstation, continuous review
Test-Driven Development (TDD) Write the failing test before the code
Continuous Integration (CI) Integrate and test many times per day
Refactoring Improve structure without changing behavior
Small/Frequent Releases Short cycles for rapid feedback
Collective Code Ownership Anyone can improve any code
Coding Standards Shared conventions
Simple Design The simplest design that works
On-Site Customer A customer available to the team
Sustainable Pace Roughly 40-hour weeks; no death marches

CAPM links XP to engineering quality : if a question describes failing builds, defect-prone code, or no automated tests, the XP practices (CI, TDD, pairing, refactoring) are the answer — not a new Scrum role.

SAFe (Scaled Agile Framework)

SAFe scales agile to dozens or hundreds of people across many teams building one large solution.

Level Focus Key construct
Team Individual agile teams Scrum or Kanban teams
Program (ART) Teams aligned to a value stream Agile Release Train (ART)
Large Solution Multiple ARTs Solution Train
Portfolio Strategy and funding Lean Portfolio Management
Key SAFe terms

Concept Definition
Agile Release Train (ART) A team-of-teams, 50–125 people , that plans and delivers together
Program Increment (PI) A planning interval, typically 8–12 weeks , of several iterations
PI Planning A cadenced event where the whole ART aligns on PI objectives
Architectural Runway Existing tech enabling near-term features
Innovation & Planning (IP) Iteration Buffer iteration for innovation and slack
WSJF Weighted Shortest Job First — SAFe's prioritization formula

Use SAFe when many teams must coordinate; it is overkill for a single small team (a frequent distractor).

Lean Principles

Lean thinking (Mary and Tom Poppendieck , Lean Software Development ) underpins agile with seven principles:

Eliminate waste — remove anything not adding value.

Amplify learning — short feedback loops.

Decide as late as possible — keep options open to the last responsible moment.

Deliver as fast as possible — short cycle times.

Empower the team — give autonomy.

Build integrity in — quality is everyone's job.

Optimize the whole — improve the full value stream, not silos.

Choosing a Framework

Feature Scrum Kanban XP SAFe
Cadence Fixed Sprints Continuous flow Short releases PI (8–12 wks)
Roles PO, SM, Developers None prescribed Coach, Customer, Developers Many
Defining feature Time-boxed iterations WIP limits Engineering practices ART + PI Planning
Best for Most team projects Support/maintenance flow Technical quality Large enterprises
Scrumban and Combining Frameworks

Real teams often blend frameworks, and the exam expects you to recognize the hybrids. Scrumban keeps Scrum's roles and cadence but adds Kanban's WIP limits and pull-based flow — popular for maintenance teams transitioning off Scrum or Scrum teams drowning in unplanned work. Many teams also run Scrum with XP engineering practices : Scrum supplies the management wrapper (roles, events, backlog) while XP supplies the technical discipline (TDD, continuous integration, pairing). These are not contradictions; Scrum is intentionally silent on engineering technique, so layering XP fills the gap.

When a question pairs a delivery cadence with a technical-quality problem, the strongest answer often combines the two rather than choosing only one.

Choosing Among the Frameworks — Worked Scenarios

Consider three quick scenarios. A help-desk team handles a steady stream of unpredictable tickets and wants to cap simultaneous work and surface bottlenecks. The pull system, WIP limits, and lack of fixed iterations make Kanban the fit. A 90-person product organization with eight teams must release one coordinated solution every quarter. The need to align many teams on a cadenced planning interval points to SAFe , with its Agile Release Train and Program Increment. A single eight-person team building a new product with evolving requirements wants regular feedback and a simple, well-known structure. That is textbook Scrum .

Matching the scale and the dominant problem — flow, scaling, technical quality, or iterative delivery — to the framework's defining feature is exactly how CAPM frames these items, so anchor your choice to that defining feature rather than to surface keywords.