How do you help establish a Sprint Goal?

WHAT THIS TESTS: This question assesses your sense of ownership and your role as a collaborative partner in delivering value. Interviewers want to see if you understand that the Sprint Goal is the 'why' behind the work, providing focus and flexibility. They are testing your ability to facilitate a productive outcome in a common, imperfect scenario, rather than just taking tickets or policing the process.

A GOOD ANSWER COVERS: A strong answer shows you guiding the conversation toward a goal. First, acknowledge the PO's priorities to build alignment. Second, ask probing, open-ended questions like, 'What is the single most important outcome we want for our users this Sprint?' or 'What theme connects these high-priority items?'. Third, based on the answers, synthesize and propose a concise, value-oriented goal. Fourth, invite the rest of the team to refine and commit to the proposed goal, reinforcing that it's a team effort.

COMMON WRONG ANSWERS: A major red flag is passivity ('It's the PO's job, I'll just start estimating tickets'). This shows a lack of ownership. Another is rigidity ('As per the Scrum Guide, we cannot proceed without a goal'). This demonstrates poor collaboration skills and an inability to handle real-world ambiguity. Finally, avoid dictating the goal yourself; your role is to facilitate its creation, not to usurp the Product Owner's accountability for maximizing value.

LIKELY FOLLOW-UPS: Be ready for 'What if the items are truly unrelated?'. A good response is to discuss pragmatism. You might suggest a smaller, more focused Sprint, pulling in only related items to create a cohesive goal. Alternatively, you could explicitly frame it as an exception, with a goal like, 'Pay down critical tech debt and resolve three P1 customer-reported bugs,' and then flag the pattern for discussion in the Sprint Retrospective to prevent it from becoming the norm.

ONE CONCRETE EXAMPLE: Imagine the PO brings five tickets for a 2-week sprint: update login API, add 2FA, fix a password reset bug, update the user profile UI, and add avatar uploads. A senior developer could observe, 'These items all seem to revolve around the user's identity and security. Could we set a Sprint Goal like, 'Strengthen user account security and enrich profile management'?'. This provides a clear purpose. If a new, unrelated task appears mid-sprint, the team can use this goal to decide whether to include it, protecting their focus.