Project Management 101 · Lesson 4

Lesson 4 of 97 minFree, no sign-upExercise + 5-question check

Agile vs Waterfall: the Real Differences, Played Out on One Project

By the end of this lesson you'll be able to:

  • Explain the five real differences between agile and waterfall: planning, change, delivery, risk and customer involvement
  • Weigh the strengths and weaknesses of each for a given project
  • Describe a hybrid approach and when it is the better choice

Quick answer: agile vs waterfall: what is the difference?

Agile vs waterfall comes down to when you plan and how you handle change. Waterfall finishes each stage in order and delivers once at the end, so late changes mean rework. Agile delivers working pieces in short cycles and re-plans after each one. In Kanbanchi's Project Management 101 course, you run one project both ways.

Agile vs waterfall in 8 slides

One idea per slide. Use the buttons, the dots or your arrow keys. The full text, with a comparison table, is right below the player.

Lesson 4 slides

8 slides

  1. Slide 1 of 8

    Agile vs waterfall in one picture

    Waterfall is a sequential approach: the team finishes each stage (requirements, design, build, test, release) before starting the next, with scope agreed up front and one delivery at the end.

    Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto.

    Read this part in full
    When does the customer see something that works?Week 1Week 2Week 3Week 4Week 5Week 6WaterfallAgiledark = working version delivered
  2. Slide 2 of 8

    Difference 1: planning

    Waterfall plans the whole project up front and treats the plan as the baseline. Agile plans the next cycle in detail and keeps the rest as a prioritized backlog that is re-planned after every cycle.

    Read this part in full
    RequirementsDesignBuildTestReleaseWaterfall: one pass, each stage finished before the next starts, one delivery at the end
  3. Slide 3 of 8

    Difference 2: change

    In waterfall, a change after sign-off becomes a formal change request, and finished stages may have to be reopened. In agile, change is expected: it goes into the backlog and the next cycle is adjusted.

    Read this part in full
  4. Slide 4 of 8

    Difference 3: delivery

    Waterfall delivers once, at the end, after testing. Agile delivers a working piece at the end of every cycle, so customers can use part of the product early.

    Read this part in full
    Cycle 1plan, build,reviewreleaseCycle 2plan, build,reviewreleaseCycle 3plan, build,reviewreleaseCycle 4plan, build,reviewreleaseAgile: short cycles, each one ends with something working and feedback that shapes the next
  5. Slide 5 of 8

    Difference 4: risk

    In waterfall, the whole system is tested late, so problems tend to surface together near the deadline. Agile tests and reviews every cycle, so problems surface early, while they are still small.

    Read this part in full
  6. Slide 6 of 8

    Difference 5: customer involvement

    Waterfall involves the customer mainly at the start, to agree requirements, and at the end, to accept the result. Agile needs the customer in regular reviews throughout the project.

    Read this part in full
  7. Slide 7 of 8

    Strengths and weaknesses

    • Waterfall: predictable scope, cost and date up front; but late feedback and costly change.
    • Agile: early value, easy change and early risk discovery; but the final scope and date are less fixed at the start, and it needs an involved customer.
    Read this part in full
  8. Slide 8 of 8

    Hybrid: the honest answer for many projects

    A hybrid approach combines methods: it typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style.

    Use the exercise below to see the trade-off on one project.

    Read this part in full

The full lesson: agile vs waterfall, difference by difference

Agile vs waterfall: the short version

Waterfall is a sequential approach: the team finishes each stage (requirements, design, build, test, release) before starting the next, with scope agreed up front and one delivery at the end. Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto.

Both still move through the five phases of the project life cycle. Waterfall runs planning and execution once, in order. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once. The real differences show up in five places: planning, change, delivery, risk and customer involvement.

Agile vs waterfall: the real differences
AspectWaterfallAgile
PlanningThe whole project up front; the plan becomes the baselineThe next cycle in detail; the rest stays in a prioritized backlog
ChangeA formal change request; finished stages may be reopenedExpected; added to the backlog and handled in the next cycle
DeliveryOnce, at the end, after testingA working piece at the end of every cycle
RiskFound late, when the whole system is testedFound early, in every cycle's testing and review
Customer involvementMainly at the start and at the endRegular reviews throughout
Best forClear, stable requirements; fixed contracts; regulated or physical workUncertain or changing requirements; products that users can try early

Planning: up front or rolling

A waterfall team writes and signs off the requirements, then designs everything, then builds and tests. The approved plan is the baseline, and progress is measured against it. An agile team plans the next cycle in detail and keeps everything else in a prioritized list, the backlog, which is re-ordered after every cycle as the team learns.

Change: a request or the normal flow

In waterfall, a change after sign-off goes through a change request: someone assesses its impact on scope, time and cost, and if it is approved, finished stages may have to be reopened. That is controlled, but expensive late in the project. In agile, change is expected. It goes into the backlog, and the next cycle is re-planned around it. In scrum, the change usually waits for the next sprint planning rather than breaking into the current sprint.

Delivery: once or every cycle

Waterfall delivers once, at the end, after the full system has been tested. Agile delivers a working piece at the end of every cycle, so customers can use part of the product, and react to it, long before the end.

