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

TOPIC: Scope Creep vs Progressive elaboration

Scope Creep vs Progressive elaboration 7 years 1 week ago #8986

  • Krupa
  • Krupa's Avatar Topic Author
  • Visitor
  • Visitor

I find hard to answer situational questions on Scope Creep, vs Progressive elaboration.
If the Scope Statement is signed off with some open items, and customer says we'll 'clarify' some requirements later after talking to users, but you please proceed with the project since 95% scope is well known and documented.
So we go ahead and baseline this ??
And later during execution when these 'Clarifications' and new work comes in, is it treated as addition in scope and a CR is raised? (which means, budget/etc will be impacted?).
Will this be called Scope creep ? What if customer says - We already told you we will "progressively elaborate'.

My take is - we should document the "unknown" scope in Risk register and have a contingency reserve, so that we can analyze whatever comes in later and use the reserve money. This wont be called as Scope Creep right?

Please reply. (my exam is in day after tomorrow)!

Scope Creep vs Progressive elaboration 7 years 1 week ago #8991

  • Mark Wuenscher, PMP
  • Mark Wuenscher, PMP's Avatar
  • Offline
  • Platinum Boarder
  • Platinum Boarder
  • Posts: 368
  • Karma: 1
  • Thank you received: 64

I see the difference between these two as Scope Creep being uncontrolled and Progressive Elaboration as controlled. I think it would be fine to baseline it based on 95% of the scope depending on the nature of the project and its objectives. Of course, you can never know all of the possible details at the start, and that is why having a good change control process is so critical in order to avoid scope creep. If you are doing progressive elaboration properly and communicating effectively, then it should be clear to all stakeholders if the additional detailing are still within the original scope or if they are expanding the scope to the point of requiring a change request so that things don't get out of control.

If the customer is not totally clear of the product or project specifications, then maybe it is necessary to do prototyping or storyboarding in order to get more early feedback on the requirements. Or, maybe you would need to take more of an Agile approach to the project and develop incrementally, get user feedback, update requirements etc..

Note that "known" risks are assigned a contingency reserve and "unknown" risks are assigned a management reserve.

Hope this helps. Best of luck to you on your exam. Stay confident!


Mark Wuenscher, PMP
Community Moderator

Scope Creep vs Progressive elaboration 7 years 1 week ago #8992

  • Krupa Rao
  • Krupa Rao's Avatar
  • Offline
  • Fresh Boarder
  • Fresh Boarder
  • Posts: 7
  • Thank you received: 7
I See, thanks Mark. Noted.

Oh yes ! We use Management reserve for unknown risks ! Thanks for reminding that. :)
Moderators: Yolanda MabutasMary Kathrine PaduaJohn Paul BugarinHarry ElstonJean KwandaDaniel Soerensen

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