Skip to main content

Sprint Goal is an Immediate Tactical Goal

January 11, 2021

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.

Topic(s): News and Reviews

Audience: StakeholdersProduct Owners

Subscribe to A Wee Dram! Get all our posts strait to your inbox by subscribing to the latest posts.

Sprint Goal is an Immediate Tactical 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.

A good Product Owner will build features now that your customers 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.

A great Product Owner will anticipate the features that customers need now.

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.

What did you think about this post?