Design Manager Hub
Product Design Reference
  • Welcome
  • Leadership Foundations
    • Leadership Blueprint
    • Good Managers
    • Bad Managers
    • Change Management
    • Leadership Styles
  • Managing People
    • Roles
      • Design/UX
      • Engineering
      • Product & Agile
      • Management
      • Levels
      • Soft Skills
    • Hiring
    • Onboarding
    • Culture
    • Performance Management
    • Feedback
    • Retention
    • Employee Exits
    • Managing Up
  • Meetings
    • Overview
    • One-on-Ones
    • Agile Meetings
    • Design Critiques
    • Stakeholder Meetings
    • Retrospectives
    • Workshops
    • Performance Reviews
    • All-hands
    • Skip-level Meetings
    • PIP Meetings
    • Exit Interviews
    • Public Speaking
  • Strategy
    • Overview
    • Vision & Goals
      • Product Vision
      • Goal Setting
      • Big Hairy Audacious Goal (BHAG)
      • Product Innovation Charter (PIC)
      • Product Trio
    • Prioritisation
      • Reach, Impact, Confidence, and Effort (RICE)
      • ICE Scoring
      • MoSCoW
      • Impact-Effort Matrix
      • The Kano Model
    • General Analysis
      • Cost-Benefit Analysis (CBA)
      • SWOT Analysis
      • The 5 Whys
      • The Sunk Cost Fallacy
    • Market Analysis
      • Product-Market Fit (PMF)
      • PEST Analysis
      • Customer Acquisition Cost (CAC)
      • Customer Lifetime Value (CLTV)
      • 6 Forces
    • Canvases
      • Business Model Canvas
      • Value Proposition Canvas
      • Lean UX Canvas
      • UX Research Canvas
      • Product Canvas
    • Customer Insights
      • User Journey Mapping
      • Net Promoter Score (NPS)
      • Customer Satisfaction Score (CSAT)
      • A/B Testing
      • Funnel Analysis
      • Jobs-to-be-Done (JTBD)
    • Organisational Alignment
      • McKinsey 7S
      • Weisbord's 6 Box Model
      • Balanced Scorecard
  • Process
    • Overview
    • Agile
    • Waterfall
    • Lean UX
    • Design Thinking (DT)
    • Design Sprint
    • DevOps
    • Cross-Functional Teams
    • Double Diamond
    • Reverse Double Diamond
    • GTD Methodology
    • Jobs-to-be-Done (JTBD)
    • Kaizen
    • Object-Oriented UX
    • Responsible, Accountable, Consulted, Informed (RACI)
    • Six Sigma
    • Work Breakdown Structure (WBS)
  • Cognitive Toolkit
    • Overview
    • Prioritisation
      • 6 Box Framework
      • Eisenhower Matrix
      • Impact-Effort Matrix
      • The Pareto Principle
    • Problem Solving
      • First Principles Thinking
      • Systems Thinking
      • Inversion Thinking
      • Abstraction Laddering
      • Occam's Razor
      • Divergent & Convergent Thinking
    • Decision Making
      • The Map Is Not the Territory
      • The Cynefin Framework
      • Second-order Thinking
      • System 1 & System 2 Thinking
      • The Hard Choice Model
      • OODA Loop
    • Managing People
      • Skill-Will Matrix
      • The 4 Worker Types
      • The 9 Employee Types
      • Maslow's Hierarchy of Needs
      • The Peter Principle
      • Dunning-Kruger Effect
      • Circle of Competence
      • Hanlon's Razor
      • Johari Window
      • The Minto Pyramid
  • Insights
    • Insightful Articles
    • Research Foundations
    • Design Roles
  • Resources
    • Articles
    • Books
    • Templates
    • Education
    • Conferences
    • Video Hub
    • Quotes
    • Experts
    • Software
Powered by GitBook
On this page
  1. Process

Waterfall

Last updated 6 months ago

"Waterfall" is a linear project management method with distinct, sequential phases. This sequential approach to project management and software development is a traditional methodology where progress flows steadily downwards through defined phases. These phases typically include requirements gathering, design, implementation, testing, deployment, and maintenance. Each phase must be completed before the next one begins, resembling a waterfall cascading down in a linear manner.

One of the key features of the waterfall model is its emphasis on extensive upfront planning and documentation. This methodology assumes that requirements can be clearly defined at the beginning of the project and that changes to those requirements are both infrequent and expensive.

While the waterfall model has been widely used in the past, it has certain limitations, particularly in today's fast-paced and dynamic business environment. Critics argue that its rigid structure can lead to difficulties in accommodating changes and responding to customer feedback effectively. As a result, many software development teams have adopted more flexible and iterative approaches such as Agile or DevOps.

Further Viewing

Further Reading

LogoAgile and Waterfall Development: A Comparison and Selection GuideMedium
LogoWhat is the Waterfall Model? - Definition and GuideSearch Software Quality
LogoWhat is the Waterfall software development methodology and is it still relevant?K&C
LogoAgile vs. Waterfall | The Difference Between Methodologies
Image by
Tmap