Scrum allows sprints to be of any length up to one calendar month (so, yes, you could run a one day sprint if you wanted to — some support/service teams actually do). Over the years, however, sprints have shortened from a typical three or four weeks to a much more common two weeks or even one week.

This is an excellent trend. Shorter sprints, like small PBIs, are easier to manage. Shorter sprints hold less overall work, so there’s fewer details to plan and get confused over. Less overall work also means less risk and fewer surprises during the sprint. Sure, the team gets less done during a 2-week sprint than a 3-week sprint, but the reduction in complexity results in an increase in day-to-day productivity and improved quality.

Scrum teams are responsible for choosing sprint length and are encouraged to experiment with different sprint lengths. If your sprint is longer than 2 weeks, try a shorter sprint.

FEATURED RESOURCE:

FEATURED RESOURCE:

Sprint Goals Reference Guide

Download Now!

Swipe this FREE DOWNLOAD for a breakdown of sprint goals.

Normally available ONLY to Artisan students, we’re offering this handy guide to you for a limited time!

More About #Sprints

Gearing a Team for Maximum Outcomes

Creating a maximum outcome team is every ScrumMaster’s goal, but you must first understand how great teams form and what YOU need to do to create a great team.

Speeding up Your Scrum Teams

Effective Scrum use is more than Sprint Planning, Daily Scrums, and so on. To see a big difference in your team's Sprints, make these workflow changes.

Keep Your Sprints Short

Scrum teams are responsible for choosing sprint length and are encouraged to experiment with different sprint lengths, but shorter sprints are easier to manage.

Keep Your Eyes on the Sprint Goal

In this article, we'll discuss how a team bares responsibility for the Sprint and what should be done if they can’t get everything done they committed to.