Scrum, Extreme Programming (XP), and Lean are the three foundational Agile approaches. Most enterprise practitioners work with Scrum but encounter XP practices (TDD, pair programming) and Lean thinking (WIP limits, flow) daily. Understanding all three makes you a significantly more effective Agile practitioner.
Framework Comparison
| Dimension | Scrum | XP | Lean Software |
|---|---|---|---|
| Primary focus | Delivery management | Engineering practices | Flow efficiency |
| Iteration length | 1–4 weeks (Sprint) | 1–2 weeks | Continuous (no fixed iteration) |
| Prescribed roles | SM, PO, Dev Team | Customer, Coach, Programmer | None prescribed |
| Prescribed events | 5 events | Stand-up, planning | None prescribed |
| Engineering practices | None (Scrum-specific) | TDD, pair programming, CI, refactoring | Partial |
| WIP management | Sprint backlog limits | Small releases | Explicit WIP limits (Kanban influence) |
| Customer involvement | PO as proxy | Customer on-site | Value stream focus |
Scrum: The Framework
Scrum is a process framework, not a methodology. It defines three roles, five events, and three artefacts. It deliberately says nothing about engineering practices — TDD, CI/CD, code review, and architecture are outside its scope. This is both Scrum's flexibility and its main weakness: teams can "do Scrum" perfectly by the ceremony calendar while producing terrible code.
Extreme Programming: Engineering Excellence
XP is the opposite of Scrum in one important way: it cares deeply about how code is written. XP's core practices include Test-Driven Development (write the test before the code), Pair Programming (two developers sharing one workstation), Continuous Integration (merge and build multiple times per day), Simple Design (the simplest solution that could possibly work), and Collective Code Ownership (anyone can change any code).
Lean Software Development
Mary and Tom Poppendieck translated Toyota Production System thinking to software in their 2003 book. The seven Lean principles — Eliminate Waste, Build in Quality, Create Knowledge, Defer Commitment, Deliver Fast, Respect People, Optimise the Whole — form the philosophical backbone of both Kanban and SAFe.
Lean thinking asks practitioners to identify and eliminate the eight wastes in software delivery: partially done work, extra processes, extra features, task switching, waiting, motion, defects, and under-utilised talent.
Which Should You Know?
As a Scrum Master, understanding XP helps you coach engineering teams on quality practices beyond ceremonies. Understanding Lean helps you identify systemic flow problems that sprint retrospectives alone cannot fix. CREA-SM covers all three frameworks and specifically tests how an enterprise SM applies insights from XP and Lean in Scrum team contexts.