I include issues after starting a sprint.
I added issues after starting a sprint, accidentally.
This meant that the "speed graph" only showed what was "performed".
How could I include the commitment in this graph?
2 answers
1 accepted
Hi @Rodrigo Coutinho ,
Unfortunately, there is no way to do that. The native version of the Velocity Chart is quite limited. The only workaround is to delete the sprint and create a new one.
If you use the app I have developed - Multi-team Scrum Metrics & Retrospective, you could just use the Final Scope metric instead of the Initial Metric, or even write your own metric using JQL and compare against it without limitation. It also provides a lot of other features. However, if you need to solve only this narrow case, a paid solution would be overkill for you, I think.
Best regards,
Alexey
The Jira Velocity report only displays the commitment at the start of the sprint. So it will not reflect the commitment if you added stories right after the sprint start.
An option, other than re-creating the sprint, would be to search on Atlassian Marketplace for an app that is able to display the final sprint commitment (including scope changes).
If you consider the idea of using an app, our Great Gadgets app offers a Team Velocity gadget that can display both the Initial Scope (work committed before sprint start) and the Final Scope (commitment after scope changes) along with Completed and other metrics.
Danut
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.