What is a sprint?
A sprint is a fixed, short work cycle of one to four weeks in which a Scrum team completes a previously agreed set of tasks and delivers a reviewable result at the end.
DEFINITION
The sprint is the heart of Scrum. Every sprint has a fixed goal agreed at the start in sprint planning. The team then works focused on that goal and aims to deliver a “Done” increment at the end — something functional that can be demonstrated. Sprints always have the same length, usually one to two weeks. This consistency creates rhythm and predictability. During the sprint, no new requirements are added. That protects the team from constant reprioritisation and is called sprint protection. The sprint ends with a sprint review, where results are checked, and a retrospective, where the process is reflected on. The goal is not perfection at the end of the sprint, but learning through short feedback cycles.
CONNECTIONS
Leadership
Team dynamics change within a sprint: at the start more clarification is often needed; towards the end more focus and support. Situational leadership along the sprint rhythm is a concrete application of this competence.
Artificial Intelligence
Sprint goals work well as a structure template for prompts: a clear goal, a defined scope and measurable results also make AI assignments more precise and evaluable.
Project Management
Sprint review dates are de facto milestones in an agile context: at the end of each sprint there is a finished increment that can be reviewed and released. That matches milestone logic in classic PM.
KEY POINTS
- A sprint lasts one to four weeks and has a fixed goal.
- During a sprint, no new requirements are added.
- At the end there is a reviewable, functional result.
- Sprints always end with review and retrospective.
- Constant sprint length creates rhythm and predictability.
EXAMPLE
A product team plans a two-week sprint with the goal: users can register successfully and set up their profile. The team breaks this down into concrete tasks, distributes the work and works focused for two weeks. At sprint end, registration works. The team demonstrates it to the product owner, gathers feedback and plans the login function for the next sprint.
MISCONCEPTIONS
Can sprints be extended if the team does not finish?
No. Sprints have a fixed length that is not extended. If the team does not finish, incomplete tasks go back to the backlog and are reprioritised.
Must every sprint end with a fully error-free product?
No. The increment should work and be demonstrable, but need not be a complete product. Perfection emerges over several sprints.