Sprint Goal as Commitment in Scrum Sprints
Explains how the Sprint Goal guides Scrum teams by providing a clear, shared objective for each Sprint, ensuring focus, transparency, and alignment …
TL;DR; The Sprint Goal should be a clear, high-level statement that explains the purpose of the Sprint and connects directly to the Product Goal, guiding the team’s immediate tactical efforts. Product Owners should use tools like Lean Canvas to define business objectives and user behaviors, formulating hypotheses with measurable outcomes to maximize value. Focus on solving users’ current problems and iteratively anticipate their needs to drive engagement and deliver impactful features.
In the The Evidence-Based Management Guide we talk about the Intermediate Strategic Goal and I likened that to the Product Goal in the 2020 Scrum Guide . If we also think of each Sprint as a tactical move towards fulfilling that Product Goal then the Sprint Goal becomes an Intermediate Tactical Goal that moves us towards our current Intermediate Strategic Goal.
The Sprint Goal is a Commitment for the Sprint Backlog and should never be “complete those 10 things” but instead should to describe the Why of the Sprint.
Just as the Product Goal provides the current Strategic direction so the Sprint Goal is the smaller step, the implementation step towards it. The Product Owner is accountable for maximizing the value delivered and should be thinking hard, with the help of the Developers, on what the next tactical outcome they want to try and achieve is.
This Sprint Goal should be high level and I would recommend that using a Lean Canvas to help identify not only the business objective but the behaviour that the Product Owner is trying to create in users or other systems. While I favour the Lean UX Canvas, which we teach in the Professional Scrum with UX , there are many valid options out there to use as a complementary practice in this space.
Lean UX Canvas
At a minimum, I would expect a Product Owner to have a hypothesis. A hypothesis is like an assumption, but also with a measure/metric that tells you if you have validated that assumption.
Product Owners are accountable for maximising value and should be looking to not just build features that customers need now, but predict or drive which features that they need now.
We should always be working to engage with our users; users don’t engage when you build a feature that they will need in 6 months. Instead, we should focus on what will solve an immediate business problem for our users. This will engage them in the process and elicit much more excellent feedback from them.
The trick for any Product Owner is to figure out where the market is going and build features that drive it, rather than just following it. Having a vision and entrepreneurially iterating towards that vision empirically with many small hypotheses is key to unlocking this level up of Product Ownership.
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
If you've made it this far, it's worth connecting with our principal consultant and coach, Martin Hinshelwood, for a 30-minute 'ask me anything' call.
We partner with businesses across diverse industries, including finance, insurance, healthcare, pharmaceuticals, technology, engineering, transportation, hospitality, entertainment, legal, government, and military sectors.
ALS Life Sciences
Schlumberger
Trayport
Bistech
Healthgrades
Slaughter and May
Hubtel Ghana
Slicedbread
Lean SA
Akaditi
Flowmaster (a Mentor Graphics Company)
Boxit Document Solutions
Higher Education Statistics Agency
Capita Secure Information Solutions Ltd
Ericson
Milliman
Lockheed Martin
Jack Links
New Hampshire Supreme Court
Department of Work and Pensions (UK)
Washington Department of Transport
Nottingham County Council
Ghana Police Service
Washington Department of Enterprise Services
Philips
Slicedbread
Epic Games
YearUp.org
Kongsberg Maritime
Teleplan