Definition
Sprint
A sprint is a fixed, repeating time-box — usually one to four weeks — during which a Scrum team commits to a focused set of work and aims to ship a usable increment. It is the Scrum term for the iteration other frameworks call a cycle, giving the team a regular cadence for planning, focus, and review.
Key takeaways
- A sprint is the Scrum term for a fixed, repeating time-box — usually one to four weeks — in which a team ships a usable increment.
- It opens with sprint planning and a sprint goal, syncs daily at standup, and closes with a review and a retrospective.
- The fixed length caps how wrong any single plan can be and is what makes velocity (completed work per sprint) meaningful.
- Sprint is the same idea other frameworks call a cycle; many teams blend it with a Kanban board and WIP limits for flow inside each one.
A sprint is the heartbeat of Scrum. It opens with sprint planning, where the team pulls a realistic slice of the backlog into a sprint goal it believes it can finish. Through the sprint the team protects that scope, syncs daily at standup, and resists mid-flight additions. It closes with a review of what shipped and a retrospective on how the team worked.
The discipline of the time-box is the point. A fixed, unchanging length caps how wrong any single plan can be and turns planning into a habit rather than an event. Consistent sprint lengths are also what make velocity meaningful — you can only average completed work per sprint if every sprint is the same size.
Sprints trade the pure continuous flow of Kanban for rhythm and predictability. Many teams blend the two: sprints supply the cadence and the commitment, while a Kanban board with WIP limits manages how work actually flows inside each one. Work left unfinished at the end rolls forward to the next sprint rather than being abandoned.
Planoda calls this same time-box a cycle: work auto-rolls to the next cycle when unfinished, and burndown and velocity charts are generated automatically from the cycle's committed scope.
Related terms
- Cycle (Sprint)A cycle — often called a sprint — is a fixed, repeating time-box, usually one or two weeks, during which a team commits to a focused set of work and aims to finish it. Cycles create a regular cadence for planning, focus, and review, turning an open-ended backlog into shippable increments.
- Sprint PlanningSprint planning is the meeting that opens a sprint, where the team reviews the prioritized backlog and decides what it will commit to in the coming iteration. The team agrees on a sprint goal, pulls a realistic amount of work it believes it can finish, and clarifies scope. The output is a concrete, achievable plan for the time-box ahead.
- VelocityVelocity is the average amount of work a team completes per cycle, measured in issues or story points. By tracking it over several cycles, teams forecast how much they can realistically take on next. Velocity is a planning aid for a specific team over time — never a target to maximize or a way to compare teams against each other.
- BurndownA burndown chart tracks remaining work against time over a cycle, sloping from the total scope down toward zero as items are completed. It shows whether a team is on pace to finish what it committed to, making slippage visible early. The ideal line falls steadily; a flat line warns that work is stalling.