Schedule a Call

Choose a time that works for you.

Loading calendar…

If it does not load, Open Calendly directly.

Quote card for Should Scrum Teams Include a Stretch Goal In Their Sprints?

Should Scrum Teams Include a Stretch Goal In Their Sprints?

There are, of course, a variety of ways to go about planning a sprint. I’ve written previously about velocity-driven sprint planning and capacity-driven sprint planning and my preference. But regardless of which approach a team takes to sprint planning, there is also the question of how full to fill the sprint.

Some teams prefer to leave plenty of excess capacity in each sprint, perhaps so there is time for emergent needs or experimentation. Other teams prefer to fill the sprint to the best of their ability to forecast their capacity.

Still other teams like to take on a “stretch goal” each sprint, which is kind of a product backlog item that is not quite in the sprint, but is one the team hopes to complete if the sprint goes well.

In this post, I’d like to share my thoughts on bringing a stretch goal into a sprint.

This is one of those things that needs to be left entirely up to the team. It should not be up to the ScrumMaster or the product owner, but up to the team. Some teams do extremely well with a stretch goal. Other teams do not.

It really depends on how the team views the stretch goal.

For example, I feel stretch goals are like a crushing weight. I feel like I need to complete them. When I set a goal, I almost always achieve it. I have a hard time distinguishing between what I call a “normal goal” and stretch goal. I don’t think this is good, but it’s who I am. But, I’m not the only one who does this.

If a team included me and perhaps a couple of others like me, we would probably not do well with a stretch goal. The stretch goal would likely be in our minds and possibly even affect our ability to finish all of the main work of the sprint.

Other people--those unlike me--have what I’ll call a more mature attitude toward stretch goals. They can look at it as it’s intended. They can think, “OK, great if we get to it but no big deal if not.” Teams comprising mostly people like that will probably do quite well with a stretch goal.

So: Should your team have a stretch goal in their sprints?

This really has to be up to the team. Unless I’m on the team. Then the answer is no.

Explore Further

Article artwork for The Goal of Sprint Planning.
Article

The Goal of Sprint Planning

Featured

Sprint planning may look like it’s about tasks and estimates but those are not the goal.

Article artwork for Are You Really Doing Scrum? A Practical Scrum Litmus Test.
Article

Are You Really Doing Scrum? A Practical Scrum Litmus Test

Featured

Use a practical litmus test to see whether your Scrum is helping or just wearing the label.

Each team member brings a piece of the sprint puzzle to each daily scrum. By syncing the pieces, the team sees a full picture of how the sprint is going. The daily scrum exists for team members to sync, not to report status to the Scrum Master.
Article

Daily Scrums: Synchronization Meetings, Not Status Meetings

Featured

Turn daily scrums into team synchronization rather than reporting to one person.

Article artwork for Capacity-Driven Sprint Planning.
Article

Capacity-Driven Sprint Planning

Plan sprints around real team capacity instead of relying only on past velocity.

Article artwork for Velocity-Driven Sprint Planning.
Article

Velocity-Driven Sprint Planning

Plan sprints using velocity while understanding its limits.

A man and woman discuss the sprint goal inside open elevator doors. The caption reads, A sprint goal is a one-sentence summary of the focus of a team's sprint. The idea is to be able to relay what the team is working on in the length of an elevator ride.
Article

The Sprint Goal: What It Is and How It Can Help

Sprint goals are something every Scrum team should try to create. Learn what sprint goals are and what a good sprint goal looks like.