Welcome, Guest
Do you need customer support or technical assistance? Click here to submit a support ticket...

TOPIC: Clarification about - Progressive Elaboration

Clarification about - Progressive Elaboration 7 years 2 months ago #554

  • SURENDRA VAIDYA
  • SURENDRA VAIDYA's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Hi Everyone,
I need help on 'Progressive Elaboration' -

Every project is characterized by Progressive Elaboration. I tried to understand and visualize it in actual contexts. What I am surprised by is by way of progressive elaboration, how do we avoid Scope Creep. Clearly, there is every possibility that someone may term some additional details of the requirements as 'Progressive Elaboration' whereas technically it may actually involve quite some work. Where does one draw a line to clearly demarcate and say - up to this point it's "Progressive Elaboration' and beyond this, it will be increase in scope and hence should go through Change Control / Management?

I have seen many situations where a clear difference of opinion arises and it becomes a case of subjective interpretation of the individual who is looking at that issue.

I think there has to be some expert way of analyzing the situation and giving a clear, convincing explanation on such issues.

How would you approach any such situation which can very well be termed as 'Progressive Elaboration' but actually it may be a Scope Creep?

Thanks a lot for your help and support.

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #577

  • JD Crump, PMP, ITIL-F
  • JD Crump, PMP, ITIL-F's Avatar
Surendra:

Excellent question. As you know with progressive elaboration we are agreeing to work in iterations whereas we know more details about the near-term work than we do about the later work. However, despite this we have gone through the process of defining what is and what is not in scope.

When you document your scope and requirements you are establishing an initial baseline of what is to be accomplished. These are your boundaries. So, what happens if a customer initially asks for a button on a page to submit a form but through progressive elaboration you find out that they want the button to also send an email, update a database, automatically post an entry to a web page, and place an order for a pizza?

THAT is scope creep because when your team created an initial effort / cost / duration for the requirement for a button on a form it used some common initial functional guidelines, which are now very different from what the customer wants.

The best way to avoid this is to document how you planned to implement the button and what the button would do but that often takes more effort than is warranted.

So, your answer is correct: change control.

You have to tell the customer that the request for the button to do all the new things they are asking for is outside the initial scope and *may* require additional effort / cost / duration to complete.

I hope this helps!

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #582

  • SURENDRA VAIDYA
  • SURENDRA VAIDYA's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 9
  • Karma: 0
Hi Crump,

Thanks for your explanation.

I understand the point. Overall I feel that this is one area where PMs have to be more watchful and ensure a balanced approach. This is where individual skills and finesse probably come in to picture.

Best regards,

Surendra Vaidya

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #607

  • Lucia R
  • Lucia R's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 12
  • Karma: 0
Did you notice the difference between Progressive Elaboration and Role Wave Planning? Is there something more apart from knowing that Role Wave Planning is a form of progressive elaboration? Tks in advance, I am new at the forum, hope to keep in touch.

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #611

  • JD Crump, PMP, ITIL-F
  • JD Crump, PMP, ITIL-F's Avatar
Well, there is more to know about progressive elaboration such as its role in portfolio, program and project management as well as in modeling.

In addition, that rolling wave planning is called into action when decomposition isn't possible.

Sometimes *knowing* the answer isn't as black and white as "rolling wave planning is a form of progressive elaboration", you have to know when and how it's called into action and what other forms it takes.

I hope that helps!

Take care,

JD

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #613

  • Lucia R
  • Lucia R's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 12
  • Karma: 0
yes, of course it helps very much, I really appreciate you take the time to answer questions which you already understand. I am taking the exam in December and Cornelius support is outstanding. There are so many book but I must focus only on the pmbok and cornelius prepcast because I cannot handly anymore, and now I wanted to experience also forums and it is very good. Thank you so much! but it is my first time in these professional forums, so coming again to this point: could you explain a bit more regarding your 1st sentence? "there is more to know about progressive elaboration such as its role in portfolio, program and project management as well as in modeling"- I understand both terms "progressive elaboration" and "role wave planning" imply starting from high level and then little by little add details, I also understand they are iterative processes however I do not understand the difference, when use one and when use another term.
tks again and regards from South America, Uruguay

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #614

  • JD Crump, PMP, ITIL-F
  • JD Crump, PMP, ITIL-F's Avatar
