Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Can I track Story Points remaining when an Issue rolls into a new Sprint?

Regarding Issues which will roll into the next Sprint:

The Issue originally had a 5 Story Point value; it rolls over, and in the next Sprint there are only 2 points worth of work remaining.

Is there a good way to track the original 5 SP in (Sprint 1) and the Prorated / Remaining 2 SP (Sprint 2) separately? 

 

2 answers

0 votes

Not without code. 

From Jira's point of view, there's no such "roll over" for the 2 and 3.  If an issue is rolling into the next sprint, then you failed to deliver it.  How far through you are is irrelevant.

For the following Sprint, should the team plan their commitment using the original Story point value/estimate on the "rolled-over story"? Using the above example, would they use the original 5 point estimate or the remaining 2 points? 

You use the full estimate - how far through the story you are is irrelevant.

As Nic has said, JIRA is not designed to support carry-over of issues (and preserve their original SPs).

If the original SP estimate needs to be preserved, I suggest defining a custom metadata field where you can keep track of the initial SP estimate. Of course, doing calculations/reporting with a custom SP field is more difficult than using JIRA's built-in SP field.

Other questions to ask about why issues are being carried over to the next sprint:

- Are the initial SP estimates too large (i.e. should have been broken down further)?

- Are the high SP issues being started too late in the sprint?

- Are issues being (peer) reviewed fast enough (i.e. not sitting and waiting for reviews) so that they can go to test without any unnecessary delay?

- Are developers grabbing all the 'good/fun/interesting issues' at the sprint start and then holding onto them (but not progressing them) until they have time to start them?

- Do testers get to provide their own Test SP estimate which provides additional guidance to Developers about how early an issue (which requires a lot of testing) needs to be started within the sprint?

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

269 views 3 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you