Waterfall Model
By: A Staff Writer
Updated on: Jul 19, 2024
What: A classic project management approach where each phase flows into the next (like a waterfall). Phases include requirements gathering, design, development, testing, and deployment.
Who: Origins in manufacturing and construction, adapted for software in the 1970s.
Why: Offers structure, but is best for projects with well-understood requirements and low risk of change.
When: If your scope is crystal clear from the outset, project timelines are critical, and your industry demands detailed documentation.
How:
-
- Invest heavily in defining requirements upfront.
- Minimize changes mid-project, as they can derail things.