Back to Scrum Framework

Sprint Goal

5 minutes 5 Questions

The Sprint Goal is a short, concise statement that communicates the purpose of the sprint. It outlines the objectives the Scrum Team wants to achieve by implementing a selection of Product Backlog items during a Sprint. The Sprint Goal is crafted collaboratively by the Scrum Team during Sprint Plan…

Test mode:
Start practice test
Agile Project Management - Sprint Goal Example Questions

Test your knowledge of Sprint Goal

Question 1

A Scrum team has set a Sprint Goal to build a commenting feature into their social media app. Midway in the sprint, they realized the existing database structure might cause performance issues. What should the team do?

Correct Answer: Prioritize a discussion about the database issue in the next Daily Scrum and assess its impact on the Sprint Goal.

When a Scrum team encounters a potential impediment to achieving the Sprint Goal, such as a performance issue due to database structure, the first step should be to discuss the matter as a team, ideally during a Daily Scrum. This promotes transparency and collaborative problem-solving within the team's existing framework without deviating from Scrum principles. Adjusting the Sprint Backlog without the Product Owner's consent, involving higher management without prior team discussion, or prematurely initiating a Sprint Review meeting undermines the self-organizing nature of the Scrum Team and the roles of the Scrum Master and Product Owner in prioritizing and managing the work.

Question 2

During a sprint review, the sales department raises a concern unrelated to the sprint goal. How should the team address this concern?

Correct Answer: Acknowledge the concern, add it to the product backlog, and prioritize it in the future.

The team should acknowledge the concern, add it to the product backlog, and prioritize it in the future. This approach allows teams to be responsive to stakeholder feedback while allowing for proper planning and prioritization.

Question 3

The sprint goal of a Scrum team working on a gaming app is to add a new level to the game. During the sprint, a team member proposes the idea of creating an in-app purchase feature. How should they handle this suggestion?

Correct Answer: Capture the idea for review and stakeholder input during the Sprint Review and for potential inclusion in future sprints.

In Scrum methodology, new requirements or features like an 'in-app purchase feature' are not added in the middle of a sprint because it can diverge the team from their sprint goal, which in this case is to add a new level to the game. Instead, such new ideas should be captured for review and input from stakeholders during the Sprint Review. They can be considered for potential inclusion in future sprints. This maintains the focus on the current sprint goal and also provides an organized approach in handling new ideas or requirements Now, let's think about the other options and why they are incorrect: The option 'Immediately start developing the in-app purchase feature' is not viable because it can disrupt the sprint's focus and lead to an inability to reach the designated sprint goal. 'Tell the team member to stop suggesting ideas that aren't relevant to the Sprint Goal' is not a good practice as it discourages team members from contributing innovative ideas which could potentially add value to the product in the future. Such ideas should be noted and assessed for future inclusion. Lastly, asking the team member to 'work on the new feature in their personal time' is also not correct as it can lead to an unbalanced workload and detracts from the team's collaborative nature.

More Sprint Goal questions
66 questions (total)
Start 66 question test