Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Should (do you) add stretch objectives in JIRA sprints?


Some of our teams use stretch objectives in their sprints and some not. My question is for the teams that do use stretch objectives in their sprints, in JIRA (this is important).

They do the following:

- the stretch items are either taken from the next sprint, or they are taken from a sprint that's never actually started, called "Extra". The team knows that if they finish the items in the current sprint, they can take anything from the "extra" sprint. So "extra" is just a prioritized backlog.

So the sprint is not finished, but the initially planned items are (I assume stretch objectives are not added initially in the sprint, because if they will not be finished the burn-down chart would look horribly).  Now the team takes something from either the next sprint, or the extra sprint.

What happens when they can't actually finish this new item? In JIRA, since it's added to the sprint, it modifies the chart, and at the end, the statistic is affected negatively.

How do you handle (or propose to handle) such cases? 

Thank you!




Log in or Sign up to comment