Skip to content
BENIBIX Learn

Waterfall, Agile and Hybrid

Level 5 Β· Ways to run a project

The three main ways to plan and build a project's result. What waterfall, agile and hybrid each do well, and how to pick one for the work in hand.

Course contentsLesson 10 of 11

After this lesson you can

  • Describe waterfall, agile and hybrid
  • Pick an approach for a given project
  • Explain why a hybrid needs a clear line

12 mincovers 4 glossary entries

Worth reading first: Project Life Cycle and Phases

Which way to run a project: waterfall, agile or hybrid

A delivery approach is the way a project plans and makes its result. There are three main ones. Waterfall plans everything first and hands over once, at the end. Agile builds in small pieces and hands one over every few weeks. Hybrid mixes the two. The right one depends on how clear the goal is on day one.

The waterfall model runs the work in steps, one after another: gather the needs, design, build, test, hand over. Each step must end before the next one starts. It is also called the predictive approach. It tries to predict the whole job up front.

Waterfall works when the goal is clear and will not change. A bridge is the classic case. Nobody changes their mind about the river halfway through. The weak spot is late feedback: users see the result near the end, and a mistake found in testing sends the team all the way back.

Agile works the other way round. The team builds a small working piece in a short round, often two weeks, and shows it to the users. What they learn shapes the next round. It suits work where people only know what they want once they see something.

A hybrid approach mixes the two by part. The fixed parts, such as the budget, the end date or the hardware, get a full plan up front. The parts that may change, such as the software, are built in short rounds. Many real projects work this way without calling it hybrid.

Agile does not mean no plan. Both approaches plan. Waterfall fixes the whole plan at the start. Agile plans in short steps and expects the plan to change. The difference is when the planning happens, not whether it does.

The common mistake is using the same approach for every project out of habit. The work should pick the approach. Another is a hybrid with no clear line between the parts. Then nobody knows which parts are allowed to change.

The three approaches side by side

ApproachHow it plansWhen it hands overFits when
WaterfallAll at the startOnce, at the endThe goal is clear and fixed
AgileA little each roundEvery few weeksThe goal will change as people learn
HybridFixed parts up frontBoth, part by partSome parts are fixed, some are not

Which one to pick

  1. 1

    Pick waterfall

    When a change late on would cost a fortune, like steel already ordered for a bridge.

  2. 2

    Pick agile

    When users cannot say what they want until they try it, like with a new app.

  3. 3

    Pick hybrid

    When one part is fixed and another is not, like a smart fridge and the app that runs it.

The same time, spent three ways. Notice when each one first hands something over.

Worked example

Lucy builds a smart fridge

Lucy's team has 12 months to build a smart fridge and its phone app. The fridge parts must be ordered by month 3, so the fridge gets a full plan up front.

The app is built in two-week rounds, 26 of them, and shown to users every round. The team writes down which part is which on page one of the plan.

The words for this lesson4

Check yourself

Does an agile project have no plan?

Finished this lesson?

Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.