How long are your sprints? What day of the week and time of day do they start?

[Kat Warner _TechTime_]

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?

[DPK J]

@Kat Warner _TechTime_We also use one week sprint, reason for this is, we started with 2 week long sprint but,

• People were lazy in first week,
• No body wanted to split task into smaller tasks, and
• Spillover was too much

After switching to one week, planning load has increased but spillover is far less and we learning to divide task into smaller sub tasks.

[Kat Warner _TechTime_]

One week sprints does make it easier to 'course correct'.

[Nicole Reichert]

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. 

[Marianne Miller]

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.