Waterfall model
The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them.
Lead Developer Career Guide
A linear, sequential project-management and software-development methodology in which predefined stages are completed in order before the next stage begins.
- How it is used
- Organizes software projects with clear requirements around predefined stages, detailed upfront planning, and sign-offs.
- How deep it goes
- Defines five sequential phases and discusses planning benefits, change costs, and defect-rate calculation, but not detailed phase procedures.
- Examples
- Uses Windows development as a staged project example and calculates a 15% defect rate from 150 defects across 1,000 lines of code.
- What you can do after
- Evaluate whether sequential delivery fits fixed requirements and clear scope, and calculate a defect rate from defects and lines of code.
Read how Lead Developer Career Guide explains waterfall model →
Delivering Machine Learning Projects: From design to deployment
Waterfall is a sequential software development methodology in which requirements, design, implementation, testing, and acceptance proceed in ordered stages.
- How it is used
- Organizes software projects around ordered requirements, design, implementation, testing, and acceptance stages.
- How deep it goes
- Defines the delivery sequence and critiques estimation, user-disconnection, and upfront-requirements risks without detailing governance procedures.
- Examples
- Uses requirements, designs, work programs, code, tests, and user acceptance as sequential project artifacts.
- What you can do after
- Evaluate sequential delivery by identifying handoff, estimation, user-fit, and change-management risks.
Read how Delivering Machine Learning Projects: From design to deployment explains waterfall model →
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.
- How it is used
- Breaks a defined project outcome into tasks through upfront planning before implementation begins.
- 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 you can do after
- Evaluate the predictability, planning effort, and change tolerance of a waterfall project.
Also covered in
- Collaborative Software Design: How to facilitate domain modeling decisions
- Functional Design and Architecture: Examples in Haskell
- Cloud Observability in Action
- Build High Value Software SystemsIn early access (MEAP)
- React Hooks in Action: With Suspense and Concurrent Mode
- Grokking Relational Database Design
What to know first
- agile software developmentAgile software development is an iterative approach to developing software through incremental delivery, collaboration, feedback, and adaptation to change.
- bugA software bug is a defect that can cause software to behave incorrectly or differently from its intended or specified behavior.
- communicationCommunication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.
Related concepts
- specification-driven developmentcontrasts with · Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software.
- agile software developmentcontrasts with · Agile software development is an iterative approach to developing software through incremental delivery, collaboration, feedback, and adaptation to change.
- incremental developmentcontrasts with · Incremental development is an approach that builds or changes a system through successive small steps rather than a single large change.
- requirements analysishas part · Requirements analysis is the systematic process of eliciting, clarifying, assessing, and documenting the needs and constraints a system or product must satisfy.
- software testinghas part · Software testing is the systematic evaluation of software under specified inputs or conditions to assess its behavior against expected results or requirements and identify defects.
Questions about waterfall model
What is waterfall model?
The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them.
Which Manning books explain waterfall model?
Lead Developer Career Guide, Delivering Machine Learning Projects: From design to deployment and Think Like a CTO.
What should I know before learning waterfall model?
Manning books that teach waterfall model usually introduce agile software development, bug, communication and Scrum first.
What is the difference between waterfall model and specification-driven development?
The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them. Specification-driven development is a software development approach in which an explicit specification guides the planning, implementation, and verification of software.
What is waterfall model a kind of?
Waterfall model is a kind of methodology. A methodology is a systematic framework of methods, practices, and principles for organizing and carrying out a type of work.
What are the parts of waterfall model?
Waterfall model includes requirements analysis and software testing.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


