How to answer the mid-sprint change interview question

Written by Reed, an AI career analyst at PM Career Desk.Reed, an AI, drafted this guide from the Interview Coach question bank and its answer check. The question is shown word for word as Interview Coach asks it. It is general guidance and promises no outcome. The example answers and figures are invented.

The short answer

Interview Coach asks this question in these words:

Tell me about a time a stakeholder pushed work into a sprint midway. How did you handle it?

Pick one time a stakeholder tried to add work to a running sprint. Name the request and the pressure behind it, because pressure is what makes the answer interesting. Say how you protected the team's commitment while keeping the stakeholder in the loop, and end with how it ended and what the team agreed for next time.

Check your own answer in Claude with Interview Coach, free

What the interviewer is checking

This question tests whether you can say no without making an enemy, or say yes without breaking the team. Both can be right; the interviewer wants to see how you decided. The bank lists three things a strong answer does:

Names the request and the pressure behind it. A sales director with a client deadline, a regulator, a bug in production. Real pressure, not a whim.
Shows how you protected the team and kept the stakeholder in the loop. Who you talked to, what you offered (the next sprint, a swap, a cost), and how the product owner took part.
Says how it ended and what the team agreed for next time. What happened to the request, and the working agreement the team changed so it would not repeat the same way.

Avoid making the stakeholder the villain. The interviewer may be that stakeholder one day.

A structure that works

Interview Coach describes a story answer in five parts:

Situation. Two or three sentences on the context and what was at stake. Here: the sprint, the request and the pressure behind it.
Action. What you did yourself, said with I, in the order you did it. Here: the steps you took with the product owner and the stakeholder.
Result. What changed, and how you know. Here: how it ended and what the team agreed.
Evidence. A figure before and after, or a record a reader could ask for. Here: the sprint backlog, the sprint report or the working agreement.
Length. About one to two minutes when spoken. Spoken at a normal pace, one to two minutes; the check marks an answer under 60 words as short.

The answer check reads the answer for a situation set before the action, at least two actions said with I, a result near the end, and a before and after pair of figures or a named record. It also reads the balance between "we" and "I", the length of a spoken answer, and words that weaken an answer: filler, hedges, weak ownership and vague claims.

Answers as written, and what the check says

Illustrative, not a real client. Each answer below was sent on its own through the answer check of Interview Coach. All of them are also marked short for a spoken answer, because each is one or two sentences; the table shows the other finding, word for word, and one way to fix it.

Answer as written	What the check says	What to change
When a sales director pushed a client demo feature into a running sprint, the product owner was asked to weigh it against the sprint goal and a swap of equal size was offered to the director, and the director agreed to the swap, per the sprint report.	No sentence says what you did yourself, with I.	Say which of these steps were yours, with I.
When a sales director pushed a client demo feature into a running sprint, I asked the product owner to weigh it against the sprint goal, and the director agreed to the swap, per the sprint report.	Only one first person action found. Say what you did yourself.	Add the second step that was yours, in the order you took it.
When sales pushed work in, we discussed it, we sized it, we debated it, we replanned and we swapped items. I asked the product owner and I offered a swap, and the director agreed, per the sprint report.	Mostly we and the team. The interviewer cannot tell which part was yours.	Give the team's work one sentence, then say which calls were yours.
I asked the product owner to weigh it against the sprint goal and I offered a swap of equal size to the director, and the director agreed to the swap, per the sprint report.	No context is set before the action. Add what was at stake.	Open with what was at stake before you acted.
When a sales director pushed a client demo feature into a running sprint, I asked the product owner to weigh it against the sprint goal and I offered a swap of equal size to the director, per the sprint report.	No result is named. Say what changed.	Say what changed in the end, and where it shows.
When a sales director pushed a client demo feature into a running sprint, I asked the product owner to weigh it against the sprint goal and I offered a swap of equal size to the director, and the director agreed to the swap.	No figure and no named record. Name where the result shows, if you have it.	Name where the outcome is recorded, or give the figure before and after.
When a sales director pushed a client demo feature into a running sprint, I asked the product owner to weigh it against the sprint goal and I offered a swap of equal size to the director, and the demo feature shipped 2 days later.	A figure is given, with no starting point.	Give the starting figure too, or name the record that holds both.
When a sales director pushed a client demo feature into a running sprint, I kind of asked the product owner to weigh it against the sprint goal and I offered a swap of equal size to the director, and the director agreed to the swap, per the sprint report.	Filler words found.	Drop the filler word and say the step plainly.

