We are going to look at 4 Scrum Sprint Goal Examples and why Sprint Goals matter. Oftentimes Scrum Teams overlook Scrum Sprint Goals.
Sometimes teams will even use the backlog to guide them during sprints. The danger with this is that team members may end up working on separate items that will not connect together in the end.
Scrum Sprint Goal Definition
A sprint goal is an overall objective the development team works towards during each sprint. It is the purpose behind each sprint.
In a way, a scrum sprint goal is a lot like the title of a to-do list. For example, imagine you are planning a party, your sprint goal AKA the list’s title would be,” Plan a Birthday Party for Sarah.”
Hence, the to-do list AKA the sprint backlog would include items like ‘Book a venue’, ‘Send Invitations’, ‘Order a Cake’, ‘Gather Decorations’, etc. These are the items or steps necessary to fulfill your sprint goal.
Importance of Scrum Sprint Goals
Scrum sprint goals clearly define victory and failure to the development team during sprints. You see, without goals, it becomes very hard to stick to a schedule.
Lack of a sprint goal may even result in disconnected and ill-fitting parts of a product. This is why you need sprint goals, to make sure everyone is working hard to contribute to a greater whole.
Additionally, Scrum Sprint Goals provide developers with the focus and direction they need. Instead of each member of the development team working in isolation, sprint goals build cohesiveness and unity of purpose within the development team.
Teams without proper sprint goals will face challenges when implementing Scrum. This is because a sprint goal assigns value to each sprint, without it, the sprint becomes vague and undefined.
How to write Good Scrum Sprint Goals?
A good scrum sprint goal is short, straightforward, and clearly defines the problem being solved.
Sprint Goals should also be brief and easy to understand. They are mainly about why and the results you wish to see.
They are not about how the process is done. They are not a list of backlog items, instead, they are an overarching theme your backlog items will accomplish.
4 Scrum Sprint Goal Examples used in real life
Below is a list of 4 Scrum Sprint Goal Examples used by another scrum team in real life. We will explain each example and try to get a clearer picture of the scrum process. These examples are from another article mentioned below.
Scrum Sprint Goal Example 1: Set up deployment pipeline & release an empty site to production
This is the development team’s first sprint. In this sprint, their goal is to prepare the infrastructure needed for development and creating a foundation upon which they can increment.
Here are some Items on their Sprint Backlog:
- Set up servers for the production environment (including database);
- Set up a build server to build commits, run unit tests and compile deployment packages;
- Set up a distributed service bus (NServiceBus);
- Before deploying to production, automatically back-up the database;
- Set up an empty API that connects to any empty database;
- Before deploying to production, automatically run integration tests on API;
- Create and deploy an empty Angular website that connects with an empty API to show the version of the deployed release;
Scrum Sprint Goal Example 2: Display top-selling products on the homepage
This sprint goal was used by the scrum team in their second sprint. The sprint goal’s guidance during the sprint can be observed by looking at the items on their Sprint Backlog.
Items on the sprint backlog included:
- Create a reusable style guide based on visual design
- Configure Bootstrap for basic styling elements on the homepage
- Implement a page where visitors can view a product’s details
- Test homepage in latest browser versions
Scrum Sprint Goal Example 3: Enable a visitor to order products
This is the goal used by the same team in their product’s third sprint. We can observe the progression of their product towards completion as they move from one sprint to the next.
Their Sprint Backlog included
- Allow customers to pay for their order by credit card (through Stripe);
- Remember failed payments in an audit log so we can track potential abuse;
- When a user purchases a product, record their license in a separate service;
- Encrypt user-sensitive information in order (e.g. email, address);
These backlog items are clear steps towards enabling visitors to order products safely and securely with their product.
Scrum Sprint Goal Example 4: Extend product catalog to more products
This the scrum team’s sprint goal for the 4th sprint. The product is progressing and it’s now ready for expansion. The sprints are ongoing increments towards a functioning product.
Fourth Sprint Backlog Items:
- Gather product information about our full range (pictures and descriptions);
- Allow visitors to search the catalog by keyword and type of product;
- Present only 10 products at a time, allowing visitors to navigate back and forth between pages;
- Extend the number of pictures to be shown per product to 10 (instead of three);
Signs of Good Scrum Sprint Goals.
How do you know if you have good Spring Goals? There is a simple method to check the quality of your goals. All you need is a list of all your previous Sprint Goals.
A good list should allow a bystander to easily follow and understand the development process of your product. Conversely, a bad list leaves everyone scratching their heads.