Business Analyst interview question
How do you manage changing scope?
Control changing scope through a visible baseline, impact analysis on value, time, cost and risk, an accountable decision maker, recorded decisions, and reprioritization rather than silently adding work.
Direct answer
What a strong answer covers
How it works
Scope changes are normal; unmanaged scope is the problem. The baseline of what is in and out is written down and visible, so a new request is recognised as a change rather than absorbed. Each change gets a short impact analysis on value, schedule, cost, and risk, and goes to a named decision-maker who can trade it against existing commitments. The decision and its reasoning are recorded where the team and stakeholders can see them. Something must come out or the date must move when something goes in; the option that does not exist is doing more with the same capacity and hoping.
Example
Halfway through a portal release the sales team asked for a partner login feature. The impact note showed three weeks of work and a dependency on the identity provider; the product owner chose to add it and drop the reporting export to the next release, and the decision log recorded why. When the export was later asked about, the log answered the question in a minute instead of reopening the debate.
Common mistakes
- Saying yes to every request and delivering everything late.
- Refusing all change and shipping something nobody wants anymore.
- Making trade-offs privately so stakeholders are surprised at the end.
A useful answer structure
Answer from your own work.
Do not memorise a script: use only examples you can explain honestly in follow-up questions.
Open the desktop workspace and rehearse a clear answer in your own words.