Logo
Delivery · Product

Agile vs Waterfall vs Scrum vs Kanban: Picking a Delivery Method

24/11/2026 · By · Founder, OG Technologies EU
Agile vs waterfall vs Scrum vs Kanban comparison

“Agile vs waterfall” is one of the most searched questions in software delivery — and one of the most confused, because it compares a philosophy with a process model and throws two frameworks into the same bucket. Untangle the terms first, then the choice gets much easier.

The Terms Are Not Equivalent

  • Agile is a set of values — the 2001 Manifesto — not a process. It says: iterate, welcome change, measure by working software.
  • Scrum is an agile framework: fixed sprints, defined roles, ceremonies that protect the iteration.
  • Kanban is an agile method: visualize flow, limit work in progress, pull continuously — no sprints required.
  • Waterfall is a sequential model: requirements → design → build → test → deploy, each phase gated on the last.

So the real question is never “agile or Scrum” — Scrum is agile. It is “iterative or sequential,” and then “which iterative framework.”

Agile vs Waterfall: The Actual Trade-Off

Iterative delivery wins when requirements are discovered by shipping — new products, evolving integrations, markets that move during the build. Every cycle is a chance to correct course before the wrong thing hardens. The cost is governance: scope flexes, so contracts, budgets, and compliance sign-offs need a different shape.

Sequential delivery wins when requirements are genuinely stable and change is expensive — fixed-price tenders with signed-off specs, regulated deliverables where documentation gates are legal requirements, hardware-coupled systems where a mid-flight change costs real money. Waterfall's failure mode is not the model — it is pretending requirements are stable when they are not.

Scrum vs Kanban: Choosing Inside Agile

Scrum fits product work with a real backlog: a cross-functional team, a Product Owner ranking priorities, two-week sprints producing shippable increments. The cadence forces planning, review, and retrospective — the forcing functions teams otherwise skip.

Kanban fits flow work: support tickets, ops, maintenance, anything interrupt-driven where batching work into sprints is artificial. The board and WIP limits expose bottlenecks instantly — work cannot pile up silently. Many teams run both: Scrum for the product roadmap, Kanban for the support stream feeding it.

Why Most Regulated Teams End Up Hybrid

In compliance-heavy environments — payments, healthcare, public sector — the dominant real-world pattern is waterfall governance around agile build: fixed scope, milestones, and documentation gates at the contract and audit level; iterative sprints inside the engineering team. It is honest about both constraints — regulators want gate evidence, users want software that learns. The mistake is adopting a label instead of answering the underlying questions: how stable are requirements, how expensive is change, and how do we prove progress?

A Selection Checklist

  • Requirements will evolve during the build → iterative (Scrum or Kanban).
  • Scope must be contractually fixed upfront → sequential or hybrid.
  • Work arrives unpredictably, flow-based → Kanban.
  • Team ships a product iteratively with a prioritized backlog → Scrum.
  • External audit/compliance gates exist → hybrid: agile inside, stage gates outside.
  • Still shaping the idea → de-risk first with a PoC, prototype, or MVP before picking a delivery frame.

Frequently Asked Questions

Is Scrum the same as agile?

No — Scrum is one framework implementing agile values: sprints, roles, ceremonies. Agile is the broader philosophy from the 2001 Manifesto; Kanban, XP, and Lean are other agile approaches. All Scrum is agile; not all agile is Scrum.

What is the main difference between Scrum and Kanban?

Cadence vs flow. Scrum batches work into fixed sprints with roles and ceremonies; Kanban pulls work continuously with WIP limits and no required iterations. Scrum suits planned product backlogs; Kanban suits unpredictable inflow like support and ops.

Is waterfall ever the right choice?

Yes — when requirements are truly stable, change is expensive, or stage-gate sign-offs are mandated (tenders, regulated deliverables, hardware-coupled builds). The failure mode is applying it to discovery work where requirements are not actually known.

What is a hybrid agile-waterfall approach?

Waterfall-shaped governance around agile-shaped build: fixed scope and stage gates at the contract and compliance level, iterative sprints inside the team. It is the dominant pattern in regulated delivery — and works only when both layers are honest about what they control.

Share:

Related Insights

Privacy & Cookie Preferences

We use cookies to enhance your experience, analyze site performance, and support our marketing efforts. Your privacy matters, and you can withdraw consent at any time.