Sometimes the whole picture is not clear when you are planning a project. But with a traditional project management methodology, such as waterfall, you set everything up first and then you’re stuck with it.
But the waterfall methodology is only one way to manage a project. Other project managers prefer a more iterative process, like scrum. Others still prefer forms of agile software development where they have room to adjust their project plan. That type of agile project management is called rolling wave planning or wave planning.
Rolling wave planning might not be for every project, but it could be for yours. Wave planning, project management software and a skilled and experienced team might be just the combination to deliver project success for you.
What Is Rolling Wave Planning?
Rolling wave planning is a type of project schedule that focuses on iterative work and frequent updates to the project plan. It is a project planning technique for projects that don’t offer all the data needed to create a plan or schedule up front.
That does not mean the project starts without a plan. It begins as most projects do, with a work breakdown structure (WBS) to the tasks, work packages and deliverables within the project scope. The difference with rolling wave planning is that the WBS is filled only to the project manager’s current knowledge.
The project plan then evolves as more details become clear. This project planning technique is like putting the track in front of the train as you move forward. By doing this, work always moves forward in short sprints throughout the project phases, while project planning occurs in the background to offer guidance once those short-term tasks are done.
Though most often applied to agile software development or new product development, it can be used for other projects that might not move as swiftly.
Rolling Wave Planning Benefits
A rolling wave plan is very helpful when the project plan has a lot of uncertainty. When you need to manage risk, rolling wave planning is set up to let you pivot as needed if any of those risks become issues. This gives you room to address those issues and resolve them before they become problems.
Outside of risky projects, rolling wave planning lets you ensure you identify all key details for the project scope you are about to execute. This gives team members a clear picture of the work items they need to do in the immediate future of the project schedule. That makes buy-in more likely, as well as accountability.
Of course, one of the most important benefits of using a rolling wave planning technique is that it gives you wiggle room in the project. With traditional project management methodologies, you are often stuck with your plan. With rolling wave planning, the plan can change quickly.
Which Industries Benefit from Using Rolling Wave Planning?
Rolling wave planning technique is suitable for projects where all the project planning data is not immediately available and when the project execution is risky. Generally, rolling wave planning is mostly used for software development.
But there are other projects and industries that are a good fit for rolling wave planning and its iterative type of project planning. For example, research and development (R&D) projects. These projects are not structured to finish with a knowable deliverable. They are exploring and hoping to discover new products or services.
Similarly, high-tech projects lend themselves to rolling wave planning. Any project that is devoted to innovation is going to constantly pivot to take advantage of opportunities. They are not on a linear path. They require the flexibility to respond as features change, but still provide the control needed to deliver any project successfully.
Rolling Wave Planning vs Agile Sprints
We have already mentioned agile sprints, which are periods in which you execute tasks. They are also a highly iterative type of project planning. But are they synonymous with rolling wave plans?
Well, both are iterative ways to work. They both involve having daily standup meetings before working on the assigned tasks. So there are similarities between rolling wave planning and agile sprints.
But they are not interchangeable project management techniques. Rolling wave planning is a better fit when you are working with ordered tasks on a tight project schedule. While it is true that rolling wave planning is only planning in the near term, the tasks are sequential, and the deadline is firm.
Sprints a way to work in an agile project environment, which is not so focused on task sequences or the critical path. Also, deadlines can be more flexible. Therefore, rolling wave planning and scrum agile sprints share some attributes, but they are different, and should not be applied haphazardly. Find the one that works best within the framework of your project plan.
Rolling Wave Planning Steps
Rolling wave planning is a great way to keep your project meeting its scope, schedule and budget requirements while staying creative. It is often difficult for project managers to keep those two ideas in their heads. Meeting requirements means having a structure, and creativity is notoriously loose.
But by learning how to do rolling wave planning, project managers can reduce uncertainties and keep a project planning framework that allows flexibility to work creatively. Project managers can track, schedule and update their plans by following these six rolling wave planning steps.
Step 1:
The project manager starts the process by identifying risks and planning to reduce their impact if they show up in the project. The project manager will also talk about the project requirements with the team, when they need to be met and who will work on them. Next, roles and responsibilities are outlined for the team.
Step 2:
Working with the team, develop a timeline, budget and what resources you need. The WBS will be helpful at this point as you define the tasks and deliverables in the project. The larger project is broken into smaller ones called horizons. This can be detailed on a Gantt chart.
Step 3:
Plan the first iteration, often called a wave, which means adding details to the work you have already done. Tighten up the timeline, budget and necessary resources for the wave. When the team is working, the project manager should start to plan the next wave.
Step 4:
Create a baseline for time, cost and scope to make sure your wave is meeting its deadline, budget and using the resources you allot for it.
Step 5:
The first wave begins. Teams work on their tasks and the project manager monitors and tracks their progress and performance. The project manager will also work towards reducing uncertainties in the later stages of the project.
Step 6:
Continue this process of iteration until you have reached the end of the project. When the project is closed, have a postmortem to discuss the things that did and did not work, so you can start the next project on better footing.