liveBook · Manning

Waterfall methodology

As explained in Think Like a CTO

A project-development approach that plans and defines as much as possible before implementation begins and proceeds through largely sequential stages.

Waterfall plans as much as possible before work begins, using upfront analysis and design to identify problems and define the project. It is one way to break a project into tasks after its intended outcome is set. section 9.1.2

Consider the trade-offs against the project’s needs:

  • For a well-defined project, upfront planning can make time and cost easier to predict and support requests for external bids. section 9.1.2
  • Planning takes time, and work cannot start until the definition is complete. The approach also struggles when requirements, technology, or feature requests change. section 9.1.2

Mapping a route before setting off

A team driving from Miami to San Francisco cannot start until it has mapped the complete route—a comparison for the upfront planning waterfall requires. section 9.1.2

How Think Like a CTO covers it

How deep it goes
Explains planning rationale, benefits, and drawbacks without prescribing detailed project stages.
Examples
Uses a Miami-to-San-Francisco road trip to illustrate why the full plan precedes action.
What it assumes
Assumes the project outcome is defined before tasks and the delivery approach are planned.
What you can do after
Evaluate the predictability, planning effort, and change tolerance of a waterfall project.
How it connects
Contrasts waterfall with agile as another approach to breaking down a project.
Cover of Think Like a CTO
liveBookmanning.com
Read Think Like a CTO on liveBook Get the book at manning.com

Also explained in

Compare how 3 books explain waterfall methodology →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.