StackLift
All terms

Glossary

Sprint

A fixed, short work cycle, one month or less, that ends with a usable, reviewed increment.

A sprint is a fixed-length work cycle of one month or less in which a team plans, builds, tests and reviews a usable piece of a product. In Scrum, each sprint has a goal and ends with a sprint review and a retrospective.

Inside a sprint are sprint planning, a daily scrum, the review and the retrospective. The team commits to a sprint goal and a set of backlog items.

Clients see working software at every sprint review, and the team's pace becomes visible over time, which makes planning more realistic.

Start in 60 seconds

Put this to work on your project.

Get an AI-assisted, architect-reviewed scope, cost range, and timeline. Free, no login.

The complete guide

Sprint: the complete guide

Updated November 18, 2026 · Published by , Founder, StackLift AI. Written with AI assistance; how we make content.

Short answer

A sprint is a fixed, short period, one month or less, in which a team plans, builds, tests and reviews a usable slice of a product. In Scrum, each sprint has a goal, a set of backlog items the team commits to, and ends with a review of the working result and a retrospective on how the team worked.

What is a sprint in software development?

A sprint is a time-boxed cycle of work. The length is fixed, so the team gets a steady rhythm: plan, build, show, reflect, repeat. The Scrum Guide says a sprint is one month or less, and many teams choose one or two weeks.

During a sprint the aim is a finished, usable increment, not a pile of half-done tasks. What counts as finished is set by the definition of done.

What happens in a sprint?

The Scrum events inside a sprint
EventPurposeWho takes part
Sprint planningChoose a sprint goal and the items to work onWhole Scrum team
Daily scrumShort check on progress toward the goal and next stepsDevelopers
Sprint reviewShow the working result and gather feedbackScrum team and stakeholders
Sprint retrospectiveFind ways to improve how the team worksScrum team

The sprint itself is the container for these events. It is the time box that holds them.

Sprint goal and sprint backlog

The sprint goal is the single purpose of the sprint, such as customers can pay by card. The sprint backlog is the set of user stories chosen to reach it, plus the plan for delivering them.

Teams often size stories in story points to see how much they can take on. Over several sprints the team's pace becomes visible, which makes planning more realistic.

How do you run a sprint well?

  1. Refine the backlog beforehand so the top items are small and clear.
  2. Hold planning and agree a sprint goal the team believes it can reach.
  3. Work the items in priority order, finishing one before starting another where possible.
  4. Check progress daily and raise blockers right away.
  5. Do not add scope mid-sprint without talking it through; changes go to the backlog for the next one.
  6. End with a review of working software, then a retrospective with one or two concrete improvements.

Common sprint problems

  • Overcommitting, then carrying unfinished work into the next sprint every time.
  • Stories too large to finish, so nothing is demonstrable at the review.
  • Skipping the review or the retrospective when busy, which removes the learning loop.
  • Changing the sprint goal or adding work mid-sprint, which turns it into a moving target.
  • Treating the sprint as a mini deadline for the client instead of a cadence for the team.

Sprints in a client project

For a buyer, sprints mean you see working software at a regular interval instead of waiting for one large delivery. Ask what will be shown at each review and how you give feedback.

StackLift names several of its engagements as sprints: the AI Scope Sprint, the Production Rescue Sprint and the MVP Build Sprint. The ongoing AI Software Pod includes sprint planning and a weekly delivery report, and clients follow live project state in the client portal. For the model behind it, read about agile, and use the free estimate to size your project.

How do you plan a sprint that actually finishes?

Start from capacity, not wishes. Look at how much the team finished in recent sprints, account for holidays and absences, and pick a sprint goal that fits. It is better to finish a smaller goal than to miss a larger one.

Leave room for the unplanned: bug fixes, support questions and review time. Break stories into tasks during planning so risks show up early, and order the work so the riskiest items start first. If a story cannot be finished in the sprint, split it before the sprint begins, not halfway through. Over time, steady sprints give you a realistic forecast of when features will arrive.

Who does what during a sprint?

Scrum names three accountabilities, and each one matters to how a sprint runs. The product owner decides what is worth building and in what order. The developers, which means everyone who builds and tests the work, decide how to build it. The Scrum Master keeps the process healthy and removes obstacles.

Scrum accountabilities in a sprint
RoleOwnsTypical question they answer
Product ownerThe product backlog and its orderWhat gives the most value next?
DevelopersThe sprint backlog and the quality of the incrementHow do we build this and prove it works?
Scrum MasterThe process and the team's ability to follow itWhat is slowing the team down?
StakeholdersFeedback at the sprint reviewIs this what we needed?

On a client project the buyer usually acts as, or appoints, the product owner. Quick decisions from that person are one of the strongest predictors of a smooth sprint, because blocked questions are the most common reason work stalls.

How long should a sprint be?

There is no single right length. The rule is that the length is fixed and no longer than one month. Shorter sprints give faster feedback and limit how far the team can drift off course. Longer sprints give more room for bigger stories but delay learning.

