How to coach a developer who skips backlog refinement?

WHAT THIS TESTS: This is a behavioral question testing your coaching and influence skills, not just your knowledge of Scrum. The interviewer wants to see if you can move a team member from a "heads-down coding" mindset to a "team ownership" mindset. They are evaluating your ability to diagnose the root cause (is the person overloaded, or do they just not see the value?), influence without authority, and apply systems thinking to improve the team's process as a whole.

A GOOD ANSWER COVERS: A strong answer progresses through four stages. First, seek to understand privately in a 1-on-1; ask open-ended questions to find out why they feel "too busy." Second, coach the individual by connecting refinement to their direct pain points, framing it as an investment to prevent future churn, rework, and interruptions. Third, address the team; use a retrospective to discuss the purpose of refinement and reinforce collective ownership. Fourth, offer to improve the process itself; perhaps the meetings are inefficient and you can suggest ways to make them more focused and effective.

COMMON WRONG ANSWERS: A major red flag is being authoritarian or escalating prematurely. Weak answers include: immediately telling the Scrum Master or manager, which shows you can't handle peer-level issues; simply stating "it's mandatory in Scrum," which ignores the need for buy-in; or focusing only on the individual's "bad behavior" without considering that the refinement meetings themselves might be the problem. Another weak answer is one that lacks empathy and jumps straight to lecturing.

LIKELY FOLLOW-UPS: "What if they listen to you, but their behavior doesn't change?" (This tests your persistence and when you do escalate). "What if the team decides they don't want to do refinement at all?" (This tests how you handle a team wanting to deviate from a core framework practice). "How would you make a refinement meeting more effective?" (This tests your practical process improvement skills).

ONE CONCRETE EXAMPLE: "I'd start by saying, 'Hey, I noticed you've been skipping refinement to focus on coding, and I get the pressure. Can we chat for 15 minutes?' In that chat, I'd connect it to a recent problem: 'Remember last sprint when the API spec for the payments feature was vague and you had to rebuild it? That's the exact kind of thing refinement helps us catch early. It's an investment. The Scrum Guide suggests it should take no more than 10% of our capacity. If it's taking more, or feels useless, let's fix the meeting itself.'"