Your browser does not support JavaScript! The Sprint | Scrum Inc
  • Google
  • RSS

The Sprint

The Sprint is the heart of Scrum. It is a short, consistent cycle no longer than four weeks. The goal is to have an iteration short enough to keep the team focused but long enough to deliver a meaningful increment of work.

Estimated time for this course: 5 minutes
Audience: Beginner
Suggested PrerequisitesScrum Framework

Upon completion you will:

  • Understand how the Sprint enables the Scrum Framework
  • Know how the Sprint focuses the Team
  • When to interrupt the Sprint
  • Qualify for Scrum Alliance SEUs and PMI PDUs. See FAQ for details
Sprint Overview:

The Sprint contains all the elements of Scrum. It is a contiguous process with one iteration immediately following the next without pause. While the first Scrum team used a month long Sprint, most teams now work in one or  two-week cycles. 

The sprint begins with Planning and ends with Review & Retrospective. Each day of the Sprint is marked by a brief meeting called the Daily Scrum or simply, Stand-up, as everyone should stand to keep the meeting short.This regular cycle:


  • Delivers on the Sprint Goal. A potentially shippable increment of software, a useable iteration of a hardware product, or any delivery that directly produces visible customer value.
  • Gives the Team regular, high quality feedback on delivered value. The Team can then inspect and adapt both their process and their product based on real and actionable customer input.
  • Measures Team output over a consistent and recurring period of time. This is called the Team's velocity. The Team can use this metric to assess the impact of process experiments.

Sprints begin and end on fixed dates. There are no extensions. No changes can be made to the Sprint Backlog that would endanger the Sprint Goal. No additional work should be brought into the Sprint unless the Sprint Goal has been reached or a feature emerges of such high value it must be brought into Sprint. In this instance, the Team should execute the Interrupt Pattern. In large projects with multiple Teams, dependencies must be carefully managed across teams. Often this means Sprints should begin and end on the same dates and have the same length. (See Scrum at Scale.)

View and Download Class Slides


These patterns can be found on the open Google site dedicated to PLoP

The Sprint

The Scrum Pattern Language of Programming (PLoP) codifies well known Agile practices that have been successfully implemented many times.

Learn Scrum Online

Scrum Startup for Teams is the best way to learn Scrum online. The curriculum and content was developed in collaboration with the co-creator of Scrum, Dr. Jeff Sutherland. Learn the fundamentals of Scrum in empirically-based lessons informed by the latest research and real-world experience. This is online training from the source.

Stay Connected

Stay Connected

Sign up to receive the latest Scrum news, special offers, and our monthly newsletter.

You have Successfully Subscribed!

Login to your ScrumLab Account

You have Successfully Subscribed!

My Account

You have Successfully Subscribed!

Try Scrum Startup For Teams

To access your free trial, please enter a valid email address. We will email you a link to access a trial of Scrum Startup For Teams for 7 days. The trial contains partial lessons to give you a sneak peek of the course content.

You have Successfully Subscribed!