What is a Sprint Goal and how does it influence planning?

WHAT THIS TESTS: This question tests whether you understand the purpose of Scrum ceremonies beyond rote memorization. It's not about defining a term. It's about demonstrating you know how to use the Sprint Goal to focus a team on delivering a coherent, valuable increment of work, rather than just a random assortment of completed tickets. It separates candidates who see Scrum as a process from those who see it as a framework for delivering value.

A GOOD ANSWER COVERS: An ideal answer touches on four key points. First, define the Sprint Goal as a single, high-level, valuable objective for the Sprint, collaboratively created by the Scrum Team. Second, explain its role in Sprint Planning: the team selects Product Backlog Items that are necessary to achieve this goal, not just to fill capacity. Third, emphasize that it provides flexibility; the goal is fixed, but the plan (the Sprint Backlog) can adapt as the team learns more. Fourth, it fosters collaboration by giving the Developers a shared objective to rally around.

COMMON WRONG ANSWERS: A major red flag is confusing the Sprint Goal with the Sprint Backlog. Candidates often say, "The Sprint Goal is to complete all the tickets we pulled into the sprint." This is fundamentally wrong and shows a task-based mindset, not an outcome-oriented one. Another red flag is describing the goal as an afterthought, something written down after the team has already picked all the work they want to do. Finally, watch out for goals that are just a list of tasks, like "Upgrade the database and fix three bugs."

LIKELY FOLLOW-UPS: Expect to be asked for a real-world example. "Tell me about a Sprint Goal from a recent project. Why was it a good (or bad) goal?" You might also be asked, "What happens if, mid-sprint, you realize the Sprint Goal is unachievable?" or "Who is responsible for crafting the Sprint Goal?" (Answer: The whole Scrum Team).

ONE CONCRETE EXAMPLE: A weak Sprint Goal is a to-do list: "Implement the new login API, write unit tests, and deploy to staging." A strong Sprint Goal is an outcome: "Enable users to log in with their Google account via a single click, reducing login friction and supporting our Q3 user activation target." This goal is valuable, measurable, and provides clear direction while giving the team autonomy on the specific implementation.