Should I ever restart the sprint count?

Amy Hogan August 25, 2014

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

0 votes
Answer accepted
Diego Zarpelon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 26, 2014

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