When does the customer see something that works?Week 1Week 2Week 3Week 4Week 5Week 6WaterfallAgiledark = working version delivered

Risk: found late or found early

Because waterfall tests the whole system late, problems tend to surface together, close to the deadline, when there is the least time to fix them. Agile tests and reviews in every cycle, so integration problems and wrong assumptions surface early, while they are still small. The HealthCare.gov case study below shows what a late, all-at-once discovery looks like.

Customer involvement: sign-offs or regular reviews

Waterfall needs the customer mainly at the start, to agree the requirements, and at the end, to accept the result. Agile needs the customer, or a product owner speaking for them, in regular reviews throughout. If nobody on the client side has time for that, agile loses much of its advantage.

Strengths and weaknesses of each

  • Waterfall strengths: scope, cost and date are known early; documentation is thorough; it suits fixed-price contracts, regulated work and physical projects where changing course late is impossible anyway.
  • Waterfall weaknesses: customers see working results only at the end; change is costly; problems surface late.
  • Agile strengths: value arrives early; change is cheap to absorb; risks surface early; the product follows what users actually need.
  • Agile weaknesses: the final scope and date are less fixed at the start; it needs an involved customer and a team that can work in short cycles; it can be harder to fit into fixed contracts.

Hybrid approaches

A hybrid approach combines methods: it typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style. For example, a company opening a new store might plan the lease, fit-out and opening date in waterfall style, while the team building the store's app works in two-week sprints inside that plan. Lesson 3 covers the other methods, from scrum and kanban to PRINCE2 and the critical path method.

Case study: HealthCare.gov, a big-bang launch

HealthCare.gov, the US federal health insurance marketplace, launched on its scheduled date in 2013 and failed in public on day one. It is a clear example of a big-bang launch, where everything goes live at once and the problems surface at once. All facts below come from Kanbanchi's Great Projects page on HealthCare.gov.

Great Projects case study

HealthCare.gov launch, 2011 to 2013

Software and IT · United States

$93.7 millionEstimated contract value for the core system, Dec 2011
More than $209 millionObligated for the core system by Feb 2014
250,000People trying to use the site at once, against 50,000 to 60,000 expected
About 2 monthsTo restore the site for high use

Requirements were not known when the work began

GAO found that the Centers for Medicare & Medicaid Services (CMS) issued the order for the core system before key requirements were known, including how many states would rely on the federal marketplace and how many people might enroll. Requirements kept changing afterward.

Testing absorbed the slippage

The launch date of Oct 1, 2013 did not move, so the late work came out of readiness checks. The readiness assessment planned for March 2013 slipped to September 2013, weeks before launch.

Everything went live at once

Open enrollment began on the scheduled date, and users met outages and errors at once. Administration official Todd Park said 250,000 people tried to use the site at the same time, against 50,000 to 60,000 expected. Fewer than 27,000 people had enrolled through the federal site by Nov 13, 2013.

The recovery ran on one team and ruthless prioritization

A tech surge was announced on Oct 21, 2013. CMS and its contractors worked as one team and applied what the Inspector General called ruthless prioritization: the most important problems first. The site was restored for high consumer use within about two months.

What this shows about agile vs waterfall

  • A single big-bang release means the first real test of the whole system happens in front of every user at once.
  • When the date is fixed and the work runs late, testing is what gets squeezed. Short cycles with testing in each one protect it.
  • The fix looked like the agile idea applied in a rescue: one team, working on the highest-priority problems first.

Source: HealthCare.gov: planned vs actual, Kanbanchi Great Projects (data last updated Oct 25, 2026, with GAO and HHS Inspector General sources listed on that page).

Exercise: run the same project two ways

Play a 6-week project week by week under waterfall and agile at the same time. Halfway through, the client changes a key requirement. You decide how each team responds and see the time and cost side by side.

Worked example

Both teams start from the same plan: 6 weeks at $8,000 a week, $48,000 in total. Waterfall runs requirements, design, build and test in sequence; agile runs three 2-week sprints, each ending with a working version. The plan below is already filled in: press the button to play it week by week.

One project, two ways: a customer booking portal

The example project: a small agency builds an online booking portal for a client. The plan is 6 weeks for a 4-person team at $8,000 a week, so $48,000. Waterfall and agile start from the same plan. Press the button to play the project week by week.

Ready: week 0 of the plan

Waterfall

Week 0: the plan is a six-week sequence of stages with one delivery at the end.

Week 6 (plan)Finish
$0Spent so far
Not yetWorking version for the client

Agile

Week 0: the plan is three two-week sprints, each ending with working software.

Week 6 (plan)Finish
$0Spent so far
Not yetWorking version for the client

Legend: Req = requirements, Des = design, Build, Test = test and launch, Redo = rework, S1 to S4 = sprints. Each sprint ends with a review where the client sees working software.

The result, if you cannot run the simulation: with the change accepted, waterfall launches in week 8 at $64,000, two weeks late and $16,000 over, because requirements, design and the first build week are reopened. Agile launches in week 6 at $48,000 with the change included and admin reports moved to a later release, or in week 7 at $56,000 with everything.

