Adapting to Changed Requirements
How to tell a story about requirements changing mid-project: spotting the change early, weighing it on the facts, keeping what still works and being open about the cost.
Overview
Requirements change on almost every project. Customers react differently than expected, a competitor ships something, a regulation changes, or a test shows the first idea was wrong. Interviewers ask about this to see how you respond: do you adapt calmly and on the facts, or do you defend the old plan because of the work already done?
That last trap has a name. The sunk-cost fallacy is continuing with a plan because of what you have already spent on it, rather than because it is still the best way forward. A strong answer shows you judged the new plan on what it would cost and deliver from today, kept whatever work still applied, and told the people affected what the change would cost them.
The interviewer also wants to know that you can tell the difference between a small refinement and a real change of direction, and that you do not quietly absorb big changes and hope to make up the time.
- Detection — Noticed early and raised it — Found out at the deadline
- Judgment — Compared options on cost from today — Kept going because of work already done
- Salvage — Kept the parts that still applied — Threw everything away, or kept everything
- Communication — Told stakeholders the cost in time or scope — Absorbed it silently
- Attitude — Calm; the change is part of the job — Frustrated or blaming
What you will be able to do
- Tell a change story that shows early detection and a decision based on facts.
- Explain how you sized the change and who you told.
- Show which work you kept and which you dropped, and why.
- Describe the habits that make later changes cheaper.
Interview questions
- Tell me about a time requirements changed mid-project.
- How do you handle scope creep?
- Describe a time you had to change your approach because of new information.
- How do you design or plan so that changes hurt less?
- Tell me about a time a change in requirements improved the outcome.
Sign up free to read the full topic
More Behavioral topics
Start free on Cariara · Coding problems · System design studio