How would you address a teammate working on misaligned low-priority tasks?

WHAT THIS TESTS: This tests whether you treat the Daily Scrum as one of the five events that provide cadence for inspection and adaptation, and whether you see the Scrum Team as accountable for progress toward agreed goals. The interviewer wants to know if you will detect variance empirically and self-manage, or if you will default to hierarchy.

A GOOD ANSWER COVERS: A good answer hits four things in order. First, use the Daily Scrum exactly as intended: inspect progress toward agreed goals and detect undesirable variances. Raise the observation with the teammate during that event, focusing on the work and its alignment with the goals rather than personal criticism. Second, inspect together whether the low-priority task endangers the Increment of value the Scrum Team is expected to produce during the Sprint. Third, adapt as peers. Since the Scrum Team turns a selection of the work into an Increment, the team can re-prioritize or reassign the work itself. Fourth, involve the Scrum Master only if the environment prevents the team from adjusting. The Scrum Master is there to foster an environment where the team can resolve such issues, not to assign tasks.

COMMON WRONG ANSWERS: The biggest red flag is bypassing the team to tell the Product Owner or a manager first. The Product Owner orders the Product Backlog, but during the Sprint the team should inspect and adapt together before escalating. Another red flag is doing nothing because it is not your role. Scrum engages groups of people who collectively have all the skills and expertise to do the work, so every member shares accountability. A third red flag is ordering the teammate to stop. That ignores the empirical approach; the response should be inspection and collaborative adaptation, not command and control.

LIKELY FOLLOW-UPS: The interviewer may ask what you would do if the teammate refuses to change course. In that case, the deviation is an impediment to the team's ability to deliver the Increment, and the Scrum Master should foster an environment where the conflict can be resolved. They may also ask how you would prevent this from happening again. You could note that the team should ensure transparency so that progress is visible, which enables inspection. They might ask whether the Product Owner should reorder the backlog mid-Sprint. You should clarify that the Product Owner orders the Product Backlog, but the team selects the work for the Sprint and manages the plan.

ONE CONCRETE EXAMPLE: You might say: During the Daily Scrum I would ask the teammate how their current task supports the agreed goals for this Sprint. If it does not, I would point out that we have a variance that threatens our Increment. I would suggest we adapt by pausing that task and pulling in the higher-priority item we already selected for this Sprint. If the teammate insists the low-priority task is critical, we would inspect why it was not visible earlier and whether our current management of the backlog needs adjustment. Should the team be unable to agree, I would ask the Scrum Master to help foster an environment where we can resolve the disagreement without breaking our cadence.