The Sprint Goal

5 minutes 5 Questions

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It is a commitment by the Development Team about what they aim to achieve during the sprint. It guides the Development Team on why it is building the increment. The Sprint Goal offers a target and purpose, facilitating decision-making and collaboration throughout the sprint. It promotes focus and creativity by providing the team with a target outcome.

Guide: Understanding The Sprint Goal and Preparing for Exam Questions

The Sprint Goal is a concise statement set at the beginning of the Sprint Planning Meeting that defines what the team plans to achieve during that sprint. It provides a clear objective, aligns team’s work towards a common goal and gives flexibility in terms of how to achieve that goal.
Importance: The Sprint Goal is integral to the Scrum framework because:
  • It gives the team a shared objective and keeps everyone focused.
  • It allows some flexibility as it does not dictate the exact tasks, but sets an objective that needs to be fulfilled.
  • It is a key tool for stakeholder communication about what will be achieved in a sprint.
Functioning: During the Sprint Planning Meeting, the Product Owner proposes the objective which forms the upcoming sprint goal. The team discusses and collectively creates a Sprint Backlog that fulfills this goal. As the sprint progresses, the work done should bring the team closer to achieving the proposed goal. At the end of the sprint, the Sprint Review meeting is held to check if the goal was indeed met.
Answering Exam Questions: The Sprint Goal is often a topic in Scrum certification exams. Here are some tips on how to answer such questions:
  • Understand that the Sprint Goal is a common objective and not a list of tasks.
  • Recognize that the goal provides flexibility to the Scrum Team in deciding the best way to achieve it.
  • Be aware that the Sprint Goal can be changed, but it usually requires the Sprint to be cancelled and a new one to be planned.
  • Remember the role of the Product Owner in proposing the objective of the goal.
By understanding these key aspects about the Sprint Goal, you should be better equipped to answer related questions in your exam. Always refer back to this guide, review and have a deep understanding of the concept.
Test mode:
Start practice test

PSM I - The Sprint Goal Example Questions

Test your knowledge of The Sprint Goal

Question 1

During the sprint review, the team was unable to accomplish the sprint goal which was to 'Develop an intuitive search feature'. The product owner is upset and is blaming the team for the failure. How should the Scrum Master handle this situation?

Correct Answer: Encourage the team to reflect on the sprint's challenges during the retrospective and engage in a solution-oriented dialogue with the product owner.

The correct answer emphasizes the importance of a constructive, collaborative approach within the Scrum framework, promoting reflection and dialogue. Imposing stricter deadlines or instructing the development team to work extra hours does not align with Scrum values of self-organization and commitment. Additionally, involving external stakeholders in detailed project failure discussions is not typically within the Scrum Master's role and deviates from focusing on team dynamics and improvements.

Question 2

The Scrum team has set 'Develop a recommendation engine' as the Sprint Goal. During the sprint, the team identifies that the scope of engine development is far larger than anticipated. As a Scrum Master, how should you suggest the team tackle this situation?

Correct Answer: Collaborate with the Product Owner to potentially descope or redefine the Sprint Goal, taking new insights into account.

When a Scrum team realizes that the scope of their Sprint Goal is far larger than anticipated, the best course of action is to collaborate with the Product Owner to review and potentially adjust the scope or redefine the goal based on the new insights gained. This maintains the integrity of the Scrum process and ensures that efforts are focused and aligned with business needs. Allocating a fixed number of hours for tasks does not solve the inherent problem of a too-large scope. Switching methodologies mid-sprint, such as adopting Kanban, does not align with Scrum principles and may cause confusion. Splitting the work into microservices without first re-evaluating the Sprint Goal and scope with the Product Owner may lead to inefficiencies and a loss of focus on the most valuable work.

Question 3

A team member suggests to have two sprint goals instead of one for the upcoming sprint. This is to tackle different features of the application they're developing. As a Scrum Master, what would be your response?

Correct Answer: Explain that keeping a singular sprint goal enhances unity and focus, ensuring the team aligns on the primary objective for the sprint.

The correct answer follows the Scrum principle of maintaining a single sprint goal to preserve coherence and focus within the team's efforts throughout the sprint. The wrong answers, while plausible in certain contexts, stray from the recommendation of the Scrum Guide to keep a unified direction through a singular sprint goal. Dividing the team or considering multiple goals can dilute the team's focus, possibly impacting the sprint's success.

More The Sprint Goal questions
15 questions (total)
Start 15 question test

Other Scrum and Customer-Centric Design concepts

Backlog RefinementBurndown ChartsCustomer-Centric DesignDaily Stand-up MeetingsEmpirical Process ControlIncremental DevelopmentProduct Owner roleScrum Master RoleSprint Review and RetrospectiveThe Scrum FrameworkUser Stories and Acceptance Criteria
All Scrum and Customer-Centric Design questions · PSM I practice test