A six-month project plan can look impressively precise while depending on decisions nobody can make yet. Giving every distant task a detailed date does not remove uncertainty. It may only hide the assumptions behind a long list.
PMI’s discussion of planning packages explains rolling-wave planning: near-term work is elaborated into detailed work packages, while later work remains at a broader planning level until it can be developed responsibly.
A small project example
Imagine a team moving a service to new software. The next stage is a pilot with one group. The pilot tasks can identify owners, test cases and dates. The later rollout still needs a budget, dependencies and an intended sequence, but its detailed training schedule may depend on what the pilot reveals.
That later stage is not an empty box. Write what is known, what remains uncertain and which result will allow a more detailed plan. “Plan rollout after pilot review” is useful only if the review itself has a date, an owner and a defined output.
Keep three controls visible
- The next planning point: when the team will expand the following stage.
- The information needed: the decisions, measurements or approvals required.
- The commitments already made: dependencies and deadlines that the broader plan must still respect.
Choose the length of the detailed planning window to suit the work. A procurement with a long lead time may need attention well before a nearby task that can be arranged quickly. “Later” in the schedule does not always mean “safe to ignore today.”
When the wave moves forward, preserve the important assumptions and explain material changes. Compare the updated plan with actual progress rather than repeatedly pushing unresolved work into a distant block.
The technique is useful when it replaces false precision with deliberate planning. Its discipline comes from adding detail in time, not from postponing every difficult question until the team reaches it.