Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage
Highlighted

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

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?

3 comments

DPK J Community Leader Nov 24, 2019

@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.

Like Sornsiri Karnchanasook likes this

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

Like Sornsiri Karnchanasook likes this

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. 

Like Marianne Miller likes this
Marianne Miller Community Leader Feb 05, 2020

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. 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Agile

On-demand: Fireside chat with Atlassian on scaling agile organizations

Scaling an agile organization and setting it up for success over the long term is a hard thing to do. We hear a common set of questions from customers all the time, questions like: Can agile scal...

3,910 views 2 17
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you