Rolling-wave planning: How to manage projects flexibly under uncertainty

Traditional plans often only provide certainty for as long as reality does not change. This can be seen, for example, in projects that extend over several months, during which requirements, resources or priorities may shift. Particularly in such dynamic environments, rigid plans quickly become outdated. Rolling-wave planning therefore creates the necessary balance between clarity of objectives and flexibility.

In rolling-wave planning, a period-oriented form of planning, plans are updated, specified and revised at regular intervals. Regularly can mean that planning takes place once per month or even once per quarter. This contrasts with traditional planning, where planning happens only once. The key point is that activities in the near future are planned in detail, whilst more distant periods, which are usually 10 to 18 months in the future, are initially only outlined roughly. The closer an event gets, the more detailed this rough planning becomes. It is therefore a top-down approach in which resources and task plans are implemented and allocated increasingly precisely in stages. With each wave, the planning is updated and refined.

Rolling-wave planning has several advantages which allow changes to be integrated more effectively without calling the entire project into question. On the one hand, its high degree of flexibility should be mentioned, enabling companies to react quickly to market changes. Market changes can create new priorities and unforeseen risks. Rolling-wave planning makes it possible to respond appropriately to these, since planning has not been carried out too far into the future. This makes it possible to avoid planning errors, as plans can be adjusted continuously. It reduces uncertainty, as data for the near future can be predicted more precisely. The risk of inaccurate forecasts is therefore lower than with traditional planning. More precise forecasting allows resources to be used optimally, so that, in the best case, there are no delays or bottlenecks, for example in the form of a lack of staff. In addition, managers always work with current data rather than outdated annual budgets, enabling them to respond quickly to new requirements, priorities or risks.

A fixed planning cycle is crucial for ensuring that projects remain manageable. In practice, monthly or quarterly updates have proved effective, allowing the team to regularly review the current status and adjust planning flexibly to new developments. The “rule of ten” provides simple guidance: over a period of around ten months, rough multi-project planning takes place; within ten weeks, projects are specified and dependencies are coordinated; and over a period of around ten days to two weeks, operational management takes place. Typically, resources are initially planned only roughly at team or department level and are only assigned specifically to individual people and tasks during the following four to eight weeks. Depending on the organisation, planning can take place either top-down (e.g. through strategic objectives such as Hoshin Kanri, a strategic management approach through which company objectives are systematically broken down and coordinated across individual levels) or bottom-up (e.g. through OKRs, Objectives and Key Results, which can be used to translate strategic objectives into measurable results).

Flexibility does not mean arbitrariness: the overarching objectives remain stable. Despite short-term flexibility, the overarching strategic objectives and milestones, in other words the “rough plan”, remain in place. However, the paths to achieving them may vary, because the more precisely one tries to plan the distant future, the less precise the result becomes. It is also important that project management remains clearly regulated. Whilst planning focuses on customers, operational management deals with handling deviations within the team. The overarching objectives set the direction.
As you may have noticed, rolling-wave planning has several challenges which must be taken into account. Regularly updating plans ties up many resources in the form of staff and time, which is also associated with higher costs. The requirement that data must be as current as possible also leads to a high level of resource commitment, after all, someone has to collect the data. If these changes or updates in planning are not regularly and accurately documented, this can lead to inconsistencies in planning because not every change is remembered.

Rolling-wave planning combines structure with adaptability and is therefore ideal for complex projects in uncertain environments. However, the planning effort is greater due to its regularity. In addition, conflicts and a lack of acceptance among employees may arise if the constant changes are perceived as unstable. It must also be taken into account that, although the process ensures flexibility, fixed planning for the near future can also lead to restrictions. In times of Artificial Intelligence and real-time data analyses, however, it should not be forgotten that the automation and forecasting accuracy of rolling-wave planning can continue to increase.