How Would You Handle Scope Creep When Dealing with Multiple Stakeholders?

To handle scope creep, you should take the contract/initial plan as a base. Everything that doesn't exist in the contract/initial plan should be taken as additional work that includes extra cost and extra time or extra resources. The additional things required should be evaluated and approved through a change control process.

Scope creep prevention with multiple stakeholders should be addressed the same was you do for projects with just one stakeholder: a strictly enforced change management process.

Having good relationships with stakeholders is a benefit but to protect all parties including yourself you should have a strong and effective change management process that is agreed by all key stakeholders when project kick-off. All changes to requirement baseline should be assessed openly, tranparently and fairly. Remember that we can never satisfy all stakeholders but they have to accept willingly to exchange something for their additional features

From a practical perspective it's better if you identify since the beginning of your project/product what does VALUE mean. And from there define a vision that is aligned to the organizational strategy and your customers' key objectives. From there you can groom or categorize the requests that you are getting from different stakeholders.

Additionally, I would strongly recommend to include the technical team in the prioritization, let them understand the requirements and make comments to know if it's feasible and to measure the efforts and resources needed to get all of the requests implemented.

First of all, it is necessary to have a clear project governance in place, where each participant understands the boundaries of their role. There should be a centralized communication channel and authority to address and validatie any backlog-related items (in-scope) and change requests/out-of-scope items.
Secondly, during project initiation clear scope, time and budgetary boundaries should be established. During planning and execution, scope items are getting refined, validated and prioritised (Must, Could, Should, Wouldn't) with the responsible stakeholder (e.g., product owner) based on the balance of time and budget.

Simple: taking a project change management process defined and putting it clear for all people involved from the very begining.

Hi Pavan,

from my point of view, a change log in combination with an approved project charter is key to maintaining a scope and avoid scope creep.

Q. "How would you handle scope creep "

A. In the contract for services.

e.g., Specify that, based on the total value of the contract, the clients request for addl. services will be accepted as a verbal order and confirmed in writing when value less than 15% of total price of contract.

Any request over that amount requires a sit-down contract negotiation.
Cheers,
Bill