Project Management Central

Please login or join to subscribe to this thread

Topics: Change Management, Communications Management
Scope reduction
Network:149



For valid reasons, if PM is proposing cutting scope to be on time in both the cases predictive and adaptive.

Is this change request? How to handle this situation with the stakeholders?
Sort By:
Page: 1 2 next>
Network:402



Any change in scope after freezing the scope base line is considered as change request and one should follow the procedure as per PMBOK involving stakeholders as required.
Network:546



Yes it would be as a change request and could be as option but it should be approval from the client or the sponsor during change request procedures!!!!
Network:1736



Always is a chage request. Mainly when you talk about project scope (product scope is out of project manager accountability) due to it implies change the whole project most of the times.The key reason to create a change request is to evaluate the impacts not the change itself.
Network:964



Agree with the other feedback. People tend to think that a change request represents a negative cost impact but as Alok said, any change should invoke a change request no matter whether it is positive, negative or no cost. A change request is not about the money, it is about the change. Money and time are just consequences of the change.
Network:402



Agree with Anton !!
Network:1276



Milind -

You should go back to the change management plan. If the magnitude or materiality of the scope change is below the threshold established in the CM plan for enacting formal change control, then it would likely just be a communication to all key stakeholders.

Kiron
...
1 reply by Milind Patil
Jan 31, 2019 5:25 AM
Milind Patil
...
Thanks Kiron

Please clear me below point:
"threshold established in the CM plan"
Network:9727



Definitely, it is a change request and as it has to do with the scope and probably deliverables, customers, stakeholders and clients should be consulted.
Network:1863



Agree a reduction in scope requires a change request in the predictive environment. In the adaptive or better Scrum environment, the scope is not frozen or baselined, and a change request is therefor not possible.

If you change schedule (change number of sprints) or cost (change in team composition/size) in a Scrum environment, this might be handled as a change request, if the project procedures even include a change process. Often the PO is in charge of approving such a change.
Network:149



Thank you all
Network:149



Jan 30, 2019 8:03 AM
Replying to Kiron Bondale
...
Milind -

You should go back to the change management plan. If the magnitude or materiality of the scope change is below the threshold established in the CM plan for enacting formal change control, then it would likely just be a communication to all key stakeholders.

Kiron
Thanks Kiron

Please clear me below point:
"threshold established in the CM plan"
...
1 reply by Kiron Bondale
Jan 31, 2019 7:56 AM
Kiron Bondale
...
Sure Milind -

To avoid incurring bureaucratic "waste" and stakeholder irritation, it is a common practice to establish a threshold for different types of changes under which the PM & team have the authority to proceed. Stakeholders should still be notified of the change, but the approval rests within the team. Otherwise, a change which would require $10 extra on a $1M project would cost more to get approved than its actual cost...

Kiron
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

One word sums up probably the responsibility of any vice president, and that one word is 'to be prepared'.

- Dan Quayle

ADVERTISEMENT

Sponsors