Develop criteria for planning horizons (or “time buckets”) to include a total number of horizons and duration for each horizon. As an analogy, imagine navigating a boat across a treacherous and unknown sea. Say, the horizon is 5 miles off, and you think the crossing is 25 to 30 miles long. You should stop the boat, peer off to the horizon, and rechart your course at least 5 times. This is the assumed total distance of the crossing divided by the distance to the horizon, plus a safety factor. Here's an example: An 18-month program with 3-month planning horizons and a 20 percent safety factor would have 7-time horizons at Level 1 of the WBS. Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
My take -
Essentially, looking at a large task as phases (buckets). Each phase completion is a major milestone (horizon) toward the final target. An 18 month program, split into 6 3-month phases; adding in a contingency factor of 20%, or ~3-months (18 x .20) used with planning and forecasting (budget and resources).
...
3 replies by Tam Nguyen
Jun 26, 2017 12:09 AM
Tam Nguyen
...
Thank you very much.
Jun 28, 2017 3:58 PM
Tam Nguyen
...
Does method overshoot a project?
Jun 28, 2017 4:00 PM
Tam Nguyen
...
thank you, Mr. Andrew
Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
Rolling Wave Planning is indeed used when you can not or want not plan the full scope in detail at the beginning, but you know about the rough full scope (18 months plus 20% or 25-30 miles) and have idea how far you want to plan ahead in detail (3 months or 5 miles). Often you can add some details to the next horizon after the one directly ahead.
Agile Scrum has some similarity here, the horizon is the sprint duration (often 2-4 weeks) and you only do a planning for the next sprint in full detail.
...
3 replies by Tam Nguyen
Jun 26, 2017 12:10 AM
Tam Nguyen
...
appreciate your explanation
Jun 28, 2017 3:57 PM
Tam Nguyen
...
But this method makes construction industry become over cost
My take -
Essentially, looking at a large task as phases (buckets). Each phase completion is a major milestone (horizon) toward the final target. An 18 month program, split into 6 3-month phases; adding in a contingency factor of 20%, or ~3-months (18 x .20) used with planning and forecasting (budget and resources).
Rolling Wave Planning is indeed used when you can not or want not plan the full scope in detail at the beginning, but you know about the rough full scope (18 months plus 20% or 25-30 miles) and have idea how far you want to plan ahead in detail (3 months or 5 miles). Often you can add some details to the next horizon after the one directly ahead.
Agile Scrum has some similarity here, the horizon is the sprint duration (often 2-4 weeks) and you only do a planning for the next sprint in full detail.
Rolling Wave Planning is indeed used when you can not or want not plan the full scope in detail at the beginning, but you know about the rough full scope (18 months plus 20% or 25-30 miles) and have idea how far you want to plan ahead in detail (3 months or 5 miles). Often you can add some details to the next horizon after the one directly ahead.
Agile Scrum has some similarity here, the horizon is the sprint duration (often 2-4 weeks) and you only do a planning for the next sprint in full detail.
But this method makes construction industry become over cost Saving Changes...
My take -
Essentially, looking at a large task as phases (buckets). Each phase completion is a major milestone (horizon) toward the final target. An 18 month program, split into 6 3-month phases; adding in a contingency factor of 20%, or ~3-months (18 x .20) used with planning and forecasting (budget and resources).
Does method overshoot a project? Saving Changes...
Rolling Wave Planning is indeed used when you can not or want not plan the full scope in detail at the beginning, but you know about the rough full scope (18 months plus 20% or 25-30 miles) and have idea how far you want to plan ahead in detail (3 months or 5 miles). Often you can add some details to the next horizon after the one directly ahead.
Agile Scrum has some similarity here, the horizon is the sprint duration (often 2-4 weeks) and you only do a planning for the next sprint in full detail.
My take -
Essentially, looking at a large task as phases (buckets). Each phase completion is a major milestone (horizon) toward the final target. An 18 month program, split into 6 3-month phases; adding in a contingency factor of 20%, or ~3-months (18 x .20) used with planning and forecasting (budget and resources).
