The Agile Family Map

Sooner or later, someone at work will say "we use XP practices," or "we're scaling with SAFe," and glance at you to see if you flinch. This lesson exists so you don't flinch. Six minutes, one map, no depth — just enough to place every name you'll hear in its family tree.

By the end of this video, you'll be able to place the major agile-family methods on one map and say, in a sentence each, what they contributed. That's the whole goal: recognition, not mastery.

Remember Snowbird: seventeen people from competing lightweight methods. The Manifesto was the common ground — but the methods themselves kept living. Four stops on the map.

Stop one: Extreme Programming — XP — associated most with Kent Beck. The name means exactly what it says: take proven good practices and turn them up to the extreme. Code reviews are good? Do them continuously — two people at one keyboard, called pair programming. Testing is good? Write the test before the code — test-driven development. XP is the family's craft branch: the deep home of the principle about technical excellence. You met that principle in cluster four; XP is where it lives with the intensity dial at maximum. If you're not in software, keep the transferable idea: quality practiced continuously beats quality inspected at the end.

Stop two, and the oldest: Lean. This branch predates agile by half a century, born on Toyota's factory floors through engineers like Taiichi Ohno. Lean's gifts to the family: relentlessly remove waste; build quality in rather than inspecting it in afterward; and let real demand pull work through the system instead of pushing work onto people. If those words ring a bell — pull, flow, visual boards — it's because Kanban, which you'll properly meet in Module 2, is Lean's most direct descendant. Lean is the grandparent whose furniture the whole family still uses.

Stop three, briefly: the siblings history mostly filed away. Crystal — Alistair Cockburn's family of methods sized to the team, with the lovely insight that process weight should match project weight. DSDM, one of the earliest full frameworks, strong on business involvement and timeboxing. FDD, feature-driven development, organizing everything around a list of client-valued features. You'll rarely run these today, but their DNA — right-sized process, business collaboration, feature-first thinking — is everywhere in what you're learning.

Stop four: scaling frameworks. Everything in this course so far assumes roughly one team. But what happens when fifty teams must move together on one product? A category of frameworks exists for that coordination problem — the most widely known is SAFe, the Scaled Agile Framework, and you may also hear of LeSS or Scrum@Scale. This course names them without teaching or endorsing them, for two honest reasons. First, they're advanced tooling for a problem beginners don't have yet. Second — remember Module 4 will make this vivid — heavyweight scaling is exactly where critics say agile's original spirit most often gets lost. Know the names; defer the judgment until you can make it yourself.

You might think these are competing religions and you'll eventually have to pick one. That's understandable — the branding wars are loud. Actually, they're a toolshed with a shared foundation: the values and principles you've already learned. Teams routinely blend them. The foundation is the education; the frameworks are fittings.

Three things to keep. One: XP is the craft branch — technical excellence at maximum intensity. Two: Lean is the grandparent — waste out, quality in, pull not push — and Kanban is its most direct descendant. Three: scaling frameworks like SAFe exist for many-team coordination; know the names, and judge later with your own eyes.

Map in hand, back to the main road: the two family members you'll actually use week to week — Scrum and Kanban — are waiting in Module 2.