Sprint length trade-offs
LengthStrengthWatch out for
One weekVery fast feedback; good for small teams and early experimentsCeremony overhead takes a large share of the time
Two weeksA common balance of focus and feedbackStories still need to be small enough to finish
Three to four weeksRoom for larger changes and integration workFeedback arrives late; scope drifts more easily

Pick a length, keep it for several sprints, and change it only when the retrospective shows a real reason. Changing length often makes it hard to see the team's pace.

What does a sprint look like in practice?

A sprint goal is easiest to understand through examples. Each one below is a sentence a team could put on the wall and test at the review.

  • Online store: a visitor can add products to a cart and pay by card, with an order confirmation email.
  • Internal tool: a manager can approve or reject a leave request and the employee sees the result.
  • AI feature: a support agent can ask a question and get an answer drawn from the help center, with the source shown.
  • Mobile app: a new user can sign up, verify an email address and reach an empty home screen.
  • Integration: orders placed in the shop appear in the accounting system without manual entry.
  • Hardening: the login flow has rate limiting, error handling and logging, and the team can roll back a release.

Notice that every goal describes something a person can do, not a list of technical tasks. That is what makes the review meaningful to someone who does not read code.

How do you tell whether sprints are working?

Good sprints leave visible evidence. You do not need a complicated dashboard; a few signals, tracked honestly over several sprints, tell you most of what you need.

  • Goal outcome: did the team reach the sprint goal, and could you see it working at the review?
  • Finished vs. started: how much work met the definition of done compared with how much was begun?
  • Pace over time: is the amount the team finishes steady enough to forecast with?
  • Carry-over: how often do items roll into the next sprint, and why?
  • Defects found after review: are bugs appearing in work that was called done?
  • Feedback acted on: did something from the last review or retrospective change the plan?

Use velocity, the total of story points finished per sprint, as a planning aid for the team, not as a score to compare teams. Once it becomes a target, people inflate estimates and the number stops meaning anything.

What tools do teams use to run sprints?

The method matters more than the tool, but a shared board makes progress visible. Common choices are Jira, Linear, Azure DevOps, GitHub Projects, Trello and Asana. Teams also use a code host such as GitHub or GitLab, a chat tool for daily questions, and a continuous integration service so every change is built and tested automatically.

Whatever you choose, keep one source of truth for the backlog and make sure the buyer can see it. A CI/CD pipeline is part of the same picture, since a sprint that cannot ship its work safely has not really finished it.

What do sprints mean for cost and timeline?

A sprint is a unit of time, so the main cost drivers are the size of the team, the complexity of what you ask for and how much work is left unclear. Clear, small stories finish; vague, large ones spill over and push the schedule. Most first versions take 6–16 weeks depending on scope, which across short sprints means a handful of review points where you can redirect the work.

For a rough figure, the free estimate returns cost, timeline and team in about five minutes, and the software estimation playbook explains how sizing becomes a plan.

How do you start running sprints?

  1. Name a product owner who can decide quickly and is available during the sprint.
  2. Write the first backlog as user stories with clear acceptance criteria.
  3. Agree a definition of done that includes testing and review.
  4. Choose a sprint length and hold the same day and time for each event.
  5. Run a short first sprint, and measure what the team actually finished.
  6. Hold the review with real users or stakeholders, and write down what changes.
  7. Hold the retrospective and pick one improvement to try next sprint.

Questions people ask

How long is a sprint?

The Scrum Guide sets a maximum of one month. Many teams use one or two weeks. Pick a length short enough to limit risk and long enough to finish something real, then keep it constant.

Is a sprint the same as an iteration?

Almost. Iteration is the general agile term for a repeated work cycle, and sprint is the Scrum name for it. In practice people use them interchangeably.

Can you change scope during a sprint?

The sprint goal should stay fixed. The team and product owner can clarify or adjust the details of the work if needed, but new requests normally wait for the next sprint.

What happens if the team does not finish?

Unfinished items are not counted as done. They go back to the backlog and are re-ordered. The team looks at why in the retrospective and plans more realistically.

Do you need Scrum to use sprints?

No. Sprints are used by teams with different agile approaches. Scrum defines them formally, but the idea of a fixed-length cycle works on its own.

What is the difference between a sprint and a milestone?

A sprint is a repeating, time-boxed cycle of work. A milestone is a point in the plan where a specific outcome is expected. A project can have several sprints leading to one milestone.

Who decides what goes into a sprint?

The product owner sets the order of the backlog, and the developers decide how much they can take on. The sprint goal is agreed by the whole team during sprint planning.

Can a sprint be cancelled?

Yes, but only the product owner can cancel one, and it is rare. It makes sense when the goal no longer has value, for example because the business direction changed. Finished work is reviewed and the rest returns to the backlog.

How do sprints work with a fixed budget?

Scope, budget and delivery path are agreed first, and sprints then deliver that scope in slices. If the client wants to add or swap items, that is handled as an explicit change so the baseline stays clear.

Sources

Sources and further reading

The standards, rules, research and official documentation this page draws on.