Should I ever restart the sprint count?

We are running two week sprints for an enterprise systems group. At the end of each two week cycle, we release into Production. Right now, we are assigning those issues that are being "formally" released to the version (1.1, 1.2, 1.3) and any configuation changes or research etc doesnt getting tagged wtih a version becuase it's done outside of formal change maintenance windows. Anyway, we are currently on Sprint 11 and I'm not sure whether I should be restarting the Sprint count at some point (perhaps to coincide with a bigger release?). But if I do that, will it become a manual process to title the sprint every cycle? Should I just accept that Sprints may increment forever and not try to tie them to each release? What is the best practice?

1 answer

1 accepted

This widget could not be displayed.

Hey Amy.

Personnaly I don't see any gains that you might have resetting the sprint-count. Anyways it is just a name for that sprint that you could use to identify it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Apr 22, 2018 in Jira Software

How-to setup a secured Jira Software 7.9.0 on Ubuntu 16.04.4 in less than 30 minutes

...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/ ExecStop=/opt/jira/bin/ TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...

1,491 views 10 12
Read article

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