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

Velocity calculations

What is the best way to stop (closed) withdrawn tickets being shown in the Velocity calculations, would that be a change to the filter or to remove the done resolution from the status? 

One way is that the Withdrawn tickets are resized to 0 points when they are withdrawn. Removing them from the board would show scope reduction and hides them in a way that could be unhelpful but setting to 0 reflects the reality of there being no work done but that the task is now done so no work still needed.

How do other teams handle this?

2 answers

Thank you.

0 votes

Cancelled/won't do does not need to be treated any differently to any other item that turns out to require less effort than was originally estimated.    If you estimate an issue at 4, but only really end up doing about 2 units of work on it, then how do you handle that?  Why is there any need to treat "estimate 4, did 0 units of work" differently?  You don't change the estimates on issues that do lead to work, so why change them on ones that only require someone to read the item and say "it doesn't need any work"?

Most Scrum teams that take an item into a sprint that turns out to need no work simply mark it done during the sprint.  No need to change scope, same as items that require less work than estimated.

That depends on the reasons for cancelling/withdrawing. There are many reasons why a team may want to withdraw a ticket and not all of them mean that no work will ever be required by any team. It's messy and does not neatly fall into agile ways of working so a blanket answer is not always the best approach. That said if a team is regularly withdrawing a proportion of their tickets each sprint (pulling other stories off the backlog to compensate) then their velocity would be seriously skewed if the points for those withdrawn stories were included. Then when they have a sprint where stories are not withdrawn it would seem like a drop in velocity. If these measures are being used to observe a teams performance then we need to seriously consider these edge cases.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.5.0
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

61 views 1 2
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