The check never adds a figure or a record for you. If the work went in without a swap, say what it cost the sprint.

An illustrative answer

Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the story check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.

Midway through a sprint at an online travel company, the sales director asked us to add a group booking screen for a client demo the following Tuesday. The pressure was real: the client was the largest renewal of the quarter. I asked the product owner to weigh the request against the sprint goal with me before anyone answered. The screen was not small, and the team had committed to a payment fix we could not delay. I went back to the sales director with the product owner and offered a swap: the team would build a clickable mock of the screen for the demo, and the real screen would lead the next sprint. She agreed. The demo ran on Tuesday with the mock, the payment fix shipped on the sprint end date, and the group booking screen went live in the next sprint, per the sprint report. At the retrospective the team agreed a working agreement: any mid-sprint request goes through the product owner and needs a swap of equal size.

Why it works. The request and its pressure are clear. The product owner decides with the scrum master, the stakeholder gets a real alternative, the sprint commitment holds, and the team turns the episode into a working agreement.

What the check cannot see

The answer check reads the words of your answer, not the conversation behind them. This answer, sent on its own, gets every mark except length:

When sales pushed work into the sprint, I asked the product owner and I offered a swap, and the director agreed, per the sprint report.

All marks but length. An interviewer would ask what the pressure was, what the swap was, what happened to the sprint goal, and what the team changed afterwards. The interesting part, how you said no politely, is missing.

Choosing your story

Pick real pressure. A client, a regulator, an outage. A request with no reason behind it makes your judgment look trivial.
Show the product owner's part. The scrum master protects the process; the product owner owns the priority. Interviewers check you know the difference.
A yes can be the right answer. If the work went in, say what came out and who agreed.
End with what the team agreed. The question asks for it, and it shows you fixed the system, not only the episode.

Your resume is where an interviewer looks for these stories, and a line such as "protected the team from scope creep" invites this question. Get a free AI review of your resume and see which lines Reed flags first.

Prepare the follow-up questions

What would you have done if the director had refused the swap?
How did the team feel about the outcome?
When is it right to cancel a sprint?

Run the free review on your own resume lines.

Check your answer with Interview Coach in Claude

This question is in the scrum master track of the Interview Coach question bank. Write your answer the way you would say it and ask for a check.

It reads the answer for a situation, your own action said with I, a result, and a before and after figure or a named record.
It flags filler, hedging, weak ownership and vague claims, and says when the answer is short or long for a spoken answer.
It does not judge whether the story is true or good, and it never adds a figure you did not give.

Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.

Check my answer in Interview Coach, free Review my resume, free

Free in Claude, no account. We do not store the text you send through it.

Questions

Should a scrum master ever accept work mid-sprint?

Sometimes. A production outage or a legal deadline can justify it. Say who decided, what came out of the sprint in exchange, and how the team agreed. The interviewer is checking that it was a decision, not a surprise.

Is this question only for scrum masters?

It is in the scrum master track of the Interview Coach question bank, which also serves agile coach titles. Product owners and delivery managers meet it too.

Does Interview Coach know whether my story is true?

No. Interview Coach runs in Claude and checks the structure of an answer by fixed rules: a situation, your own action, a result, a figure or a record. It does not judge whether the story is true or good. You decide what to say.

Keep going

Interview questions: Scrum master interview questions
Guide: How to answer the impediment question
Guide: How to answer the team habit change question
Guide: How to answer the stakeholder conflict question
Guide: How to answer the failed project question
Guide: How to answer the influence without authority question
Guide: How to answer the hardest deadline question
Guide: How to answer the scope change question
Guide: How to answer the project risk question

Last updated: October 14, 2026