They can either stick to the agreed scope baseline they (should) have signed up to, which means don't include it, or they (the Change Control Board) can approve a change request for the new requirement. As long as the scope and requirements plan was agreed to, and the change control process was also agreed to, then just communicate this calmly to the demanding stakeholder. Saving Changes...
Eric SimmsSenior Program ManagerBaltimore, Maryland, United States
Stakeholders who change requirements on the fly often believe they can do so without incurring any impact to the project. You should calculate the impact of the changes the stakeholder wants before implementing them, then get the stakeholder to agree to the changes in writing. Saving Changes...
Senior Projects Manager | Field & Marten AssociatesNew Westminster, British Columbia, Canada
I fully agree with my fellow colleagues. Sometimes you encounter those issues so the best thing is to evaluate the impact and put it on the table for approval.
There should be a control board who assess and evaluate changes. Saving Changes...
Anonymous
Please elaborate on your question
For example, who are these stakeholders? Are they the customer and are paying for the change or someone else?
Are you working under contract? What does the contract say?
Do you have a change control system? Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
All changes are welcome if and only if everybody in the project are aware the change control process and about they are the owner of changes. In other words, change has an associated cost and stakeholders must afford it. First thing to do before starting is put clear it. Saving Changes...
Make sure the stakeholder is aware of the impact of changes, get it written, put through change control process and implement if approved. Saving Changes...
It has all to do with the situation. You need to consider his power and level of influence on the project. However, communication helps most of times. You need to communicate the values of the project and consequences of any changes. Saving Changes...
Mansoor MustafaSenior PM| Government DepartmentRawalpindi Punjab, Pakistan
My point of view, involve him as early as possible and ask to forward his requirement in written form( So that he cannot change later), evaluate the impact and process through CCB. Saving Changes...
Change is ok and welcome but must be put into a structured framework. It is always bad, if a team gets confronted continously with change request like, "lets do it just now" or stakeholders try to squeeze it in using direct and control behaviors. Try to agree on time-boxed iterations that are change-locked in order to keep the team focused on work without interference. Put a CR process in place that embraces change, but in a way the team can manage and digest in a proper way. Saving Changes...
Community Champion
