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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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

Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Nov 24, 2019

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?


Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 24, 2019

@KatWe 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
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Nov 25, 2019

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
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
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. 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events