Hint: If you prefer working with Gantt charts, then look at the “Going beyond Agile Boards” article. It explains how to use Sprints and Jira Sprint Goals on Gantt charts with the help of the BigGantt application.
How to write good Jira Sprint Goals?
Every Sprint Goal should be short (ideally, a one or two-sentence statement) and easy to understand. Good Sprint Goals inspire teams and help them self-organize around a single objective.
From a business perspective, Sprint Goals are unique because they depend on the individual business context—Precisely on the Product Goal. Consequently, Sprint Goals represent the next most valuable outcome toward the Product Goal.
So how do you write good goals for your Sprints?
Like any other goal, a Sprint Goal should be SMART (Specific, Measurable, Achievable, Relevant, and Time-bound).
The goal should tell you what is waiting by the end of the road. In other words, it should explain what you are trying to accomplish.
When the Sprint is over, you should be able to measure the results. For that, you may want to define some standards that will let you assess the end product.
Being ambitious is fine as long as the goals you set are realistic. So before your team commits to anything, make sure there is enough time and resources to carry out the work.
Sprint goals and business goals should be hand in hand. The value the goal represents should indicate what positive impact it will cause on the stakeholders, including the users.
Deadlines in Sprint are natural—each Sprint has a clear start and end date. Timelines help teams commit, focus, and work at the same pace.
Sprint Goal examples
What could constitute a Sprint Goal that, on the one hand, is specific enough to let the team understand what they should focus on, and on the other—its value could be measured? Let’s take a look at a few examples:
– An example of a Sprint Goal in a software development context is delivering a feature. The value of new functionality is that it allows users to perform actions that did not exist before the feature release.
- Bad Sprint Goal: “Complete 3 stories from the top of the Sprint Backlog.” — not very specific or measurable. Plus, all 3 stories could lead to different functionalities.
- Good Sprint Goal: “Customers can pay for their flight tickets with PayPal.”
– Agile marketing teams could establish their Sprint Goal to be about risks by addressing an issue, such as broken links, low landing page conversion rate, performance, or security. The value would be an immediate better user experience, more secure data handling, or more customers signing up for a demo webinar.
- Bad Sprint Goal: “Improve the landing page.” — What exactly is wrong with the landing page, and what do you want to do to fix that? Also, how will you tell that your team achieved the goal?
- Good Sprint Goal: “Time to First Byte on the landing page for the ABC campaign is under 0.8s.”