You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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.