Hi Lucia:

Okay, let's try it this way:

Jeff says to Lucia: Lucia, you have been assigned a new project but you wont have a lot of details about what is required because the client hasn't figured them all out yet. How are you going to handle this situation?

Lucia says to Jeff: I am going to use progressive elaboration to learn more about the project in an iterative manner as time goes by.

Jeff says to Lucia: Well, that's sounds great but how do you expect to actually do that?

Lucia says to Jeff: I am going to use a technique called
"rolling wave planning."

Jeff to Lucia: What's that?

Lucia to Jeff: Great question Jeff! How it works is like this: I am going to create my work breakdown structure (WBS) with as much detail as I can get right now and I am going to focus on getting more and more detail over time. I'm going to focus more on getting the detail for the work that is coming up soon and will add the detail for the later activities when they become available in the future.

Jeff to Lucia: That sounds fantastic! You are amazing! Keep up the great work!

:)

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #617

  • Lucia R
  • Lucia R's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 12
  • Karma: 0
I really appreciate your generous reply. Thanks Lucia

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #628

  • Debangshu Ghose
  • Debangshu Ghose's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 11
  • Thank you received: 1
  • Karma: 0
Hi,

Just thought to add my 2 bits to this discussion :-) I'm currently prep'ing to do the PMP first week of Oct 09 and hence am attempting to provide my perspective...

Say, i want to build a car and 10 people in the room decide that it's a good idea and we begin.

Discussion1. How will the car look and drive and what features will it provide the end-user who will buy and use the car, what will we name it, will it be petrol/diesel/water/air driven :-) etc etc...

Discussion2. With details from the first meeting, we begin to elaborate on features and details of stage 2. (This is progressive elaboration at work :-)

"As per PMBOOK pg-7, Progressive elaboration involves continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available."

"Rolling wave planning" is basically to do with the whole "project management plan" depending on various information becoming available over the entire project management life-cycle.....

"As per PMBOK, Pg-46, Significant changes occurring throughout the project life-cycle triggers a need to revisit one or more of the planning processes and, possibly, some of the initiating processes. This progressive detailing of the project management plan is often called "rolling wave planning" indicating that planning and documentation are iterative and ongoing processes.

As per PMBOK, pg - 448, Scope creep: Adding features and functionality (project scope) without addressing the effects on time, cost and resources, or without customer approval. It is similar to "gold plating".

This would be like a team member who is part of this project team adding a GPRS and remote controlled PSP on the dashboard of the car so that the driver can play interactive games while twiddling his fingers on a traffic snarl :-)...... These features we're however not discussed with the client and we're just implemented by the team since they felt that these features would be highly desired on the product....

i hope the above explanation makes sense, request the experts to please correct me if i have made any mistake.

It will also help me clear concepts which i may have missed.

Cheers
Debu
Aspiring PMP, ITIL(F), CEH, ECSA, MCSA (M+S)

Re:Clarification about - Progressive Elaboration 7 years 2 months ago #631

  • Lucia R
  • Lucia R's Avatar
  • Offline
  • Fresh Boarder
  • Posts: 12
  • Karma: 0
This is a very important week for you in which you polish final details for your exam, remember all Cornelius tips for the day of the exam, and I wish you all the best on the 9Th. At this stage what do you think of the saying "plans are useless but planning is indispensable" ? Lucia from Uruguay
Moderators: Yolanda Mabutas, Ahmed Amin, Scott Gillard, Michael DeCicco, Rahul Kakkar, Fernando Jr Sinlao Lim, Mary Kathrine Padua, Chris Preziotti, Lazard Toe, ITBMC, MPM, CIPM, PMP, ITIL, Christian Winter, Kevin Nason, Michael Sumaquial, PMP, Mark Wuenscher, PMP

OSP INTERNATIONAL LLC
OSP INTERNATIONAL LLC
Training for Project Management Professional (PMP)®, PMI Agile Certified Practitioner (PMI-ACP)®, and Certified Associate in Project Management (CAPM)®