Pebellslearn by building
0%
RoadmapsMatrixCoursesSandboxSign in
SDLC Delivery Models  ›  Capstone Project

Kanban, XP and SAFe

Kanban 15 minKanban limits work in progress on a visible board, XP uses engineering practices such as test-driven development and pairing, and SAFe coordinates many Agile teams on one large product.

Kanban, XP and SAFe

Basketly's support team fixes small problems all day and could never plan them into two-week sprints. The core team wants to write better-tested code. And Basketly's parent company has twelve teams that must release together. Three different problems, three different Agile approaches.

The rule

Kanban limits the flow, XP sharpens the craft, SAFe aligns many teams.

Kanban shows work as cards moving across a board, for example To do → In progress → Testing → Done. Its key rule is the WIP limit (work in progress): each column may hold only so many cards. When a column is full, nobody pushes more into it; people help finish what is there. There are no sprints; work is pulled continuously, which suits steady streams like support fixes.

XP (Extreme Programming) is about engineering habits that keep quality high:

  • Test-driven development: write a failing test first, then the code to pass it.
  • Pair programming: two people at one problem, reviewing as they go.
  • Continuous integration: merge and run the automated tests many times a day.
  • Small releases and simple design.

SAFe (Scaled Agile Framework) coordinates many Agile teams working on one large product. Teams are grouped into an Agile Release Train and plan together in fixed program increments of several sprints, so their pieces fit at release time. For testers it adds system-level testing across teams on top of each team's own testing.

The shortcut

Match the approach to the problem with one question each: Is work an unplanned stream? Kanban. Is code quality the pain? XP practices. Must many teams ship one product together? SAFe.

A jam in the Testing columnStep 1 of 4
  1. Read the board

    Testing holds 3 cards and its WIP limit is 3. A developer finishes card 4.

The trap is treating a WIP limit as a suggestion. Without it, the Testing column quietly fills with twenty cards and the board hides the jam instead of showing it.

Drills

Answer fast — trust the rule.

quick drill

A Kanban column is at its WIP limit. What should a free team member do?

quick drill

Which is an XP practice?

quick drill

Twelve teams must release one product together. Which approach addresses that?

quick drill

Basketly's support team handles unpredictable fixes all day. What fits best?

Remember

  • Kanban limits the flow, XP sharpens the craft, SAFe aligns many teams.
  • Ask: unplanned stream? code quality? many teams?
  • A WIP limit is a rule, not a suggestion; full columns mean swarm, not start.

Practice — level up

0/1 solved

Write your answer, then compare it with a rubric and a model answer.

ExplainThe testing column is full

Basketly's Kanban board has a Testing column with a WIP limit of 3, and it is full. A developer finishes a new card. Explain what should happen next under Kanban and why, and name one XP practice that would help the team avoid this jam.