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?
Hi Community! I’m Elaine, Confluence Product Manager. You may have read my earlier post about page tree in space navigation sidebar. I'm excited to share another improvement that helps you organize ...
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