Updated 19 October 2026.
Scrum is a framework; a Sprint is an event within that framework. They are connected concepts, so you do not choose between them. Scrum describes how a team works together on complex problems. Sprints provide a consistent rhythm for creating value, inspecting what happened and adapting.
Scrum versus Sprint
| Question | Scrum | Sprint |
|---|---|---|
| What is it? | The overall framework. | A fixed-length event of one month or less within Scrum. |
| What does it contain? | Accountabilities, events, artefacts and commitments. | Sprint Planning, Daily Scrums, the work, Sprint Review and Sprint Retrospective. |
| What is the focus? | Creating value through an empirical approach. | Working towards the Sprint Goal and producing a useful Increment. |
| Who is involved? | The Scrum Team and relevant stakeholders. | The same Scrum Team, with stakeholder involvement where appropriate. |
The Scrum Guide defines the framework. Use it to check terminology and requirements when an informal explanation or older video differs.
What is Scrum?
Scrum helps people inspect real results and adapt their approach. A team makes its work and outcomes transparent so that decisions can respond to what is learned. A collection of meeting names alone does not create that feedback loop. Scrum.org’s introduction provides further context.
The Scrum Team is self-managing. Its three accountabilities are Product Owner, Scrum Master and Developers. The 2020 guide uses Developers rather than a separate Development Team. An organisation may have other job titles, but it needs to understand how their responsibilities relate to the framework.
What is a Sprint?
Sprints have a fixed length of one month or less. Two weeks is a common choice, not a universal requirement. A new Sprint begins after the previous one ends. Its length should provide consistency while allowing the team to learn soon enough to make useful decisions.
A Sprint is not a promise that every task first discussed will be completed regardless of new information. The Sprint Goal provides focus, and the plan can adapt as more is learned. Quality should not decrease. The Product Owner may cancel a Sprint if its goal becomes obsolete.
What happens during a Sprint?
Sprint Planning
The Scrum Team agrees why the Sprint is valuable, what work can be selected and how that work will be done. The Sprint Backlog contains the Sprint Goal, selected Product Backlog items and the Developers’ delivery plan. Past performance can inform a forecast; it does not guarantee the same output next time.
Daily Scrum
The Daily Scrum is a 15-minute event for Developers to inspect progress towards the Sprint Goal and adapt their plan. It is not a required status report to a project manager. The format can vary; three standard questions are not compulsory. Further discussion can happen afterwards. See Scrum Alliance’s Daily Scrum guidance.
Sprint Review
The Scrum Team and stakeholders inspect the Sprint’s outcome and discuss what to do next. It is a working conversation about results and changed circumstances, not simply a presentation or a mandatory release approval. Useful work can be released before the review. Scrum.org’s review guidance explains how to prepare for the conversation.
Sprint Retrospective
The Scrum Team examines how it worked and identifies improvements. Make an improvement concrete enough to try: who will do something differently, when and what evidence would show that it helped? A retrospective has little value if the same issues return without action.
How long do the events take?
For a one-month Sprint, the Scrum Guide sets maximum timeboxes of eight hours for Sprint Planning, four for Sprint Review and three for the Retrospective. These events are usually shorter for shorter Sprints. The Daily Scrum remains 15 minutes. Do not treat a maximum as time that must always be filled.
Illustrative example: improving a customer application
Suppose a team wants to help customers complete an online application. Its Product Backlog contains several possible improvements. During planning, the team chooses a Sprint Goal focused on helping users understand what information they need before starting.
Developers select suitable work, plan it and adapt their plan as they learn. If an assumption proves wrong, they discuss the implications with the Product Owner. They keep the goal in view while adjusting the detail.
At the review, the team and stakeholders examine the outcome and new information. They may learn that customers need a different explanation or that an accessibility issue deserves attention. In the retrospective, the team considers how its own working approach could improve. This is an illustrative workflow, not a measured customer case study.
What a project manager should avoid
- Using the Daily Scrum to collect individual status reports for a separate audience.
- Treating historical velocity as a guaranteed commitment or an individual productivity score.
- Assuming that completing a Sprint proves a business benefit has been realised.
- Treating the Sprint Review as the only time stakeholders may provide feedback.
Agree how wider project governance connects to the team’s work. A sponsor update can explain milestones, risks and decisions without changing the purpose of Scrum events. Keep the source information traceable and distinguish a forecast from an approved commitment.
The practical distinction
Use “Scrum” when referring to the framework and “Sprint” when referring to one of its repeating periods of work and learning. If a conversation becomes confusing, ask which goal, decision or event is being discussed. That is usually more useful than adding more terminology.
Put It Into Practice
Pick one thing from this article to try on your next project. If you need a starting point, Resources has free status report, action log and decision log templates. For a difficult conversation, try the People Field Guide.
Get new practical guides by email →
About Paulius
I’m Paulius Petravicius, a project manager with a background in business and data analysis. I share practical ways to make everyday project work a little easier. Read my story →