A simplified teaching model: a 4-person team, $8,000 a week, a 6-week plan and one key change at the end of week 3. The numbers show the pattern; they are not data from a real project.

Knowledge check: Lesson 4

Five questions on this lesson. Get at least 4 right to complete Lesson 4 and move your course progress forward. Each answer comes with an explanation.

1. How does waterfall usually handle a change to the requirements after sign-off?
Show the answer

Answer: It handles it as a formal change request, and finished stages may have to be reopened. In waterfall, a change after sign-off goes through a change request. If it is approved, finished stages such as requirements or design may have to be reopened, which is why late change is costly.

2. When does a waterfall project typically deliver a working product to the customer?
Show the answer

Answer: Once, at the end, after the full system has been tested. Waterfall delivers once, at the end, after testing. Agile delivers a working piece at the end of every cycle.

3. Which project is the best fit for waterfall?
Show the answer

Answer: A bridge with a fixed, approved design and strict safety rules. Waterfall fits clear, stable requirements and work where changing course late is impossible, such as a bridge with a fixed, approved design.

4. What does a hybrid approach usually do?
Show the answer

Answer: Plans the fixed parts up front and builds the uncertain parts iteratively. A hybrid approach typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style.

5. According to Kanbanchi's Great Projects page, what happened to HealthCare.gov's readiness assessment?
Show the answer

Answer: It slipped from March 2013 to September 2013, weeks before launch. The readiness assessment planned for March 2013 slipped to September 2013, weeks before the Oct 1, 2013 launch, because the launch date did not move, so the late work came out of readiness checks.

Key takeaways

  • Waterfall plans everything up front and delivers once at the end; agile plans and delivers in short cycles and re-plans after each one.
  • Late change is expensive in waterfall because finished stages are reopened; in agile it goes into the next cycle.
  • Waterfall finds problems late, when the whole system is tested; agile finds them early, in every cycle.
  • Pick by how clear and stable the requirements are, and use a hybrid when a project has both fixed and uncertain parts.

Try it on a real board: run one sprint in Kanbanchi

The quickest way to feel the difference is to run one short cycle on a real board:

  1. Create a board with five lists: Backlog, This sprint, In progress, Review and Done.
  2. Add every task to Backlog and drag the most valuable ones into This sprint.
  3. Set a due date two weeks from today on the sprint's cards and assign each card to its owner.
  4. Move cards across as you work, show the Review list to your client at the end, and move what they accept to Done.
  5. For a hybrid, put the fixed milestones on the Gantt chart and keep the sprint work on the board.

Run your first sprint on a Kanbanchi board

Backlog, sprint lists and a Gantt chart for the fixed milestones, inside Google Workspace.

Start your free trial

This step is optional. The course works without an account, and your progress does not depend on it.

Course progress and next lesson

Your course progress

0 of 8 knowledge checks passed

  1. Lesson 1: The project life cycleThe five phases of a project and what each one produces · 7 minNot passed yet
  2. Lesson 2: The project management processFrom idea to closing, step by step · 6 minNot passed yet
  3. Lesson 3: Project management methodologiesEight methods compared, and how to pick one · 8 minNot passed yet
  4. Lesson 4: Agile vs waterfall (this lesson)The real differences, played out on one project · 7 minNot passed yet
  5. Lesson 5: Scrum vs kanbanSprints or continuous flow · 7 minNot passed yet
  6. Lesson 6: What is a Gantt chart?Tasks, dependencies and the critical path · 7 minNot passed yet
  7. Lesson 7: How to prioritize tasksOur step-by-step guide on the Kanbanchi blogGuide, no check
  8. Lesson 8: Pre-mortem: spot risks earlyFind out why a project could fail, before it does · 6 minNot passed yet
  9. Lesson 9: Project manager skillsThe hard and soft skills, and how to build them · 6 minNot passed yet

Progress is saved in this browser only, with no sign-up. Pass all 8 knowledge checks to unlock the course badge on the course page.

Agile vs waterfall: FAQ

Is agile better than waterfall?

Neither is better in general. Waterfall fits clear, stable requirements, fixed contracts and physical or regulated work. Agile fits uncertain or changing requirements and products that users can try early. Many real projects use a hybrid of both.

What is the main difference between agile and waterfall?

When you plan and how you handle change. Waterfall plans everything up front and delivers once at the end, so late change means rework. Agile plans and delivers in short cycles and re-plans after each one, so change is absorbed in the next cycle.

Is scrum agile or waterfall?

Scrum is agile. It is an agile framework in which a small team works in fixed-length sprints of one month or less, often two weeks, with three accountabilities: product owner, scrum master and developers.

Can you combine agile and waterfall?

Yes, and many teams do. A hybrid approach typically plans the fixed parts, such as budget, milestones or regulated work, up front in a waterfall style and builds the uncertain parts iteratively in an agile style.

Plan the fixed parts, sprint through the rest

Kanbanchi gives you boards for sprints and a Gantt chart for milestones on the same cards.

Start your free trial