Business Analyst
Stakeholder
medium
How do you handle scope creep in a live project?
Asked at
CognizantInfosysTCS
Framework
quantify the cost, force the trade-off
Model answer
Don't fight the request — quantify it. Every new ask gets a written impact analysis (effort, dependency, risk, cost) shared with the sponsor within 24 hours. Sponsors say yes to good ideas until they see the price tag.
What great candidates actually do
- A change request template with fields for impact and trade-off makes the process feel neutral, not obstructionist.
- Track cumulative creep — 5 x 2% changes = a 10% overrun no one signed up for.
- Use a change control board for anything over a threshold.
Traps to avoid
- Naming the solution before the problem — always restate the goal in one sentence first.
- Answering without structure — pick a framework out loud, then execute it.
- Skipping the trade-off — every strong answer names what you would NOT do and why.
Related questions
Requirements
Walk me through the last BRD you wrote — how did you structure it?
Read answer →Requirements
What's the difference between a BRD, FRD and SRS — and when would you use each?
Read answer →Stakeholder
How would you elicit requirements from a senior stakeholder who won't give you time?
Read answer →
Practice with a human
Rehearse this out loud.
Book a 1:1 mock interview. Detailed feedback sheet + scoring on the exact rubric hiring managers use.
Book a mock interview