Methodology Is the Top Layer

Software delivery practices form a stack with three layers, and most teams try to adopt them in the wrong order.

Layer 1: Fundamentals. Source control, work tracking, intent communication, estimation habits, and traceability. These are the practices this course covers. They're methodology-agnostic — a Scrum team and a Kanban team both need them, and they look almost identical in both contexts.

Layer 2: Methodology. Scrum, Kanban, XP, or a hybrid. This is where you choose a cadence (sprints or continuous flow), define roles (or explicitly choose not to), and adopt ceremonies (standups, retrospectives, planning sessions). Methodology gives a team rhythm and structure — but it assumes the fundamentals are already in place.

Layer 3: Scaling. SAFe, LeSS, Lean Portfolio Management, or homegrown coordination patterns. This layer only matters when multiple teams need to coordinate delivery. It assumes both fundamentals and methodology are working at the team level.

The stack matters because each layer depends on the one below it. A team running Scrum without solid work tracking will spend half of every sprint planning meeting re-discovering what's in flight. An organization adopting SAFe without functioning team-level retrospectives will scale dysfunction, not delivery.

Most "agile transformations" fail because they start at Layer 2 or Layer 3. They buy a tool, hire a coach, rename meetings — and then wonder why velocity doesn't improve. The answer is almost always the same: the fundamentals weren't there.

Every methodology assumes you already have the basics. Scrum assumes you can track work in a backlog, commit code to a shared repository, and estimate effort with enough consistency to plan a sprint. Kanban assumes you can visualize work items, measure cycle time, and trace a ticket from request to delivery. XP assumes you can write tests, review code, and deploy frequently.

None of these assumptions are stated in the methodology guides, because the authors considered them obvious. But for many teams, they're not obvious — they're aspirational. And when a team adopts a methodology without the fundamentals, the methodology becomes theater: the ceremonies happen, the artifacts exist, but the outcomes don't change.

You've seen this. The team that runs sprint planning but can't answer "what did we commit to last sprint?" because the tickets weren't updated. The team that does daily standups but can't share progress because half the work isn't tracked. The team that holds retrospectives but can't act on the insights because there's no system to assign and follow up on action items.

The fix isn't to abandon methodology. The fix is to get the fundamentals right first, then layer methodology on top. That's the order this course follows: Modules 2–4 cover the fundamentals (source control, tickets, estimation), and Module 5 helps you choose which methodology — if any — to adopt once the foundation is solid.