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.



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

Sprint Goals: The Key to a Well-Executed Sprint

Sprint goals are key to a successful Sprint. They help keep the Scrum team on track and moving together in one direction. Without Sprint goals, the Scrum team can easily lose focus and get sidetracked. In this blog post, we'll discuss what sprint goals are and how they can help your Scrum team stay focused

What is a Sprint Demo? #AskArtisan

What's a Sprint Demo? It's typically a sure sign that your organization has no idea how to do a Sprint Review! I'll explain in this edition of #AskArtisan.