nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Velocity for past sprints when story points have only just been added

leewarren

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?

Accepted answers

Alexander Bondarev_x6gjf3

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.

All comments

Vero Rivas

Hi @leewarren

Look at this post

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/

Cheers

Alexander Bondarev_x6gjf3

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.

leewarren

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.

Nic Brough -Adaptavist-

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)

leewarren

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud