Waterfall

A phase-based Waterfall template for fixed-scope projects — move work through requirements, design, build, QA, release, and maintenance with clear gates.

About this template

This template implements a classic Waterfall delivery flow with sequential phases and clear expectations at each gate. It's ideal when requirements are stable, approvals matter, or changes are expensive.

Each phase includes guidance to align teams on deliverables like requirements specifications and technical design.

Documentation fields let you link your SRS and technical specs directly to the work — so phase gates don't rely on scattered docs.

What's inside

Columns included

Requirements gathering & analysisSystem designImplementation / DevelopmentTesting / QADeployment / ReleaseMaintenance & support

Task types

GreenBlueCobaltPinkOrange

Custom fields

SRSDesign document / Technical specificationOther

Key features

  • Sequential phases with clear deliverables
  • Strong fit for fixed-scope and regulated work
  • Built-in links for SRS + technical/design docs
  • Stakeholder approvals become explicit gates
  • Maintenance stage included

Who is this template for?

  • Fixed-scope projects
  • Regulated/compliance-heavy teams
  • Implementation and delivery teams
  • Projects with formal sign-offs
  • Teams needing phase-gate visibility
Ready to get started?
Learn how to create a board from this template in just a few steps.
Read the step-by-step guide

Frequently asked questions

What are the phases?

Requirements → System Design → Implementation → Testing/QA → Deployment/Release → Maintenance.

When should I use Waterfall vs Agile?

Use Waterfall when requirements are stable and sign-offs are required; use Agile when requirements evolve frequently.

What documentation is included?

Fields for SRS, technical/design specification, plus space for additional docs.

How do I handle change requests?

Treat them as new tasks in Requirements with explicit approval before they enter downstream phases.

Related templates