Kanban, XP, and SAFe

While Scrum is the most popular agile framework, the CAPM exam also tests your knowledge of other adaptive methodologies. Understanding when to use each framework and their distinguishing characteristics is essential.

Kanban

Kanban is a lean method for managing and improving work across human systems. Unlike Scrum, Kanban does not prescribe roles, iterations, or ceremonies.

Core Kanban Practices

The Kanban Board

A typical Kanban board has columns representing workflow stages:

| To Do | In Progress (WIP: 3) | Review (WIP: 2) | Done |
|-------|----------------------|-----------------|------|
| Item A| Item D               | Item F          | Item H|
| Item B| Item E               | Item G          | Item I|
| Item C|                      |                 |      |

WIP Limits

WIP limits are the defining feature of Kanban:

• Each column has a maximum number of items allowed
• When a column is at its WIP limit, no new items can enter until one moves forward
• This prevents overloading and improves flow
• It makes bottlenecks visible — work piles up before bottleneck stages

Kanban Metrics

---

Extreme Programming (XP)

Extreme Programming (XP) is an agile methodology that emphasizes technical excellence and engineering practices. It is particularly focused on software development.

XP Values

1. Communication — Team members and stakeholders communicate openly
2. Simplicity — Do the simplest thing that works
3. Feedback — Get frequent feedback to guide development
4. Courage — Make bold decisions and speak up
5. Respect — Respect team members and their contributions

Key XP Practices

---

SAFe (Scaled Agile Framework)

SAFe is a comprehensive framework for scaling agile practices across large organizations with multiple teams working on related products.

SAFe Levels

Key SAFe Concepts

---

Lean Principles

Lean thinking underpins many agile frameworks. The seven Lean principles (from Lean Software Development by Mary and Tom Poppendieck):

1. Eliminate waste — Remove anything that does not add value
2. Amplify learning — Develop knowledge through short feedback loops
3. Decide as late as possible — Keep options open until the last responsible moment
4. Deliver as fast as possible — Shorten cycle times to deliver value quickly
5. Empower the team — Give teams autonomy and authority
6. Build integrity in — Quality is everyone's responsibility
7. Optimize the whole — Focus on the entire value stream, not just individual components

---

Comparing Agile Frameworks