We have just finished sprint planning and the team has committed to 30 points with a stretch target of 8 points (total 38 points).
Question: should we bring the stretch stories into the current sprint or leave them in the backlog as we don't want the stretch target to impact our burn down chart.
If you don't want them in your burndown, then you should leave them in your backlog. Possibly create a temporary sprint called Stretch which will house this kind of issues during every active sprint. This will also give you the added benefit of showing a scope creep if your employees did manage to outperform their estimation.
Hi Boris - one further question - I have moved those stories out of the current sprint but this has affected my metrics (ie sprint burn down chart). I have already activated the start of the sprint which shows the total points being the committed AND stretch points - is there any way for me (i have admin access) to reset the current sprint so our burndown chart doesn't reflect the stretch stories?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs