A sprint is a short, fixed stretch of time, usually two weeks, in which a team picks a small goal and finishes it. Agile teams run sprints one after another.
Nobody runs anywhere: the name comes from the short, focused burst, and the point is to ship something that works, learn from it and plan the next one.
What a sprint is
A sprint is a timebox. Its length is set before it starts and doesn't stretch when work runs late: the sprint ends on the planned day whether everything is done or not. Most teams use two weeks. Some use one, a few use three or four; the Scrum Guide caps a sprint at one month.
Sprints come from Scrum, the best-known agile framework, though plenty of teams run them without the rest of Scrum. Whatever the label, every sprint has the same shape:
- Planning at the start, to pick a goal and the work for it.
- The work itself, with a short stand-up each day.
- A review at the end, to show what got built.
- A retrospective, to improve how the team works.
The next sprint starts straight after, with no gap between them.
Why teams work in short cycles
The alternative is one long plan: gather every requirement, build for six months, release once. It tends to fail in a predictable way. By the time anyone sees the product, needs have moved on, and the mistakes made in month one are baked into everything built after them.
A short cycle shrinks the feedback loop. Every couple of weeks the team has something real to show, users or stakeholders react to it, and the next sprint's plan takes that reaction into account. A wrong guess costs two weeks, not six months.
Because the timebox never moves, the team learns how much it can finish in one, and its planning gets more accurate over time. The steady rhythm also makes the team predictable to everyone around it: the product owner knows when the next review is, and stakeholders know when to expect something new.
Sprint planning
Wondering how this was made? How we make these