Agile, Scrum, Kanban, Lean, and Waterfall are not interchangeable project management methodologies. Waterfall is a linear sequential approach best for fixed-scope projects. Agile is a philosophy of iterative delivery best for changing requirements. Scrum is a specific Agile framework using sprints. Kanban is a visual workflow system for continuous delivery. Lean is a waste-elimination philosophy originating in manufacturing. Understanding the relationship between these five, which is a philosophy, which is a framework, which is a tool – is the foundation of modern project management certification and practice.
The fastest way to understand all five: Agile and Lean are philosophies. Waterfall is a methodology. Scrum and Kanban are frameworks that implement those philosophies in practice.
The Relationship Between All Five: The Map You Need First
Before comparing them, understand how they relate to each other. Most candidates and practitioners confuse Agile with Scrum or treat Lean and Kanban as separate systems when Kanban originally came from Lean.
PHILOSOPHIES METHODOLOGY FRAMEWORKS
Agile ────────────────────────────► Scrum
\ â–º Kanban
\ â–º XP (Extreme Programming)
\ â–º SAFe, LeSS (scaled frameworks)
Lean ─────────────────────────────► Kanban (originated here)
â–º Six Sigma (combined: Lean Six Sigma)
Waterfall ────────────────────────── Sequential phases methodology
Agile approach is just a way of thinking that enables teams and organizations to innovate, quickly respond to changing demand, while mitigating risk. Organizations can be agile using many available frameworks such as Scrum, Kanban, Lean, XP and others.
What Is Waterfall?
Waterfall is the original structured project management methodology. Waterfall is a linear approach to software development where each phase represents a distinct stage in the process, typically completed before the next begins.
Waterfall Phases
| Phase | What Happens | Who Is Responsible |
| Requirements | All project requirements documented upfront | Business analysts, stakeholders |
| System design | Architecture and technical design completed | Solution architects |
| Implementation | Development and coding begins | Developers |
| Testing | Full system tested after development complete | QA team |
| Deployment | Product released to production | DevOps, release team |
| Maintenance | Ongoing support and bug fixes | Support team |
The defining rule of Waterfall: Each phase must be fully completed and verified before the next begins. You cannot go back. If a flaw is discovered during testing that originated in the requirements phase, addressing it requires revisiting everything in between — which is expensive and time-consuming.
Waterfall Strengths and Weaknesses
| Strengths | Weaknesses |
| Clear structure and documentation | No flexibility once a phase is complete |
| Fixed cost and timeline predictability | Errors discovered late are expensive to fix |
| Easy to manage and report progress | Customer sees working product only at the end |
| Works well with fixed requirements | Assumes requirements can be defined perfectly upfront |
| Regulatory and compliance-friendly | Fails when requirements change mid-project |
When to Use Waterfall
Use Waterfall when requirements are fully defined and unlikely to change, the project has strict regulatory documentation requirements, you are building physical infrastructure or hardware, your contract specifies fixed scope and fixed price, or your team is distributed across locations with limited communication bandwidth.
Construction projects, government contracts, hardware manufacturing, and regulated healthcare or financial software with rigid compliance requirements are all environments where Waterfall remains the dominant approach.
What Is Agile?
The linear waterfall methodology requires completing distinct, sequential phases and is best for projects with fixed requirements. Agile methodology focuses on iterative workflows that allow teams to adapt to changing requirements and constraints.
Agile is not a methodology — it is a philosophy articulated in the Agile Manifesto, written by 17 software developers in 2001. The Agile Manifesto states four core values:
| Agile Values | Over |
| Individuals and interactions | Processes and tools |
| Working software | Comprehensive documentation |
| Customer collaboration | Contract negotiation |
| Responding to change | Following a plan |
These values do not mean processes, documentation, contracts, and plans have no value. They mean the items on the left are valued more. This distinction matters for certification exams — PMI-ACP, CSM, and PMP all test whether candidates understand Agile as a values-based philosophy rather than a specific set of practices.
The 12 Agile Principles (Simplified)
| Principle Category | Core Idea |
| Customer satisfaction | Deliver valuable software early and continuously |
| Welcome change | Changing requirements, even late, are a competitive advantage |
| Frequent delivery | Working software every 2 weeks to 2 months |
| Business and development collaboration | Daily collaboration throughout the project |
| Motivated individuals | Give teams the environment and trust they need |
| Face-to-face communication | Most efficient and effective method |
| Working software as progress | Primary measure of progress |
| Sustainable development | Sponsors, developers, users maintain constant pace indefinitely |
| Technical excellence | Continuous attention to good design enhances agility |
| Simplicity | Maximizing work not done is essential |
| Self-organizing teams | Best architectures and designs emerge from self-organizing teams |
| Regular reflection | Team reflects and adjusts at regular intervals |
When to Use Agile
Use Agile when requirements are expected to change, you need to deliver value incrementally and get early customer feedback, the project involves innovation or uncertainty, you have a stable team working in close collaboration, or you are building digital products where market feedback shapes direction.
Software products, mobile applications, e-commerce platforms, and any digital initiative where customer feedback drives ongoing development are the natural home of Agile.
What Is Scrum?
Scrum is an Agile way to manage a project, usually software development. Rather than viewing Scrum as a methodology, think of it as a framework for managing a process.
Scrum implements Agile values through a specific structure of roles, events, and artifacts. It is the most widely adopted Agile framework in software development globally.
The Three Scrum Roles
| Role | Responsibilities |
| Product Owner | Manages the Product Backlog, defines priorities, represents stakeholders, accepts or rejects completed work |
| Scrum Master | Facilitates Scrum events, removes impediments, coaches the team on Scrum practices, not a project manager |
| Development Team | Self-organizing, cross-functional, typically 3 to 9 people, collectively responsible for delivering the Sprint Goal |
The Five Scrum Events
| Event | Duration | Purpose |
| Sprint | 1 to 4 weeks (fixed) | Time-boxed development cycle — the heartbeat of Scrum |
| Sprint Planning | 8 hours max (for 4-week Sprint) | Team selects items from Product Backlog and plans how to complete them |
| Daily Scrum | 15 minutes | Daily inspection of progress toward Sprint Goal — not a status meeting |
| Sprint Review | 4 hours max (for 4-week Sprint) | Inspect the Increment and adapt the Product Backlog based on stakeholder feedback |
| Sprint Retrospective | 3 hours max (for 4-week Sprint) | Inspect and improve the team’s processes and ways of working |
The Three Scrum Artifacts
| Artifact | What It Is | Commitment |
| Product Backlog | Ordered list of everything the product needs | Product Goal |
| Sprint Backlog | Items selected for the Sprint plus the plan to deliver them | Sprint Goal |
| Increment | Sum of all completed Product Backlog items in the current and all previous Sprints | Definition of Done |
Scrum Strengths and Weaknesses
| Strengths | Weaknesses |
| Regular delivery of working software (each Sprint) | Requires fully dedicated team — not suitable for part-time team members |
| Built-in retrospective improves team continuously | Scope changes within a Sprint cause disruption |
| Clear roles reduce confusion | Daily Scrums and ceremonies can feel overhead-heavy for small teams |
| High visibility into progress | Works best when the team is co-located or in the same timezone |
| Customer feedback integrated every Sprint | Difficult to scale without additional frameworks like SAFe or LeSS |
Scrum Certifications
The most recognized Scrum certifications are:
- CSM (Certified Scrum Master) from Scrum Alliance — $495 to $1,495 including training
- PSM I (Professional Scrum Master) from Scrum.org — $200 exam only
- PSPO (Professional Scrum Product Owner) from Scrum.org — $200 exam only
- PMI-ACP (PMI Agile Certified Practitioner) from PMI — covers Scrum plus other Agile frameworks
What Is Kanban?
Kanban is Japanese for “visual signal” or “card.” Toyota line-workers used a Kanban to signal steps in their manufacturing process. As a part of Lean, the system’s highly visual nature allowed teams to communicate more easily on what work needed to be done and when.
Kanban is a visual workflow management method that helps teams visualize work, limit work in progress, and maximize efficiency. Unlike Scrum, Kanban has no sprints, no fixed roles, and no prescribed meetings. Work flows continuously based on capacity.
The Six Core Kanban Practices
| Practice | What It Means |
| Visualize the workflow | Map every step work goes through on a Kanban board with columns |
| Limit Work in Progress (WIP) | Set maximum number of items allowed in each stage simultaneously |
| Manage flow | Monitor and optimize how work moves through the system |
| Make policies explicit | Define and display the rules for how work is processed |
| Implement feedback loops | Regular cadences for reviewing flow and improving the system |
| Improve collaboratively | Use scientific thinking to make incremental, evolutionary improvements |
Kanban Board Structure
| Column | What It Contains |
| Backlog | All identified work items not yet started |
| To Do | Work selected and ready to begin |
| In Progress | Work actively being worked on (WIP limited) |
| Review | Work completed and awaiting review or approval |
| Done | Fully completed work items |
The WIP limit is what makes Kanban powerful. Setting a maximum number of items allowed in each column forces the team to finish work before starting new work. This prevents the common failure mode where a team starts many things but finishes nothing. When a column reaches its WIP limit, no new items can enter that column until one exits.
Kanban vs Scrum: The Key Differences
| Factor | Scrum | Kanban |
| Iteration structure | Fixed-length Sprints | Continuous flow — no Sprints |
| Roles | Product Owner, Scrum Master, Dev Team | No prescribed roles |
| WIP limits | At Sprint level | At workflow stage level |
| Change policy | Changes wait until next Sprint | Changes can enter the backlog at any time |
| Metrics | Velocity (story points per Sprint) | Lead time, cycle time, throughput |
| Best for | Projects with batched deliverables | Support queues, continuous maintenance, ongoing operations |
| Cadence | Sprint rhythm drives ceremonies | Pull-based — work pulled when capacity available |
Kanban readily adapts to new tasks as they arise while Waterfall makes changes difficult after the initial phases. Kanban is well-suited for evolving scopes while Waterfall works best with a fixed scope.
What Is Lean?
The goal of Lean is to maximize value while minimizing waste in a process or system. It is a management approach that was initially developed in manufacturing but has since been applied to a wide range of industries including software development.
Lean originated with Toyota’s production system in post-World War II Japan. Taiichi Ohno developed the Toyota Production System around two pillars: just-in-time manufacturing and jidoka (automation with a human touch). These principles were later codified as Lean by Western researchers studying Toyota’s methods.
The 8 Wastes of Lean (TIMWOODS)
| Waste | Description | Software Development Example |
| Transport | Moving products or information unnecessarily | Passing work between teams that could be handled by one |
| Inventory | Excess work items waiting to be processed | Backlog of features nobody has prioritized |
| Motion | Unnecessary movement of people | Developers context-switching between unrelated tasks |
| Waiting | Idle time between process steps | Code written but waiting weeks for code review |
| Over-processing | More work than the customer requires | Building features nobody asked for |
| Overproduction | Producing more than needed | Writing extensive documentation nobody reads |
| Defects | Errors requiring rework | Bugs that escape testing and need emergency fixing in production |
| Skills | Underutilizing people’s capabilities | Senior engineers doing manual testing that tools could automate |
Lean Principles
| Principle | What It Means |
| Define value | Identify what the customer actually values |
| Map the value stream | Document every step that creates or does not create value |
| Create flow | Ensure value-creating steps flow without interruption |
| Establish pull | Produce only what is needed when it is needed |
| Pursue perfection | Continuously improve the system toward zero waste |
Lean vs Agile
Lean and Agile are not the same. Lean focuses on the fact that we should minimize waste, whereas Agile’s primary focus is to develop incrementally. Scrum is an improvement of the Agile Method. Kanban is considered a way of Lean.
The Complete Comparison: All Five Side by Side
| Factor | Waterfall | Agile | Scrum | Kanban | Lean |
| Type | Methodology | Philosophy | Framework | Framework | Philosophy |
| Delivery | Single delivery at end | Incremental and iterative | Each Sprint delivers | Continuous flow | Continuous improvement |
| Requirements | Fixed upfront | Evolve throughout | Refined each Sprint | Pulled as capacity allows | Driven by customer value |
| Change response | Resistant | Embraces change | Accommodates per Sprint | Accommodates anytime | Eliminates waste from change |
| Team structure | Functional siloes | Cross-functional preferred | Prescribed roles | No prescribed roles | Cross-functional |
| Best for | Fixed scope regulated projects | Digital products with changing needs | Software development teams | Operations, support, maintenance | Manufacturing, process improvement |
| Planning horizon | Full project upfront | Rolling — each iteration | Sprint by Sprint | Continuous backlog prioritization | Continuous |
| Progress measurement | Phase completion | Working software | Sprint velocity | Lead time and cycle time | Waste reduction metrics |
| Customer involvement | Primarily at start and end | Continuous | Sprint Reviews | Ongoing | Defined by value stream |
| Risk management | All risk identified upfront | Risk reduced by early delivery | Risk addressed each Sprint | Continuous risk visibility | Risk reduced by eliminating waste |
Which Methodology Should You Choose? The Decision Framework
| Your Situation | Best Choice | Why |
| Fixed scope, fixed budget, regulatory compliance required | Waterfall | Predictability and documentation requirements align |
| Changing requirements, digital product, ongoing customer feedback | Agile (choose a framework) | Flexibility and iterative delivery match the need |
| Software team needing structured Agile with regular release cadence | Scrum | Sprint structure creates rhythm and accountability |
| Operations, support team, or maintenance work with continuous incoming requests | Kanban | Continuous flow and WIP limits match the work type |
| Manufacturing, process improvement, or eliminating operational inefficiency | Lean | Waste elimination principles are purpose-built for this |
| Team transitioning from Waterfall to Agile | Kanban first, then Scrum | Kanban is less disruptive to adopt incrementally |
| Large enterprise needing scaled Agile across multiple teams | SAFe or LeSS | Scrum and Agile frameworks designed for enterprise scale |
| Project with some fixed requirements and some changing requirements | Hybrid Agile/Waterfall | 57% of businesses have now taken a hybrid approach to project delivery |
Agile, Scrum, Kanban, Lean, and Waterfall in Project Management Certifications
This is the angle every competitor misses — and the most valuable section for CertEmpire’s audience of certification candidates.
Understanding these methodologies is not just theoretical knowledge. It is tested content in the most sought-after project management certifications.
| Certification | Issuing Body | Methodologies Tested | Relevance |
| PMP (Project Management Professional) | PMI | All five — approximately 50% Agile, 50% Waterfall and hybrid | The most widely recognized project management credential globally |
| PMI-ACP (Agile Certified Practitioner) | PMI | Agile, Scrum, Kanban, Lean, XP | Specifically validates Agile knowledge across multiple frameworks |
| CSM (Certified ScrumMaster) | Scrum Alliance | Scrum specifically | Entry-level Scrum practitioner certification |
| PSM I (Professional Scrum Master) | Scrum.org | Scrum specifically | More rigorous alternative to CSM |
| PRINCE2 Agile | Axelos | Agile, Scrum, Kanban in PRINCE2 context | Popular in UK, Australia, and Europe |
| SAFe Agilist | Scaled Agile | Agile, Scrum, Kanban at enterprise scale | Enterprise Agile transformation roles |
The PMP certification now tests both Agile and Waterfall equally. PMI updated the PMP exam in 2021 to reflect how project management is actually practiced — approximately 50 percent of PMP exam questions now cover Agile, Scrum, Kanban, and hybrid approaches. Candidates who prepare only for traditional Waterfall-based project management consistently underperform on the current PMP exam. Our Agile vs Scrum certification guide covers the specific Scrum knowledge tested in certification exams in detail.
Common Misconceptions About These Methodologies
Misconception 1: Scrum and Agile Are the Same Thing
Agile is the philosophy. Scrum is one of many frameworks that implement Agile values. You can be Agile without using Scrum. You can misuse Scrum in a way that is not Agile at all. The Scrum Guide explicitly states that Scrum is founded on empiricism and Lean thinking — meaning Scrum draws from both Agile and Lean philosophical roots.
Misconception 2: Waterfall Is Dead
The biggest advantage of the Waterfall approach is fixed cost and predictability. For projects with genuine fixed requirements — construction, hardware, regulated healthcare systems, government contracts — Waterfall remains the most appropriate methodology. The question is not Agile versus Waterfall ideologically. It is which approach fits the actual nature of your specific project.
Misconception 3: Kanban Is Just a Board
Kanban is a complete workflow management system with explicit policies, WIP limits, feedback loops, and continuous improvement cycles. Using a sticky-note board to track tasks is not Kanban. Kanban requires deliberately limiting work in progress, measuring flow metrics, and making policies explicit.
Misconception 4: Lean Is Only for Manufacturing
Lean is a management approach that was initially developed in manufacturing but has since been applied to a wide range of industries including software development. Lean principles now underpin DevOps practices, software delivery optimization, and organizational transformation programs across every industry.
Misconception 5: You Must Choose One
57% of businesses have now taken a hybrid approach to project delivery. Most mature organizations use multiple methodologies simultaneously — Waterfall for compliance-heavy infrastructure projects, Scrum for product development teams, Kanban for IT support and operations, and Lean principles throughout for continuous improvement.
Agile vs Scrum vs Kanban vs Lean vs Waterfall: Quick Reference Card
| Question | Answer |
| Which is a philosophy, not a framework? | Agile and Lean |
| Which is a methodology, not a framework? | Waterfall |
| Which are frameworks? | Scrum and Kanban |
| Which has Sprints? | Scrum only |
| Which has WIP limits? | Kanban (by design) and Scrum (implicitly) |
| Which originated in manufacturing? | Lean and Kanban |
| Which has the most prescribed roles? | Scrum |
| Which is most flexible to change? | Kanban |
| Which gives the most predictable cost and timeline? | Waterfall |
| Which delivers value most frequently? | Kanban (continuous) or Scrum (every Sprint) |
| Which is best for maintenance and support work? | Kanban |
| Which is best for regulated projects? | Waterfall |
| Which certifications cover all five? | PMP and PMI-ACP |
You can also check more detail here: https://www.visual-paradigm.com/scrum/scrum-vs-waterfall-vs-agile-vs-lean-vs-kanban/
FAQS
What is the difference between Agile and Scrum?
Agile is a philosophy articulated in the 2001 Agile Manifesto — a set of values and principles for iterative, customer-focused delivery. Scrum is a specific framework that implements Agile values through defined roles, events, and artifacts. All Scrum teams are Agile but not all Agile teams use Scrum.
Is Kanban part of Agile or Lean?
Kanban originated in Lean — specifically from Toyota’s manufacturing system. It was later adopted by software teams as an Agile framework. In current practice, Kanban is considered both a Lean tool and an Agile framework depending on the context. Most Agile practitioners consider Kanban an Agile method while Lean practitioners see it as an implementation of Lean principles.
When should you use Waterfall instead of Agile?
Use Waterfall when requirements are fully defined and fixed, the project has regulatory or contractual requirements demanding complete upfront specification, changes are prohibitively expensive once development begins, or you are working on physical infrastructure or hardware where iterative delivery is not practical.
What is the difference between Scrum and Kanban?
Scrum uses fixed-length Sprints to batch work into iterative delivery cycles with prescribed roles and ceremonies. Kanban uses continuous flow with explicit WIP limits and no prescribed roles or iterations. Scrum is better for product development teams delivering batches of features. Kanban is better for operations, support, and maintenance teams handling continuous incoming work.
Is Lean the same as Agile?
No. Lean focuses on eliminating waste and maximizing value delivery through process efficiency — originating in Toyota’s manufacturing system. Agile focuses on iterative development and responding to change — originating in software development. Both philosophies share values around continuous improvement and customer focus but have different origins, principles, and practices.
Which project management methodology is best in 2026?
No single methodology is universally best. Waterfall is best for fixed-scope regulated projects. Scrum is best for software product development with regular releases. Kanban is best for continuous flow work like support and operations. Lean is best for waste elimination in any process. Most organizations use hybrid approaches combining elements of multiple methodologies to fit their specific context.
What is the difference between Scrum Master and Agile Coach?
A Scrum Master facilitates Scrum practices within a single team — running Sprint ceremonies, removing impediments, and coaching the team on Scrum. An Agile Coach works at an organizational level — transforming culture, coaching multiple teams, and guiding leadership on Agile adoption across the enterprise.
Which methodology does the PMP exam cover?
The current PMP exam covers both traditional Waterfall project management and Agile approaches including Scrum, Kanban, and hybrid methods. Approximately 50 percent of PMP questions now cover Agile and hybrid content. Candidates who prepare only for Waterfall-based project management consistently underperform on the current PMP exam.
Can you use Scrum and Kanban together?
Yes. Scrumban is a hybrid approach that combines Scrum’s Sprint structure with Kanban’s visual board and WIP limits. Teams commonly use a Kanban board to visualize work within Scrum Sprints while applying WIP limits to prevent overloading team members. This hybrid is particularly useful for teams transitioning from Scrum to a more flow-based approach or managing both planned Sprint work and unplanned support requests simultaneously.
What is SAFe and how does it relate to Scrum and Agile?
SAFe (Scaled Agile Framework) is an enterprise-scale Agile framework that coordinates multiple Agile teams working toward shared goals. It builds on Scrum, Kanban, and Lean to provide structure for large organizations delivering complex products. SAFe is one solution to the challenge of scaling Scrum beyond a single team.
