What happens when a sprint goal starts to push the boundaries, or when does a sprint goal become a ‘stretch goal’?
This is a critical question for scrum masters, teams, and organisations committed to achieving high performance without overburdening their teams.
Sprint goals are a crucial part of the scrum framework, providing teams with a clear focus and direction for each sprint.
But to help your team strike a balance between ambition and feasibility, you need to understand the difference between a standard sprint and stretch goals.
That’s the purpose of this post. You will also learn why stretch goals are important and how to manage them.
What is a sprint goal?
At its core, a sprint goal defines the purpose of a sprint. It represents the primary objective the team aims to accomplish during that iteration.
The goal provides focus and alignment, ensuring that every task in the sprint backlog directly contributes to achieving that outcome.
But sometimes, teams aim for more. That’s when a stretch goal comes into play.
What is a stretch goal in scrum?
A stretch goal goes beyond the standard sprint goal, encouraging the team to push themselves further.
It’s an additional target that, while desirable, is not necessarily expected to be completed within the sprint.
Essentially, stretch goals inspire teams to go above and beyond but remain optional.
Think of a stretch goal as a “nice-to-have” rather than a “must-have.”
It is an aspirational target that the team would love to achieve if everything goes smoothly, but it won’t derail the sprint if it’s not met.
When does a sprint goal become a stretch goal?
A sprint goal can become a stretch goal under several circumstances. Here are some scenarios to watch for:
1. When the scope expands significantly
Has your sprint goal grown beyond its initial scope?
Teams often try to accommodate new requirements, features, or technical complexities during sprint planning.
If these additional items threaten to overwhelm the team’s capacity, what was once a straightforward goal can evolve into a stretch goal.
Rather than abandoning these new items, teams might categorise them as stretch goals.
By doing so, they can prioritise the most critical work while leaving room for extra accomplishments, should time permit.
2. When there’s a desire for innovation
Is your team experimenting with a new technology or feature?
Teams may want to explore innovative solutions or take on extra challenges that go beyond the core sprint goal.
In these cases, the team might define an ambitious stretch goal to try something new.
While innovation is vital, teams need to ensure that this stretch goal doesn’t detract from the primary sprint goal.
If it becomes too complex, it risks overloading the sprint and diluting focus.
3. When stakeholders have additional expectations
Are stakeholders hoping for more than what’s initially planned?
Product owners or other stakeholders may push for additional deliverables within the same sprint.
If the team cannot realistically commit to these extra requests, a stretch goal may serve as a compromise.
This way, stakeholders feel heard, while the team remains focused on their original goal.
By clearly defining the extra work as a stretch goal, teams manage expectations while still demonstrating their willingness to exceed stakeholder demands if feasible.
4. When team capacity is uncertain
If your team’s availability fluctuates, stretch goals might be the key.
Teams may face varying levels of capacity due to holidays, illness, or resource constraints.
If the team is uncertain about its ability to complete the full sprint goal, portions of the work can be labelled as stretch goals.
This allows the team to commit confidently to the core sprint goal while acknowledging potential capacity shortfalls.
If everything goes according to plan, they’ll have the opportunity to tackle the stretch goal.
5. When agile maturity drives ambition
Is your team more experienced and eager to take on more challenging objectives?
High-performing, agile-mature teams often embrace stretch goals.
With greater experience and efficiency, they can handle more complex tasks, using stretch goals to fuel their continuous improvement and mastery.
Mature teams understand that not achieving a stretch goal is acceptable, as long as they’ve met the core sprint goal.
This mindset keeps the team motivated while preventing burnout.
Why use stretch goals in scrum?
While they’re not always necessary, stretch goals offer several benefits when used correctly. Such as:
1. Boosting motivation
Teams often feel energized by the prospect of achieving something extraordinary. Stretch goals provide that extra spark.
2. Driving innovation
Stretch goals encourage teams to step outside their comfort zones and try new approaches, promoting creative problem-solving.
3. Maximising capacity
Teams with greater efficiency or capacity can use stretch goals to ensure they’re fully utilising their abilities without overcommitting.
When can stretch goals backfire?
Not all stretch goals are beneficial. If misused, they can lead to unintended consequences.
1. Risk of burnout
Overloading the team with unrealistic expectations can cause burnout, especially if stretch goals are consistently presented as mandatory rather than optional.
2. Distraction from core goals
If a stretch goal takes priority over the sprint goal, the team’s focus can suffer. The primary objective should never be neglected for the sake of additional, uncommitted tasks.
3. Lower morale
Failure to meet stretch goals repeatedly can demoralise teams.
If stretch goals feel out of reach or unachievable, they can create a sense of failure, even if the core sprint goal is accomplished.
Best practices for managing stretch goals
To avoid the pitfalls of stretch goals, it’s essential to manage them effectively. Here are some best practices:
1. Set realistic expectations
Ensure that the team understands the optional nature of stretch goals. They should inspire, not pressure.
2. Prioritise core goals
Always keep the sprint goal as the top priority. The stretch goal is secondary and should never jeopardise the primary objective.
3. Celebrate all wins
Whether the team completes the sprint goal or both the goal and the stretch goal, celebrate the achievement.
Acknowledging the team’s hard work maintains motivation.
From sprint to stretch: When goals go too far
This usually happens when ambition pushes the team to explore additional possibilities while keeping the core objective within reach.
Sprint goals and stretch goals both play vital roles in a team’s success. But, understanding the distinction ensures that teams remain focused, efficient, and motivated.
By managing stretch goals properly, scrum masters can empower their teams to strive for excellence without sacrificing balance.
As your team grows in its agile journey, knowing when to push for that extra mile can make all the difference between good and great performance.
You should also learn about the pros and cons of having multiple sprint goals.
I hope you found this post helpful.
