We run company-wide sprints here using Scumban-ish with 1 week long sprints.
Sprint changeover for us is during the Wednesday working day.
Who out there does fortnight or 4-weekly sprints?
Does anyone have the sprint changeover process automated?
What are your cons and pros for shorter or longer sprints?
One week sprints does make it easier to 'course correct'.
We usually keep to two-week sprints but! The idea is to not keep or have kick-offs at the start of working weeks.
Following our Mon-Fri week withholding flexible work, springs are started on Wednesday. I've considered moving us to one week but we end up having our velocity drop off over time and there's is slightly more management involved where otherwise we'd be pretty lassiez-faire.
Our Sprints are also two weeks and run Wednesday to Wednesday. We make a morning out of of our ceremonies (Review/Retro/Planning) and head directly into the next Sprint. This has worked really well for us, and the team is accountable in DSU for starting and completing tasks from the get go. We schedule backlog refinement during the off week, so the team is thinking about and planning work that may need to feed into the next increment.
We found one week to be too much overhead for planning, and anything longer than that limits our quick release to the customers.
Recommended Learning For You
Level up your skills with Atlassian learning
Jira Align Program Essentials
Learn how to use Jira Align at the program level and how to plan for and manage your Program Increment (PI).
Managing Agile Boards and Reports
Learn how to pick the right board type for your team and customize it to fit your specific requirements.
Atlassian Certified Associate
Jira Software Board Configuration
Earn an associate-level credential from Atlassian that shows you can effectively configure Jira Software boards.