Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

wrong velocity report

Stéphane October 20, 2021

Hello,
I realized that the last day of sprint, the number of points made on burnup (report) is not the same as in velocity report to closing the sprint. But it should be the same

So I investigated the cause. The Complete Workflow of the US is here this:
Ready for Dev> Dev in Progress> Dev Done> Test OK> Delivery> In Prod

Our sprint is only on steps:
Ready for Dev> Dev in Progress> Dev Done> Test OK

Burn up Report counts as "realized" all the US in "OK test" or more (Delivery and in Prod) (even if they are finally more visible on the Kanban).
But the velocity report , only the US in "OK test" during the closure.
If US are in Delivery or in Prod, they are not considered ok. It is a big problem because the velocity is heavily lowered. In addition, it forces to deliver our US, only after the closing of a sprint, and before the opening of the new sprint. If we do apart from this precise moment one loses all the benefit of our work. And it's not good!

Would it have a workaround?
Can you correct this problem please?

Thank you vry much

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 20, 2021

I suspect your boards are not set up to match your team's process.

Velocity is a measure of completion against commitment, so the estimates going into a sprint get burned-down (or up) when an issue moves from not-done to done.

In a Jira scrum board, the definition of done is "in the right-most column".  So you need to map Test-ok, delivery and in-prod into the last column if you want the burn and velocity reports to report accurately on the sprint.  (Note that the difference between burn-up and velocity is that burn-up is recorded as you go, but the velocity is done dynamically on the current data - this covers cases of re-opening, or when you remove things from a sprint)

Stéphane October 20, 2021

Excellent remark.
Thank you very much.

I did not think about the way. I made the modifications, I will see the next sprint but  I think that will fix the problems.
I had to adapted my filters.

I could also see that the US off sprint continued to be inserted automatically into the current sprint, while they are already in prod.

This new config should I hope corrected the problem.

Thank you

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events