Velocity report: Why completed bar is higher than commited bar

[Daniela Jimenez]

Hello,

I am checking the sprint capacity with the Velocity chart and I see the completed bar is much more higer than the committed one.

Why is so, can you tell me what is wrong?

Thank you

[Fabian Lim · Accepted solution]

Hola Daniela,

Most likely, when you started the sprint the story points were not added to the stories and you added story points while you were working on the sprint. 

The recommendation is to always assign the story points before you start the sprint so that you can have an accurate representation of your velocity in your reports.

Cheers.

[Bill Sheboy]

Hi @Daniela Jimenez -- Welcome to the Atlassian Community!

To check on what Fabian suggests, please review your sprint report.  That will show if:

• there were scope changes during the sprint
• issues were sized/resized during the sprint

Another possible cause to this symptom is starting the sprint prior to adding all of the issues.  This will make the initial "committed" value lower than what you might expect.

Best regards,
Bill

[Daniela Jimenez]

Thanks for you support, In deed I think issues and Us were added after the beginning of the sprint...

Knowing that now what value can I get from this chart?

- interpreting only completed bar?

- compare completed with previous sprints?

-nothing?

[Bill Sheboy]

For this specific sprint with the problem: if you believe completed count is correct, review that with the team to help with future planning...

One value to get from this is to ensure your planning is completed before starting the sprint...including checking the start/end values for the sprint configuration.

[Daniela Jimenez]

Thanks Bill, for sure we need to review thi with the PO

Great community here