Each Scrum Artifact creates a certain Scrum Team commitment. The Product Goal, Sprint Goal, and Definition of Completion describe the future state of the Product. They are the intentions or commitments of the Scrum Team. However, each Scrum Team commitment covers a different scope and time scale.
Scrum Team Commitment – table of contents:
The Product Goal was not added to the official Scrum Guide until its 2020 version. It is defined there as a Scrum Team commitment to the final shape of the Product. It is made by the Scrum Team and written in the Product Backlog.
The Product Goal thus joined the previously existing Goals in Scrum: The Sprint Goal, which is about the Sprint Backlog, and the Definition of Completion, which is the Scrum Team’s commitment to delivering the Increment according to agreed-upon guidelines.
The creators of Scrum thus decided to make the following connections:
Committing is designed to strengthen the Scrum Team’s focus. It provides the team with a clear goal and horizon for the entire project, one Sprint, and an Increment.
They should all keep in mind the Product Vision and the long-term strategic goal. The Vision is not a commitment of the Scrum Team, but rather the horizon of all its aspirations. It helps in formulating the Goals accordingly. It can be formulated as follows:
Product Vision: To become the world leader in magic commerce and services.
In the text below, examples of sub-goals will refer to this example of the Product Vision.
The Product Goal is a description of the future Product that the Scrum Team is working on from the beginning to the end of the project. The path to achieving the Product Goal is written in the Product Backlog.
A Scrum Team can only do one Product Goal at a time. To change it, the Scrum Team must either complete it or abandon it.
A good formulation of the Product Objective depends on the industry in which the Scrum Team works. But in all cases, the Goal should be compelling, clearly expressed, and relevant. In other words, it should describe the key achievement that brings the Product Vision closer to realization.
It could be, for example:
Product Goal 1: To open the world’s first online store for magic accessories.
Product Goal 2: Create a 24/7 flying broom service.
A Sprint Goal is a description of the work that will be done within a Sprint. It is expressed in the form of a Business Objective to ensure consistency in the work of the Development Team. And also increase Focus – one of the core values of Scrum.
The completion of Product Goal 1 that we proposed above could be broken down into the following Sprint Goals:
Sprint Objective 1.1: Conduct a market survey of magicians for demand for magic accessories
Sprint Objective 1.2: Compile a list of suppliers and product availability
Sprint 1.3 goal: To create a store website
Whereas for Product Goal 2, the Sprint Goals could look like the following:
Sprint Objective 2.1: Find a convenient location for the first service point
Sprint 2.2 goal: Conduct service technician recruitment
Sprint 2.3 goal: Launch a local marketing campaign
Each Sprint Goal is defined and discussed by the Scrum Team during Sprint Planning, which we discuss in detail in this article. A Sprint Planning event cannot be completed without defining the Goal for the next Sprint.
Definition of Completion
The Definition of Completion is another detailed commitment made by the Scrum Team. Unlike Product and Sprint Goals, it is formal by definition.
It usually consists of a list of quality criteria that must be met by the Product for the Increment to be considered finished. Thanks to the Definition of Completion, Scrum Team members and each Stakeholder can easily see what changes and improvements have been made to the Product by a given Increment.
For Sprint Objective 1.1: Survey the mage market for demand for magic accessories, a criterion for the Increment could be: Compile survey results of mages active in the magic forum. The definition for completing this increment could be as follows:
Definition of Incremental Completion 1.1:
- Each of the magicians gave comprehensive answers to the questions
- At least 80% of magicians are active
- The results of the study were entered into a magic bullet database
The definition of completion can also refer to quality standards defined by the organization. Then it is not freely set by the Scrum Team. Its minimum requirements are set by the external requirements of the organization.
However, the Definition of Completion differs from the acceptance criteria we wrote about in the text on User Stories. Referring to the example of Completion Definition 1.1, the acceptance criteria could be formulated as follows:
Acceptance Criterion 1.1:
- Estimate the percentage of magicians who will be willing to use an online store
- Identity which accessories are most popular among them
- Determine what budget your potential customers have
The acceptance criterion, therefore, refers to the performance of the task as it is perceived by the customer.
Scrum Team Commitment – summary
Scrum Team commitments are the Product Goal, Sprint Goal, and Definition of Completion. These enable the Scrum Team to stay focused while working on detailed tasks. They allow the Scrum Team to answer the question of what the key achievement will be from the perspective of the Product Backlog, Sprint Backlog, and Increment.
- Glossary of basic terms, roles and notions
- What is Scrum?
- Scrum values
- How to implement Scrum in your company?
- Scrum Team - what is it and how does it work?
- Who is a Product Owner?
- The most common mistakes of Product Owner
- Who is the Scrum Master?
- Characteristics of a good Scrum Master
- The most common mistakes of Scrum Master
- What statistics and metrics should the Scrum Master track?
- Cooperation between Product Owner and Scrum Master
- Development Team in Scrum
- The most common mistakes of Developers
- Scrum artifacts
- Scaling Scrum
- Sprint Backlog
- What is the Product Backlog?
- What are User Stories?
- Creating the best User Story with INVEST
- The most common User Story mistakes
- User Story Acceptance Criteria
- Estimation and Story Points in Scrum
- Planning Poker
- Team Estimation Game
- Defining Increment
- Scrum events
- What is Sprint in Scrum?
- Scrum Team Commitments - Product Goal, Sprint Goal and Definition of Completion
- What is a Burndown Chart?
- How to create and interpret a burndown chart?
- Advantages and disadvantages of the burndown chart
- Kanban boards in Scrum and Scrumban
- Velocity in Scrum - Speed of the Development Team
- Daily Scrum
- Sprint Planning
- Sprint Review
- What is a Sprint Retrospective?
- Common mistakes during a Sprint Retrospective
- Product Backlog nurturing