Project Management

Please login or join to subscribe to this thread

Difference between these techniques: Rolling Wave Planning, Decomposition and Progressive elaboration

linkedin twitter facebook   Work Breakdown Structures (WBS)  
avatar
Peyman Mokhtarzadeh Sharabiani North Vancouver, Canada
What are the differences in above techniques? Which one is the best technique for Agile Methodology?
Sort By:
< 1 2 3 >
avatar
Stéphane Parent Self Employed / Semi-retired| Leader Maker Prince Edward Island, Canada
Nov 17, 2017 2:55 AM
Replying to Peyman Mokhtarzadeh Sharabiani
...
Stephane

Yes I mean using Agile approached for Project Integration Management System throughout the project which agile approached for the product will be included.
By definition, you cannot have a "best approach" when you do Agile. All you have is a "best approach for this project for now".

Your rolling wave planning might work well with one of your project. You retrospective may find that it doesn't work as well with another project or the same project later on. You may have to use a different or custom approach.
avatar
Chuck Doerrler Senior IT Project Manager| Financial Services Company Hartford, Ct, United States
Apologies for lateness. I've been practicing RWP for years and it's very Agile. RWP agilizes and modernizes waterfall.

All 3 techniques are tightly coupled. Decomposition breaks down a larger deliverable into activities and tasks which become inputs to Progressive Elaboration (PE). As we better understand what we need to do in more detail (PE) we can continuously plan in the near term, which is an input to RWP. As we continuously plan from week to week (rolling), we are using RWP, PE, and decomposition together.

Remember, RWP is a planning method within a larger plan that's blended with milestones and key deliverables - high level timeline. A good RWP plan is no longer than 1-2 weeks as the team drives to the next milestone or key deliverable.PE and decomposition are inputs to continuous planning. Embrace the Agile Manifesto principle of "Responding to Change over Following a Plan" when managing your project.
avatar
Peyman Mokhtarzadeh Sharabiani North Vancouver, Canada
Hi Chuck

Thanks for your contribution , your points are that RWP, PE and Decomposition are similar but there are some how different definitions :

Decomposition and RWP both are tools and technique in real definition.

Decomposition is tools and technique in Project Scope Management - in Create WBS 5.4 also in Project Time Management - in Define Activities 6.2.

Say you are handling a water treatment plant electrical portion and need to create a new control panel for a water treatment plant.

What do u do?

Identify activates that you need to do viz design & engineering,drafting,checking and closing so you have subdivided the work package into smaller manageable components of schedule activities which is decomposition.Remember decomposition was used to create WBS process, if u further decompose WBS package you get schedule of activities.

RWP is tools and technique in Project Time Management - in Define Activities 6.2

There are 3 branches in a tree one above the other .You are in the second branch.Your friend on the top branch tells u that he can see a truck on this way.But you are not able to vision the truck but after some time when the truck comes near to your area vision you are able to see.

Rolling wave planning replicates this example that things in near future should be relatively clearer, while project activities in distant future may not be as detailed. It is a kind of progressive elaboration .

Progressive Elaboration concept is so similar to RWP but there are some different as bellows :

Planning is an iterative process. Often times, it’s difficult to do detailed planning of a project in the beginning. As the project evolves, and more specific and accurate details are available, the planning gets more detailed. With each successive iteration of the planning process, the project plan becomes more elaborate and complete. This approach to planning is known as Progressive Elaboration.

Two forms of Progressive Elaboration:

The PMBOK® Guide, 5th Edition mentions two forms of Progressive Elaboration - Rolling Wave Planning and Prototypes.

Summary:
Rolling Wave Planning and Prototyping are forms of Progressive Elaboration.

Prototype is also tools and technique of Project Scope Management - in Collect Requirements 5.2

Prototyping is a method of obtaining early feedback on requirements by providing a “tangible” working model or a mock-up of the expected product before actually building it. It gives stakeholders an opportunity to test and experiment with a model of their final product and give them a way to ‘visualize’ their end product. Prototypes help to identify problems early in the project and reduce project risks.

Your company wants to build a commercially viable model of a Hydrogen-powered car. Initially, your researchers build several working models (prototypes) of the car, maybe of a smaller size, to conduct experiments and check the feasibility of the project. Based upon the results of the feasibility studies, your company decides whether to move forward with or kill the project.

Either it is useful for Mass Building Construction to find out the buyers interest....

Progressive Elaboration is comprehensive definition which improving the process .
The concept of progressive elaboration refers specifically to a project management technique in which the plan for the particular and designated project is being continuously and constantly modified, detailed, and improved as newer and more improved (as well as more highly detailed) .

For Agile approach the best technique is RWP as per my opinion.

Although there are many other continuous improvement tools available such as PDCA, TQM, Six Sigma,etc. We can say as traditional method but

Agile Approach takes Continuous Improvement one step further by incorporating people improvements through the use of self-organizing teams, cross-functional training (Matrix) and regular team-building activities.
avatar
Chuck Doerrler Senior IT Project Manager| Financial Services Company Hartford, Ct, United States
My main point is that all 3 are complimentary and work better when integrated rather than thinking of them as silo'd, unrelated techniques.

I recommend, in general, not getting boxed into strict, one dimensional readings of definitions via the PMBOK. Rather use them as guidelines toward facilitating critical thinking across the project and the team. Blending techniques and mindsets helps drive project innovation, execution, and high performance.
avatar
MIFTAH ARIEF Project Control Engineer| PT.RAA Depok, West Java, Indonesia
Could anyone advice on how to create a rolling wave model/diagram? is it possible for a rolling wave as a style, tolls and technique, or approach become a standard/model? Like, conceptual phase by phase, staging, or other structure would impact on a rolling wave technique?
avatar
Raju Rao Founder & Principal| Xtraplus Learning & Consulting Chennai, Tn, India
Interesting discussions by all . I will second the explanation given by Chuck Doerrier. Though PMBOK does give lot of information in terms of definitions and tools and techniques ,we should not bogged down by semantics, and instead understand the principles behind these techniques and how they could be applied appropriately
< 1 2 3 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"Education is the ability to listen to almost anything without losing your temper."

- Robert Frost

ADVERTISEMENT

Sponsors