Plan Scope Management - Iterative?

Submitted by santhoshmurali on Mon, 04/07/2014 - 16:18

Managers,

I was reading PMP exam prep, in Plan scope management chapter, it was mentioned that "Scope management plan can be developed in stages, or iterated". Rita gave example as Risk Response Planning triggering the change in Scope management plan. I'm not convinced. Can someone enlighten me with another example?

My understanding is, once we plan how the scope will be managed, monitored and controlled, we already define the ways to handle the changes to the scope. If any changes come in the future it may be to the scope of the project but not the way it is being managed.

If there is any scenario that requires us to change the way how we have defined on how we will manage the scope (scope planning), please let me know.

Thank you,

Santhosh

Forums: 
General Discussion
  • Log in to post comments
  • 284 reads

InduSharmaPMP

Tue, 04/08/2014 - 11:25

Let's take example of a project, where a new product need to be developed. 

Now at the inittial phases of project, the whole scope may not be known as it is a New product and assume that your org and you don't have any experience in developement of this kind of product...in short , no historical data avilable to refer.

In these kind of scenarios, what the PM and team need is Progressive elaboration ... or rolling wave kind of scope planning. It will de defintely iterative and PM will need to look for scope planning again n again. 

But Yes .... I fully agree with the point that for every change in scope once it is baselined need to be done thru Integrated Change Control only 

 

jpawl

Wed, 04/09/2014 - 17:24

Scope Management Plan consists (among others) of specifications how projects deliverables will be formally accepted.

If (for example) acceptation method will change during project - you should change Scope Management Plan (even if scope of deliverable won't change).