What is waterfall product management?

Waterfall refers to a sequential model for planning, building, and delivering new products and features. The requirements for any new customer experience are defined upfront and implemented in discrete phases. Each phase has specific activities that must be documented and approved before the next phase can begin.

The waterfall model is often used when managing the production and delivery of hardware products, such as in manufacturing and construction. In these industries, establishing the full scope before beginning work is often important because change is costly and difficult to accommodate in the development or manufacturing process. Activities are managed in a linear way to ensure that the requirements are met. The finished product or feature is delivered in its complete form.

History

The waterfall approach was first introduced by Dr. Winston W. Royce in 1970 in a paper on how to implement large software systems. Royce defined a logical progression of steps to help teams achieve “an operational state, on-time, and within costs.”

In 1976, Thomas E. Bell’s and T.A. Thayer reinforced this approach in a paper called “Software requirements: Are they really a problem?” The authors studied the challenges associated with incorrect, ambiguous, inconsistent, or missing requirements. They concluded that starting with a clearly defined set of requirements and following a top-down “waterfall” approach to implement them was an effective method to achieve a successful outcome.

Waterfall established itself as the predominant product development methodology for the next twenty years. Then, in the early 2000s, agile methodologies emerged. Agile proposed a more flexible way to incorporate feedback once work was underway. The goal was that companies would be able to deliver new products and functionality to market faster, delighting customers and achieving a competitive advantage.

Today, many companies use an agile approach for managing software-based products. Hybrid agile-waterfall methods also provide a way to include some flexibility into traditional workflows. Some organizations combine the planning structure of waterfall — such as fixed deadlines and cost forecasting — with lighter documentation and iterative feedback cycles so they can respond faster to changing requirements. But, as you will learn in this guide, there are a number of situations when a true waterfall model can still be effective.

Waterfall phases

Let’s take a closer look at how a waterfall model works. There are six phases. Each phase is distinct and must be completed in order for the next one to begin. The table below lists the phases in sequential order and provides an overview of what must be accomplished.

A stage gate review often happens between phases. The stage gate serves as a decision point for whether a project can proceed to the next phase. This provides an opportunity for the project team to assess status, identify risks, and review cost and schedule. If a project is struggling to stay on track, it may be put on hold or terminated.

When to choose waterfall

There are a number of pros and cons to consider when choosing whether to use a waterfall approach. On the positive side, planning is more straightforward because requirements are agreed upon upfront and the full scope of the work is known in advance. Conversely, there are more risks to manage and a higher possibility of customers being dissatisfied with the end result. This is because customers typically do not see what will be delivered until the project is completed, at which point it is too late in the process to make changes.

To help you decide if waterfall model is a good fit for your work, consider this list of characteristics:

Requirements are clear and unlikely to change

• Cost of change is high

• Strict budget and/or time constraints

• Resources with required expertise are available

• Customers do not need to be involved during development

• Underlying technology is well known and stable

• Complex dependencies between projects

Many organizations use waterfall for managing the development of physical or hardware products, as well as hybrid products that include both hardware and software components. This is because there are many dependencies to manage and it is challenging to change requirements midway.

Another use case is developing products for heavily regulated industries. Rigid change-control processes and stage gates between phases make it easier for organizations to ensure that compliance requirements are met and to address any issues along the way.

Waterfall in product management

A waterfall model emphasizes the importance of upfront planning and comprehensive documentation. You can see this in the table above with the first phase being requirements analysis. It is key that product managers set strategy and plan releases. Here is a look at some of the practices and tools product managers use to achieve product success in a waterfall environment.

Product roadmap

Product managers build a long-term roadmap that commits to delivering specific features on a set timeline. Plans are defined on an annual cycle and release budgets and dates are fixed. Here is an example of a product portfolio roadmap. It shows the timeline for delivering releases over a 12-month period.