How to answer the team habit change interview question
The short answer
Interview Coach asks this question in these words:
Tell me about a team habit you helped change. How did you know it had changed?
Pick one habit of a team you coached: stand-ups that ran long, stories that were too big, retrospectives that changed nothing. Describe the habit before with one concrete example. Then show how you coached the change instead of ordering it, and end with the sign or measure that showed it had changed, from the team board, the sprint report or the retro notes.
Check your own answer in Claude with Interview Coach, free
What the interviewer is checking
The question is about coaching, so the interviewer listens for questions you asked and experiments the team chose, not rules you set. The bank lists three things a strong answer does:
- Describes the habit before, with a concrete example. Not "communication was poor". "Every story over eight points spilled into the next sprint, three sprints running."
- Shows how you coached the change rather than ordered it. A question in a retrospective, an experiment the team picked, data you showed them. The team made the change.
- Names the sign or measure that showed the change. Spillover, cycle time, retro actions closed. A figure from the board, or a record the team kept.
"Helped change" is the interviewer's phrase. In your answer, say what you did and what the team did, separately.
A structure that works
Interview Coach describes a change answer in three parts:
- Starting state. How the work was done before. Here: the habit and one example of it.
- Adoption. Who had to change and how you handled pushback. Here: who had to change, and how you coached rather than ordered.
- Effect. What changed afterwards, and where that shows. Here: the sign that it changed, from a record.
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 stories kept spilling into the next sprint, the spillover was put on the board and the developers were asked to pick a size limit, and the developers adopted a size limit, per the sprint report. | No sentence says what you did yourself, with I. | Say which of these steps were yours, with I. |
| When stories kept spilling into the next sprint, I put the spillover on the team board, and the developers adopted a size limit, 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 stories spilled over, we sized stories, we split work, we tested limits, we reviewed spillover and we adjusted plans. I put up the data and I asked a question, and the team adopted a limit, 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 put the spillover on the team board and I asked the team to pick a size limit, and the developers adopted a size limit, 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 stories kept spilling into the next sprint, I put the spillover on the team board and I asked the team to pick a size limit, per the sprint report. | No result is named. Say what changed. | Say what changed in the end, and where it shows. |
| When stories kept spilling into the next sprint, I put the spillover on the team board and I asked the team to pick a size limit, and the developers adopted a size limit. | 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 stories kept spilling into the next sprint, I put the spillover on the team board and I asked the team to pick a size limit, and spillover dropped to 5 percent. | A figure is given, with no starting point. | Give the starting figure too, or name the record that holds both. |
| When stories kept spilling into the next sprint, I basically put the spillover on the team board and I asked the team to pick a size limit, and the developers adopted a size limit, 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 habit came back, say what you did then.
An illustrative answer
Illustrative, not a real client. Every figure is invented. This answer gets all nine marks of the change check: length, situation, own action, team versus me, result, evidence, and no vague words, filler or hedges.
When I joined a claims processing team as scrum master, stories spilled into the next sprint every time: sprint after sprint, a large share of the committed points did not finish. Nobody had looked at why. In the next retrospective I put the spillover on the board without comment and I asked the team what the unfinished stories had in common. The developers saw it first: every one was among the largest on the board. I asked them to choose an experiment, and they chose to split any large story before planning, as a trial. I kept the board and the counts; the team ran the splitting. Over the next sprints spillover fell from 33 percent of committed points to 6 percent, per the sprint report, and the team kept the rule in its working agreement. Since then I start with the data and a question rather than a fix.
Why it works. The habit is concrete and measured. The scrum master shows data and asks; the team finds the cause and picks the experiment. The change has a before and after figure from a named report and lasts in the working agreement.
What the check cannot see
The answer check reads the words of your answer, not the team behind them. This answer, sent on its own, gets every mark except length:
When stories spilled over, I put up the data and I asked a question, and the team adopted a limit, per the sprint report.
It passes every mark but length. An interviewer would ask: what habit, what did the data show, what experiment did the team choose, and did it last? Coaching lives in those details.
Choosing your story
- Pick a habit, not a crisis. The question is about how teams work every day.
- Show the team choosing. If you set a rule, the story is about authority, not coaching.
- Pick one with a measure. Spillover, cycle time, retro actions. A sign the team itself would recognize.
- Say if it lasted. A habit that changed for one sprint did not change.
Your resume is where an interviewer looks for these stories, and a line such as "coached teams in agile practices" 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 team had not seen the pattern?
- Which habit did you fail to change?
- How do you know when to stop coaching and just decide?
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.
Free in Claude, no account. We do not store the text you send through it.
Questions
What if the change came from management, not the team?
Then tell the coaching part: how you helped the team adopt it rather than resent it. The question is about the coach's method.
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.
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 mid-sprint 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