How do you coach a dev who skips backlog refinement?

WHAT THIS TESTS: This question tests your leadership and coaching skills, not just your knowledge of Scrum. The interviewer wants to see if you can influence without authority, diagnose the root cause of a problem, and connect process to practical outcomes. They're evaluating your ability to handle interpersonal team dynamics and improve team effectiveness pragmatically, rather than by rigidly enforcing rules.

A GOOD ANSWER COVERS: A strong answer demonstrates a multi-step coaching approach. First, seek to understand by talking to the developer 1:1. Ask open-ended questions to learn their perspective. Are the meetings inefficient? Do they feel intense pressure for code output? Second, connect refinement to their self-interest. Frame it as a way to reduce future pain, like mid-sprint surprises or poorly defined work that requires constant clarification, ultimately enabling more focused coding time. Third, evaluate the process itself. Suggest concrete improvements, like time-boxing the meeting (the Scrum Guide suggests refinement should take no more than 10% of a team's capacity) or requiring a clearer agenda from the Product Owner. Finally, reinforce that backlog health is a shared team responsibility, crucial for predictable sprints.

COMMON WRONG ANSWERS: A common red flag is immediately escalating to the developer's manager, which shows an inability to handle conflict at the team level. Another mistake is being dogmatic, simply stating "The Scrum framework says you have to attend." This approach is alienating and rarely effective. A passive answer, like "I'd just let it go," is also a major red flag, as it demonstrates a lack of ownership. Finally, focusing solely on the individual's behavior without questioning if the refinement meeting itself is flawed shows a lack of critical thinking.

LIKELY FOLLOW-UPS: Be prepared for "What if the developer still refuses after your coaching?" At this point, it becomes a pattern of behavior that impacts the team, and you would need to partner with their manager. Another follow-up is "What if the entire team dislikes refinement?" This indicates a systemic issue, and you should facilitate a team discussion or retrospective to fix the process itself.

ONE CONCRETE EXAMPLE: "A senior dev on my team was skipping refinement, saying it was 'discussion hell.' In our 1:1, I learned they felt our 90-minute sessions were unfocused. I proposed an experiment: we'd time-box it to 50 minutes, and the PO would pre-circulate the top 3 items for asynchronous review. The dev agreed to try it. The focused format worked, they started contributing valuable insights, and our sprint planning became 30% faster because the work was already well-understood."