Alok PriyadarshiProject Manager| Tata Consulting Engineers LimitedJamshedpur, Jharkhand, India
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. Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
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!!!! Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
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. Saving Changes...
Anton OosthuizenSenior Business Analyst / Project Manager| Self EmployedPretoria, Gauteng, South Africa
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. Saving Changes...
Alok PriyadarshiProject Manager| Tata Consulting Engineers LimitedJamshedpur, Jharkhand, India
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"
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. Saving Changes...
Thomas WalentaGlobal Project Economy ExpertHackenheim, Germany
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. Saving Changes...
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...
