Sprint Goal Definition , Who Determines? (making observation between two Scrum Orgs sources.)

Last post 03:49 pm August 5, 2019
by Daniel Wilhite
2 replies
04:00 pm August 4, 2019

In this Scrum ORG Forum , there is information very clear that WHO DEFINES SPRINT GOAL is SCRUM TEAM, but if you read https://www.scrum.org/resources/blog/11-advantages-using-sprint-goal by Barry Overeem, says PRODUCT OWNER and DEV TEAM.


"What is a Sprint Goal?

The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. Sprint goals are the result of a negotiation between the Product Owner and the Development Team. Sprint Goals should be specific and measurable. While the selected work for the Sprint Backlog represents a forecast, the Development Team gives their commitment to achieving the Sprint Goal"

09:48 am August 5, 2019

The only difference between "Development Team + Product Owner" and "Scrum Team" is the Scrum Master.

Minimally, you need a negotiation between the Product Owner and Development Team to develop an appropriate selection of Product Backlog Items for the Sprint and a Sprint Goal. However, the Scrum Master may be involved in a few different capacities, such as facilitating the Sprint Planning or coaching the other participants on good practices for crafting a Sprint Goal or teaching the Product Owner techniques for ordering and Product Backlog.

03:49 pm August 5, 2019

As @Thomas said, there is only 1 role difference.  I will often coach teams, especially ones that are just starting, that by including the Scrum Master in the crafting of the Sprint Goal there is a person involved that is completely removed from the technology or problem.  That allows for one person to sole focus on the team's history in being able to complete stories.  This helps them to ensure that their Sprint Goal is realistic based on their past performance. This practice has helped teams come to realize the difference between their ego and reality. Teams early in formation will often see themselves as being able to do more than they can actually do.  The Scrum Master can often be the voice of reason.

As teams mature the involvement of the Scrum Master starts to diminish. But since the entire Scrum Team is responsible for the value delivered during a Sprint, the Scrum Master should be included in the discussions.