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 for past sprints when story points have only just been added

We finally specified story points for issues that were completed in prior sprints. Unfortunately the velocity chart does not seem to be retroactive.  I can see from the list of issues shown below that it recorded no story points for them and yet, clicking any given issue, the detailed view for it actually shows the story points later added. Is there any way to refresh the velocity chart so that it reflects the newly added story points?

2 answers

1 accepted

1 vote
Answer accepted

Hi, @leewarren !

If I correctly understand your question, it is impossible to re-calculate Velocity Chart. 

Because on "Sprint Start" issues were not be estimated. 

View and understand the velocity chart :

Commitment: The gray bar for each sprint shows the total estimate of all issues in the sprint when it begins. After the sprint has started, any stories added to the sprint, or any changes made to estimates, will not be included in this total. 

OK, thanks. I do find it amusing that even though values are entered for issues, they can't be recalculated; one would assume that velocity charts are newly regenerated each time. And indeed, there are use cases such as "we just decided the original story point estimate was wrong". I'm going to chalk this one up to Atlassian being too busy expanding their empire to concern itself with perfecting what they have. :)

Yep, you're not supposed to rewrite history.  

The correct action here is to simply document that you didn't estimate properly before executing (so people should know ignore the reported velocity, and be reassured that you're doing it better now)

Not a great analogy - history is often rewritten as we achieve a better understanding of it :) That's why we continually groom backlogs, and teams may better grasp their use of story points as a project proceeds. It really ought to be a team decision whether they want to update story points, and thus recalculate velocity. Not permitting this strikes me as against the spirit of agile's continuous learning ethos.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Marketplace Apps & Integrations

Staying organized with Jira: best practices for a better project management

Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...

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