What is a sprint in agile?

A sprint in agile is a short, fixed period, usually one to four weeks, in which a team commits to finishing a set amount of work and then stops to review what it delivered. At the start, the team picks tasks from a waiting list called the backlog. During the sprint, it works only on those. At the end, it shows the finished work, talks about what to improve, and plans the next sprint.

The term comes from Scrum, the most widely used agile method, but plenty of small teams borrow the idea without adopting the whole framework. The appeal is simple: a short deadline you can actually see keeps work moving.

Why sprints matter for a small business

Small teams rarely lack ideas. They lack focus. Everything feels urgent, priorities change daily, and big projects drift for months. Sprints put a fence around the work.

• Short-term focus. For two weeks, the team knows exactly what it is working on.
• Regular results. Something finished lands every sprint, instead of one big reveal at the end.
• A safe place to change your mind. New ideas go into the backlog and are considered at the next planning, not mid-sprint.
• Honest planning. After a few sprints you know how much your team really gets done, so promises to clients get more accurate.

How a sprint in agile works: an example

Zanele runs a four-person app studio in Johannesburg, building a booking app for a chain of salons. The team works in two-week sprints.

1. Sprint planning (Monday, 1 hour). They agree a sprint goal: “A customer can book and cancel an appointment.” They pull eight tasks from the backlog that serve that goal.
2. Daily check-in (15 minutes). Each person says what they finished, what is next, and anything blocking them.
3. The work. When the salon owner asks for a loyalty-points feature mid-sprint, Zanele adds it to the backlog instead of the current sprint.
4. Sprint review (Friday of week 2). They demo booking and cancelling to the client. Seven of eight tasks are done; the eighth goes back to the backlog.
5. Retrospective (30 minutes). The team agrees one change: get designs approved before the sprint starts, not during it.

Key parts of a sprint

Best practices and common mistakes

• Keep the length fixed. Stretching a sprint to fit the work defeats the point. Move unfinished work to the next one instead.
• Write a real goal. “Do the tasks” is not a goal. “Customers can pay online” is.
• Do not add work mid-sprint unless it is a true emergency. Put new requests in the backlog.
• Keep the backlog tidy. Before each planning session, put the most important work at the top and delete ideas nobody still wants. Planning is quick when the list is already in order.
• Keep the ceremonies short. A three-person team does not need a two-hour planning meeting. Match meetings to team size.
• Actually hold the retrospective. It is the part teams skip first and the part that makes each sprint better than the last.
• Know when sprints do not fit. Support requests and walk-in orders arrive unpredictably. A kanban board often suits that kind of flow better.

If you are new to managing work this way, our guide to project management for beginners covers the basics first.

Related terms

Agile project management is the wider approach that sprints belong to. A kanban board is the other common agile way of working, with continuous flow instead of sprints. A project milestone marks a major checkpoint, which may land at the end of a sprint.

Sprints in startbuddi

Every project in Work has a Sprints tab. You create a sprint with a name, start and end dates and an optional goal (“What should be true when this sprint ends?”), then pull tasks in from the backlog, which lists open tasks not yet in a sprint. Tasks can carry story points, and velocity shows the average completed over your last three sprints.

When you complete a sprint, you choose whether unfinished tasks go back to the backlog or into the next sprint. A burn chart shows progress, with a table view if you prefer numbers. The same tasks appear on the project’s board, list and timeline, so the sprint never becomes a separate system. Your next step: pick one project, set a two-week sprint with a single goal, and hold a short review when it ends. If you are comparing tools, see our page on agile project management software.