[Stakeholders] A stakeholder wants to add scope late in the project. How do you handle it?

Example Answer

I would not react to that with an automatic no, but I also would not treat it like something the team can just absorb without consequences. My first step would be to understand exactly what they want, why it matters now, and whether this is truly a new need or something that should have been surfaced earlier.

Then I would work with the team to understand the impact. What does it change in timeline, effort, testing, dependencies, or delivery confidence? Once that is clear, I would bring the conversation back to tradeoffs. Can we fit it by moving something else? Can we split it into a smaller version? Does it make more sense in a later phase?

For me, the key is that scope changes should be explicit, not silent. Projects get into trouble when extra work comes in informally and everyone acts like nothing changed. A good PM helps people make a real decision instead of letting the project slowly drift.

Common Poor Answer to Avoid

"If it is late in the project, I would tell them it is out of scope and we cannot take it."

Why it's weak

• It sounds disciplined, but it is too rigid and does not show how the candidate handles real business pressure and tradeoffs.

Why this works

• It balances control and flexibility while keeping the project grounded in visible delivery tradeoffs.