Are deployed issues counted as completed, thereby skewing the velocity for a sprint?

In JIRA, my team's velocity does not match what I'm seeing my team do. Specifically, the completed work is quite low while the committed work is quite high. Could this be due to deployed issues? Are those issues not counting as completed, thereby skewing the velocity? I'm also confused by what I'm seeing as committed issues. The report is showing a commitment amount nearly three times higher that what we agreed on in our sprint planning session.

1 answer

This widget could not be displayed.

Depends on how your board is configured. Irrespective of individual statuses, report counts the issues in the far right column, on the board, as completed. You can have one or more statuses mapped to this column.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Tuesday in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

137 views 1 3
Join discussion

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you