Skip to main content

Stretch Storries in a Sprint should the be added at the Start or when we know we have capacity

Last post 08:34 am June 12, 2024 by Joeri Mastop
3 replies
11:31 am June 6, 2024


I am new to Scrum and Jira. I work in an organization that wants to maximize capacity 

In order to appease them the Scrum Masters add Stretch Stories to a sprint- i.e. Stories in case we have slack we can then tackle. 


  1. should they be in the backlog and then added to the Sprint when we know definitively, we can address them within the Sprint? or should they be added at the start 

Note if they are added at the Start of the Sprint and we can't achieve it they bugger up the Reporting KPI





07:38 pm June 6, 2024

I work in an organization that wants to maximize capacity 

That's an awful thing to want to do, and no reason at all to use Scrum. It would be smarter to maximize value, which is not the same thing. A  Scrum Master's first duty is not to appease, but to carefully manage people's understanding of such things.

08:45 pm June 6, 2024

This seems to be an output-centric approach. Scrum is an outcome-centered approach. The purpose of Scrum is not to do more work in less time. The purpose of Scrum is to allow the team to maximize the value delivered and quickly adapt and pivot as they and the key stakeholders learn more about what is valuable.

You shouldn't talk about a Sprint and the work in a Sprint without talking about the Product Goal and the Sprint Goal. The primary objective of the Sprint is to achieve the Sprint Goal. However, how the team handles the rest of their capacity to do work once the Sprint Goal is achieved is up to them.

08:34 am June 12, 2024

First of all, previous answers are very important. Focus on value, not troughput. Outcome in stead of output.

When you've managed to get the organisation to appreciate that, if a team runs out of stories in the sprint, and the sprint goal has been achieved or will be achieved, you can let the developers pull more stories into the sprint. They could select the most valuable and manageable stories together with the product owner.

I always recommend to pull in new work if you really need to, in stead of taking on too much work and failing to meet the sprint goal or removing stories from the sprint. It makes the work more transparent, stakeholders have clear expectations and the team is happy. But if your team is self-managing and a little further in their journey, I expect them to get better in estimating how much work they can manage in a sprint, so you probably won't see this happening as much. As a scrummaster, you should facilitate that learning process.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by may have their access revoked at any time, without warning. may, but is not obliged to, monitor submissions.