If the Velocity chart reflects completed hours exceeding committed hours, does this mean the sprint was seen as a failure or not performing well.
please let me know, we use JIRA and Confluence and I need to provide feedback on the sprint velocity.
It's neither good nor bad for the sprint performance really.
You need to look at the magnitude and frequency. Was it a few points either side of the committent? Small variations are perfectly normal, but if it's over 10% of the committment, you might have soemthing wrong. The frequency matters too - if it happens on the odd sprint randomly, it's natural variation. If it happens every sprint, you have a problem.
However, over-delivering is usually not a working problem, most of us see it as an issue with estimates - "we need to get better at estimating what we can get done in a sprint".
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot