Sprint
A sprint is a fixed-length time box (usually 1-4 weeks) in which a Scrum team works to complete a set of predefined work items and deliver a potentially usable product increment.
§ 1 Definition
In Scrum and other Agile frameworks, a sprint (also called an iteration) is a time-boxed period during which a team focuses on a specific set of work items from the Product Backlog. The core rule is that sprint duration is fixed and never extended; if the work cannot be completed, the scope is reduced, not the deadline. Each sprint begins with Sprint Planning and ends with a Sprint Review and Retrospective. The goal is to produce a potentially releasable increment of the product at the end of every sprint. The consistent cadence creates a predictable rhythm: stakeholders know exactly when to expect new features, and the team gets regular feedback to adjust priorities.
§ 2 Sprint Characteristics
Every sprint has a fixed duration (typically two weeks, never more than one month). The duration is chosen based on the product context and team maturity and remains consistent. A shorter sprint means faster feedback but more overhead for planning and review. Longer sprints provide more uninterrupted work time but delay stakeholder feedback. The sprint duration is a commitment; it never changes during a sprint. If the team realizes they have taken on too much work, they negotiate scope with the Product Owner rather than extending the sprint.
§ 3 The Sprint Goal
Each sprint is anchored by a Sprint Goal: a concise statement of the purpose and objective of the sprint. The Sprint Goal creates coherence, giving the team a shared focus even if the specific tasks shift slightly. It answers the question "Why are we doing this sprint?" rather than just "What are we doing?" A good Sprint Goal is achievable, specific, and provides flexibility in how the team achieves it. If the work turns out to be more complex than expected, the team can adjust the approach while still aiming for the Sprint Goal.
§ 4 What Happens During a Sprint
During the sprint, the team works from the Sprint Backlog (selected items + plan). They hold a Daily Scrum each day to inspect progress and adapt. No changes are made that would endanger the Sprint Goal. Scope can be clarified and renegotiated with the Product Owner if the team discovers new information. Quality does not decrease; the Definition of Done remains constant. At the sprint's end, the team demonstrates the Increment at the Sprint Review and reflects on their process in the Retrospective.
§ 5 Common questions
- Q. What happens if we cannot finish the sprint work?
- A. Scope is reduced, not deadline extended. Unfinished items are returned to the Product Backlog and reprioritized for a future sprint.
- Q. Can a sprint be cancelled?
- A. Yes, but only by the Product Owner. If the Sprint Goal becomes obsolete (e.g., a market shift), the sprint can be terminated and re-planned. This is rare.
- Q. Should every team use the same sprint length?
- A. No. Choose a sprint length that fits your product cycle and stakeholder availability. Two weeks is common, but one-week and three-week sprints also work well.
- A sprint is a fixed-length time box (1-4 weeks) focused on delivering a usable Increment.
- The Sprint Goal provides purpose and coherence for the sprint work.
- Scope is reduced if the team cannot complete all work; the deadline never moves.
- The consistent sprint cadence creates predictability for stakeholders and the team.
We work in two-week sprints. You get demonstrable progress every cycle, not promises. See how our Agile process delivers results. Get in touch.
Get in touchA sprint is a fixed-length time box (usually 1-4 weeks) in which a Scrum team works to complete a set of predefined work items and deliver a potentially usable product increment.
Category: General (also: Software Engineering, Business)
Author: Atomic Glue Technical Team
## Definition
In Scrum and other Agile frameworks, a sprint (also called an iteration) is a time-boxed period during which a team focuses on a specific set of work items from the Product Backlog. The core rule is that sprint duration is fixed and never extended; if the work cannot be completed, the scope is reduced, not the deadline. Each sprint begins with Sprint Planning and ends with a Sprint Review and Retrospective. The goal is to produce a potentially releasable increment of the product at the end of every sprint. The consistent cadence creates a predictable rhythm: stakeholders know exactly when to expect new features, and the team gets regular feedback to adjust priorities.
## Sprint Characteristics
Every sprint has a fixed duration (typically two weeks, never more than one month). The duration is chosen based on the product context and team maturity and remains consistent. A shorter sprint means faster feedback but more overhead for planning and review. Longer sprints provide more uninterrupted work time but delay stakeholder feedback. The sprint duration is a commitment; it never changes during a sprint. If the team realizes they have taken on too much work, they negotiate scope with the Product Owner rather than extending the sprint.
## The Sprint Goal
Each sprint is anchored by a Sprint Goal: a concise statement of the purpose and objective of the sprint. The Sprint Goal creates coherence, giving the team a shared focus even if the specific tasks shift slightly. It answers the question "Why are we doing this sprint?" rather than just "What are we doing?" A good Sprint Goal is achievable, specific, and provides flexibility in how the team achieves it. If the work turns out to be more complex than expected, the team can adjust the approach while still aiming for the Sprint Goal.
## What Happens During a Sprint
During the sprint, the team works from the Sprint Backlog (selected items + plan). They hold a Daily Scrum each day to inspect progress and adapt. No changes are made that would endanger the Sprint Goal. Scope can be clarified and renegotiated with the Product Owner if the team discovers new information. Quality does not decrease; the Definition of Done remains constant. At the sprint's end, the team demonstrates the Increment at the Sprint Review and reflects on their process in the Retrospective.
## Common questions
Q: What happens if we cannot finish the sprint work?
A: Scope is reduced, not deadline extended. Unfinished items are returned to the Product Backlog and reprioritized for a future sprint.
Q: Can a sprint be cancelled?
A: Yes, but only by the Product Owner. If the Sprint Goal becomes obsolete (e.g., a market shift), the sprint can be terminated and re-planned. This is rare.
Q: Should every team use the same sprint length?
A: No. Choose a sprint length that fits your product cycle and stakeholder availability. Two weeks is common, but one-week and three-week sprints also work well.
## Key takeaways
- A sprint is a fixed-length time box (1-4 weeks) focused on delivering a usable Increment.
- The Sprint Goal provides purpose and coherence for the sprint work.
- Scope is reduced if the team cannot complete all work; the deadline never moves.
- The consistent sprint cadence creates predictability for stakeholders and the team.
## Related entries
- [Agile Development](atomicglue.co/glossary/agile-development)
- [Scrum](atomicglue.co/glossary/scrum)
- [Roadmap](atomicglue.co/glossary/roadmap)
- [Technical Debt](atomicglue.co/glossary/technical-debt)
Last updated July 2025. Permalink: atomicglue.co/glossary/sprint