Waterfall vs. Agile: What’s the Difference?

Companies generally approach software development with one of two very different methodologies: waterfall or agile. Even if you’re not a developer, if you work for a startup you will need to have a topline understanding of the methodology your team uses and the difference between waterfall and agile.

Waterfall is a very rigid, step-by-step framework with distinct phases and detailed planning. The product or feature requirements are fully detailed in advance, and each stage of development is done just once. The name comes from the idea that the project flows all in one direction, like a waterfall.

The waterfall process proceeds in sequence:

• Conception or decision on the product/feature to build
• Analysis to determine requirements
• Coding
• Testing
• Implementation or launch

Agile is a more flexible, iterative methodology conducted in numerous time-boxed sprints (with one sprint being, for example, a two-week period). Agile is often implemented using a scrum or sprint system under direction of a scrum master or product manager, who sets up tasks and goals for the upcoming sprint, assigns them to developers, evaluates progress at the end of the sprint, and sets up the next sprint with unfinished and new work. Sprints are repeated until the project or product is complete. While the general sequence of work may be the same as that of waterfall, it’s more flexible and some phases will be repeated in multiple sprints.

Waterfall is the more traditional methodology of the two and is best used when change is not expected and continual customer feedback is not necessary. Agile has gained wide use recently and is best for complex projects that will require significant of feedback from customers along the way (which, one could argue, could be most projects).

Either way, understanding the way your development team is working will help you know when and how to interact with what they’re building.