Determining "Complete" states for Velocity view

We have an issue in that our release schedule is not completely linked up with our sprint schedule. We have biweekly sprints and weekly releases, but stories that get to code complete have to go through a week of testing and release to go out. Our definition of done says that you can't close a ticket until it's actually out in production and in use.

This affects the Velocity chart in that it always shows overcommitment as a result.

Let's say the team can do 100 story points a sprint, but at the end of each sprint there's about 30 points of stories that don't close, but slide into the next sprint. But next sprint, they can accomplish another 100 points of work - so the sprint "has" 130 points in it. They complete 100 and slide 30 waiting on release, and then the velocity chart always looks like an overcommitment of 130 and only delivering 100.

The simplest fix for this is to be able to configure a set of ticket statuses that count as done from the velocity chart perspective. We'd basically say that Ready for Release, Resolved, and Closed are the states which would be "done" from a velocity point of view. This would allow us to not improperly close tickets before they are live in production but also not artifically show chronic overcommitment.

Are there any ways people have found to account for this problem, this way or another way?

1 answer

We had a similar problem where we sent development tickets to QA after a sprint was complete. We set the ticket to 'Done' in JIRA agile on Code Complete but that ended up having its own issues for tracking post-sprint.

We are now doing QA within our sprints so that every ticket gets to 'Done' properly by the end of a sprint and it has been MUCH better. Plus we don't have to fight JIRA anymore and we actually have releasable software at the end of a sprint as Scrum would like us to.

Hi David,

We are currenlty having a similar issue where some of our QA work for a release is done after the sprint is complete, did you find a good workaround for this issue?

 

Regards Michael 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,314 views 14 20
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot