I closed a feature that was a bucket of points (72 points) for un-estimated stories, which then lead to an artificial increase in the team's velocity. The velocity should be 20/25 when now it is 54 points. This feature was not part of the sprint and yet the way JIRA works it does have an impact on the velocity, which does not make sense to me. Does anyone know?
Not sure exactly what you're doing, but for the stories that you did not complete in the sprint, those should have been removed from the sprint. Your sprint burndown should show those story points as having been removed. Or perhaps you no longer required those stories in which case you could set its story points to zero and close them with a resolution of "will not complete" or something...leaving them in the sprint should not count against your velocity.
Try the Great Gadgets add-on for JIRA cloud (https://marketplace.atlassian.com/plugins/com.stonikbyte.great.gadgets.plugin/cloud/overview). It offers gadgets for calculating team velocity and displaying release burndown charts.
See more details here: https://bitbucket.org/StonikByte/great-gadgets-add-on/wiki/Home
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs