Skip to main content
Mobius
Beginner

What is a sprint

Also known as: sprints, agile sprint, Scrum sprint

Definition

A sprint is a fixed period, one month or less, in which a Scrum team works toward one goal and delivers a working result. The dates stay, the work can flex.

Why it matters

A sprint turns a long project into short, fixed deadlines the team can actually see.

Common mistakes

Adding work in the middle of a sprint that endangers the Sprint Goal.

Related terms

Worked exampleIllustration

Two weeks to online booking at the clinic

A three person web team builds the clinic's online booking in a two week sprint. The Sprint Goal: patients can book and cancel online.

  1. Day 1

    The team pulls in four items that fit ten working days: the booking form, the cancellation link, calendar sync and a confirmation text message.

  2. Day 6

    A request arrives for a pay in advance option. It does not serve the goal, so it goes to the backlog.

  3. Day 9

    The booking form and the cancellation link work and are shown to the office manager. The confirmation message is not done, so the Product Owner and the team agree to finish without it. The goal still holds.

  4. Day 10

    The Sprint Review of the working booking, then the Retrospective. The confirmation message returns to the backlog.

The end date never moved. What fitted inside it did.

Illustration

The end date is a wall

Sprint: days 1 to 10The end does not move

Goal: patients book and cancel online

  • Booking form
  • Cancellation link
  • Calendar sync
  • Confirmation text message

Backlog

  • Pay in advanceDay 6: does not serve the goal

A new request arrives in the middle of the sprint. It does not serve the goal, so it waits in the backlog instead of stretching the sprint.

Ten working days with a fixed end. Move the day: what does not serve the Sprint Goal, or does not fit, goes back to the backlog, and the wall stays where it is.

Definition

In the Scrum Guide, a sprint is a fixed length event of one month or less, and it is the container for all the other Scrum events: Sprint Planning, the Daily Scrum, the Sprint Review and the Sprint Retrospective. Each sprint has a Sprint Goal, the single objective for the sprint. During the sprint no changes are made that would endanger that goal, and the scope may be clarified and renegotiated with the Product Owner as more is learned. A team can create several increments within one sprint and deliver them before it ends, so the Review inspects working results and is never a gate for releasing them. A sprint can be cancelled only if its goal becomes obsolete, and only the Product Owner can cancel it. The name comes from the everyday sense of a short, all out run. A design sprint, a five day workshop format, is a different thing.

Why it matters

Because the end date never moves, the question during the sprint is not whether to extend but what fits, so work that does not serve the goal waits for the next sprint instead of stretching this one. The owner gets a working result to look at every few weeks, and the whole team gets a rhythm to plan around.

Directly related: Scrum, Agile, Scope.

Improvement tips

  • Keep the same sprint length, many teams choose two weeks, so the team learns how much fits in one.
  • Write one Sprint Goal at Sprint Planning, and test every new request against it.
  • Send requests that do not serve the goal to the backlog, and let the Product Owner renegotiate the scope inside the goal when the team learns more.
  • Deliver working pieces as soon as they are ready. The Sprint Review inspects them, it is not a gate they have to wait for.

Common mistakes

  • Extending the end date to finish open items, instead of closing on time and returning them to the backlog.
  • Treating the work inside a sprint as frozen, when it can be clarified and renegotiated with the Product Owner as long as the goal holds.
  • Ending a sprint with nothing that works, only parts in progress.

Related terms

Quick check

What is the longest a sprint can last, according to the Scrum Guide?

Choose an answer

Frequently asked questions

Do I need to work in sprints when starting a new business?
It is not required. Short fixed periods with one clear goal each help a new business move, because each one ends with something you can show, not only a plan.
When does a new business first start using sprints?
When a small team builds something over several weeks, such as a website or a new service, and needs regular points to show progress and adjust.
How long should a sprint be?
The Scrum Guide sets the maximum at one month. Many teams choose two weeks: long enough to finish something useful, short enough to change course quickly. Once you choose a length, keep it.
Can sprints help a new business control spending?
They give a checkpoint every few weeks. At each one you see what the time and money produced, and decide whether to continue, change direction or stop before more is spent.
Why do sprints matter for an established business?
They protect strategic work from the daily noise. For a fixed period the team works toward one goal, and new requests wait for the next sprint unless they serve it.
What happens when a business owner changes the goal in the middle of a sprint?
The work already aimed at the old goal is lost and the rhythm breaks. The Guide allows a sprint to be cancelled when its goal becomes obsolete, and only the Product Owner can do it. Short of that, the goal stays and new ideas go to the backlog.
How do I start using sprints and still handle client emergencies?
Plan the sprint with some time kept free for urgent requests, so an emergency does not push out the goal. If emergencies keep filling that time, the sprint was planned too full.
How do I handle tasks that are not finished by the end of the sprint?
Return them to the backlog, the list of all the work still to do, and decide at the next Sprint Planning whether they still matter.
What is a sprint in simple business words?
A short fixed period, one month or less, with one goal and a working result at the end. The dates are fixed, and what fits inside them can change.
Is working in sprints stressful or risky?
It is meant to lower the pressure: the goal is realistic for the time, outside requests wait, and the end date is known in advance. A sprint is a fixed box, not a race.
Do I need complex software to run sprints?
No. A board on the wall, a spreadsheet or any simple task list is enough to track the sprint's items.
What is a Sprint Goal and do we need one?
It is the single objective of the sprint, written at Sprint Planning. It gives the team a reason to say yes or no to each new request, and every sprint in Scrum has one.

Sources: Ken Schwaber and Jeff Sutherland, The Scrum Guide, November 2020, scrumguides.org

Last reviewed: 2026-09-24

I have worked with

What Clients Say

From different fields, at different stages of business

Dan Manto

Eclipse Capital

Real Estate Investment and Finance, USA

Arty McLabin

GameReady

Game Development Education and Outsourcing, International

Anna, Beautician

Anna

Beautician

After I finished a cosmetology course at a leading company, I was confused. I didn't know how to open a business, what to sell from home, or how to bring in clients. Since I reached out to Mobius, everything has changed. We built an organized plan with clear steps and no unnecessary risks. Today I see results, and I'm growing and developing every month.

Mark, Massage therapist, Gan Yavne

Mark

Massage therapist, Gan Yavne

When I finished a massage course, I imagined a different world. I found out it's a hard field, and financial stability isn't easy to find. When I came to Mobius, something changed. We started an organized process and built a business plan. Without Mobius? I probably would have given up. Today I believe in myself and in my own path.

Projects always running late or over budget?

Alex helps Israeli businesses deliver projects on time and on plan. The first call is free.

+972 055-248-6151. Better on WhatsApp: I am in meetings most of the day and answer as soon as I am free.