What Is a Sprint in Scrum? Length, Ceremonies and Deliverables
The sprint is the heartbeat of Scrum. It is a short, fixed period during which a team turns a set of priorities into a working, tested increment of the product. Understanding how a sprint works helps you follow a software project, read progress reports and take part in the right meetings.
This guide explains what a sprint in Scrum is, how long it lasts, the events that structure it and what you should receive at the end of each one.
Definition: what is a sprint?
According to the Scrum Guide, a sprint is a fixed-length event of one month or less during which the Scrum team creates a usable increment. A new sprint starts immediately after the previous one ends. All the work needed to reach the product goal, including planning, development, review and retrospective, happens inside sprints.
Each sprint has a sprint goal: a single objective that gives the team focus, for example “Sales managers can approve quotes online”.
How long is a sprint?
The Scrum Guide sets a maximum of one month. In practice, most software teams choose one to four weeks, and two weeks is a very common choice.
| Sprint length | Advantages | Points of attention |
|---|---|---|
| 1 week | Very fast feedback, easy to adjust | Meetings take a larger share of the time |
| 2 weeks | Good balance between delivery and feedback | Requires well-refined backlog items |
| 3 to 4 weeks | Room for larger features | Slower feedback, higher risk of drifting |
Whatever the length, it should stay constant so the team can measure its pace and make reliable forecasts.
The Scrum events inside a sprint
Sprint planning
At the start, the team defines the sprint goal, selects items from the product backlog and plans how to deliver them. The Scrum Guide timeboxes it to a maximum of eight hours for a one-month sprint, and usually shorter for shorter sprints.
Daily Scrum
A 15-minute daily meeting where developers inspect progress toward the sprint goal and adapt their plan for the next day.
Sprint review
At the end, the team demonstrates the increment to stakeholders, collects feedback and updates the product backlog. This is the key meeting for the client.
Sprint retrospective
The team reviews how it worked (people, tools, process, definition of done) and chooses improvements for the next sprint.
Backlog refinement, the ongoing work of clarifying and estimating upcoming items, also happens during the sprint so that the next planning runs smoothly. The roles involved in each event are described in our article on Scrum roles.
Sprint artifacts and deliverables
- Product backlog: the ordered list of everything that might be needed in the product.
- Sprint backlog: the sprint goal, the selected items and the plan to deliver them.
- Increment: the working, tested result of the sprint, meeting the definition of done.
As a client, you should also expect a demonstration at the sprint review and a short report: what was delivered, what was not and why, and the priorities for the next sprint.
What happens inside a sprint, step by step
At Euro Tech Conseil, each sprint follows ten steps, from requirements and risk analysis to planning the next sprint:
- Requirements and risk analysis
- Conception
- Unit testing
- Development
- Running test scenarios
- Deployment to the test environment
- Test
- Feedback and validation
- Technical debt review
- Planning the next sprint
The full process is detailed on our Agile Scrum development methodology page.
Good practices for effective sprints
- One clear sprint goal rather than a list of unrelated tasks.
- Well-refined backlog items with acceptance criteria before planning.
- A shared definition of done that includes testing and code review.
- Protect the sprint: avoid adding new work mid-sprint unless the goal becomes obsolete.
- Attend the sprint review: client feedback is what keeps the product on track.
To compare this iterative way of working with a sequential approach, read Agile vs Waterfall.
Frequently asked questions
What is the ideal sprint length?
Two weeks suits most software projects, but the best length is the one that gives your team and stakeholders regular feedback without too much overhead.
Can a sprint be cancelled?
Yes, but only by the product owner and only if the sprint goal becomes obsolete, for example after a major change in business priorities.
What is the difference between a sprint and an iteration?
A sprint is the Scrum name for an iteration: a fixed time period that ends with a working increment.
Can we change priorities during a sprint?
Priorities for upcoming sprints can change at any time in the product backlog. The current sprint backlog should stay stable so the team can reach its goal.
Want to see working software every two weeks? Euro Tech Conseil, a Paris-based software development company since 2000, runs projects in Scrum sprints with full visibility. Discover our Agile software development services or contact our team.