Scrum for Beginners: Running Your First Sprint
November 18, 2026 · 12 min read

Scrum is the most widely used agile framework for software development, but if you are new to it, the vocabulary can feel overwhelming: sprints, backlogs, product owners, increments and retrospectives. The good news is that Scrum itself is simple. The official rulebook is short, and you can run your first sprint within a couple of weeks.
This Scrum for beginners guide explains the essentials in plain English, then walks you step by step through planning and running your first sprint, with a sample two-week sprint calendar, a Definition of Done checklist and the mistakes new teams make most often.
Scrum for Beginners: What Is Scrum?
Scrum is a lightweight framework for building complex products in short, repeated cycles called sprints. Instead of planning an entire project upfront, a Scrum team picks the most valuable work, builds it within a sprint, shows the result to stakeholders and uses what it learns to plan the next sprint.
Scrum is defined in the Scrum Guide, written by its creators Ken Schwaber and Jeff Sutherland and last updated in 2020. It is based on empiricism, meaning decisions are made from what is observed rather than what is assumed, and on three pillars: transparency, inspection and adaptation.
Scrum is one way to put agile values into practice. If you are still deciding whether agile is right for your project, read our comparison of agile vs waterfall first.
Scrum at a Glance: Roles, Events and Artefacts
| Element | What It Is |
|---|---|
| Product Owner | Maximises the value of the product and owns the Product Backlog |
| Scrum Master | Helps the team understand and apply Scrum, and removes obstacles |
| Developers | The people who build a usable increment each sprint |
| Sprint | A fixed-length cycle of one month or less in which the work is done |
| Sprint Planning | Starts the sprint by deciding why, what and how |
| Daily Scrum | A 15-minute daily check on progress towards the Sprint Goal |
| Sprint Review | The team shows the results to stakeholders and gathers feedback |
| Sprint Retrospective | The team reflects on how it worked and plans improvements |
| Product Backlog | An ordered list of everything that might be needed in the product |
| Sprint Backlog | The Sprint Goal, the selected backlog items and the plan to deliver them |
| Increment | A usable piece of the product that meets the Definition of Done |
The Three Scrum Roles (Accountabilities)
A Scrum Team is small, typically 10 or fewer people, so that it can stay nimble and communicate easily. It includes one Product Owner, one Scrum Master and the Developers. There are no sub-teams or hierarchies.
Product Owner
The Product Owner decides what the team works on and in what order. They create and order the Product Backlog, explain items clearly and make sure the work delivers value to users and the business. The Product Owner is one person, not a committee. In client projects, this is often someone on the client side, or a product manager who works closely with the client.
Scrum Master
The Scrum Master is responsible for the team's effectiveness. They coach the team on Scrum, facilitate events when needed, help remove blockers and protect the team from distractions. The Scrum Master is not a traditional project manager who assigns tasks; the team organises its own work.
Developers
"Developers" in Scrum means everyone who builds the product increment: programmers, designers, testers, DevOps engineers and so on. They create the plan for each sprint, hold each other accountable and make sure their work meets the Definition of Done.
The Five Scrum Events
The Scrum Guide sets a maximum length, called a timebox, for each event. Here are the limits for a one-month sprint; for shorter sprints, the events are usually shorter:
| Event | Purpose | Timebox (One-Month Sprint) |
|---|---|---|
| Sprint | The container for all the other events | One month or less |
| Sprint Planning | Agree the Sprint Goal, select the work and plan how to do it | Maximum 8 hours |
| Daily Scrum | Inspect progress and adjust the plan for the next day | 15 minutes |
| Sprint Review | Show the work to stakeholders and adapt the backlog | Maximum 4 hours |
| Sprint Retrospective | Improve how the team works | Maximum 3 hours |
Product Backlog refinement, where the team breaks down and clarifies upcoming items, is an ongoing activity rather than a formal event.
The Three Scrum Artefacts and Their Commitments
Each artefact has a commitment that gives it focus:
- Product Backlog and the Product Goal: the long-term objective the product is working towards.
- Sprint Backlog and the Sprint Goal: the single objective for the sprint, which gives the team flexibility in exactly what it builds.
- Increment and the Definition of Done: the quality standard every piece of work must meet before it counts as done.
Before Your First Sprint: Setting Up
1. Form the team and agree the roles
Name the Product Owner and the Scrum Master, and confirm who the Developers are. Make sure the Product Owner has the authority to make decisions about priorities.
2. Define a Product Goal
Write one or two sentences about what the product should achieve. For example: "Launch a customer portal that lets clients track orders and download invoices without calling support."
3. Build the initial Product Backlog
List features, improvements and fixes as backlog items, often written as user stories. Put the most valuable items at the top. The items for the first one or two sprints should be small and clear; items further down can stay rough. If you already have a software requirements document, it is a great source for your first backlog.
4. Agree the Definition of Done
Decide what "done" means for every item. Here is a simple starting checklist:
- The code is written and reviewed by another developer
- Automated tests are written and passing
- The acceptance criteria are met and checked by the Product Owner
- The feature works on the agreed browsers and devices
- The code is merged and deployed to a staging environment
- Any necessary documentation is updated
5. Choose your sprint length
Two weeks is the most popular choice for beginners. It is long enough to build something meaningful and short enough to get frequent feedback. Keep the length consistent, so the team develops a predictable rhythm.
6. Set up your tools
You can run Scrum with sticky notes on a wall, but most software teams use a digital board in a tool such as Jira, Linear, GitHub Projects or Trello. See our guide to the best project management tools for IT teams.
Running Your First Sprint: Step by Step
Step 1: Sprint Planning
The Scrum Guide organises Sprint Planning around three topics:
- Why is this sprint valuable? The Product Owner proposes how the sprint could increase the product's value, and the whole team agrees a Sprint Goal.
- What can be done this sprint? The Developers select items from the top of the Product Backlog that they believe they can complete.
- How will the chosen work get done? The Developers break the items into smaller tasks, often of a day or less.
For your first sprint, be conservative. You do not yet know your team's capacity, so it is better to finish everything and pull in more work than to overcommit. Scaled down in proportion to the one-month limit, Sprint Planning for a two-week sprint should take no more than about four hours.
Step 2: Estimate the work
Many teams estimate backlog items in story points, a relative measure of effort, complexity and uncertainty, using a sequence such as 1, 2, 3, 5, 8 and 13. A popular technique is planning poker: each person privately picks a card, everyone reveals at the same time and big differences lead to a short discussion. Other teams simply estimate in hours or days. Our guide to estimating software development time covers these techniques in depth.
Step 3: Hold the Daily Scrum
Every working day, at the same time and place, the Developers meet for 15 minutes to inspect progress towards the Sprint Goal and adjust their plan. Many teams discuss what they did yesterday, what they will do today and anything blocking them, but any format that focuses on the goal is fine. Detailed problem-solving happens afterwards, with only the people involved. For distributed teams, see our guide on how to manage a remote development team.
Step 4: Refine the backlog during the sprint
Set aside a little time mid-sprint to prepare items for the next sprint: clarify requirements, add acceptance criteria and split large items. This keeps the next Sprint Planning short and focused.
Step 5: Protect the sprint
During the sprint, no changes should be made that would endanger the Sprint Goal. If a stakeholder asks for something new, the Product Owner adds it to the Product Backlog for a future sprint. This discipline is one of the best defences against scope creep.
Step 6: Sprint Review
At the end of the sprint, the team presents what it achieved to stakeholders and discusses progress towards the Product Goal. This is a working session, not a slide presentation: show working software, gather feedback and update the Product Backlog together. For a two-week sprint, plan for up to about two hours.
Step 7: Sprint Retrospective
Finally, the Scrum Team discusses how the sprint went: what went well, what problems it faced and what to change. Choose one or two concrete improvements and add them to the next sprint. For a two-week sprint, plan for up to about 90 minutes.
Sample Two-Week Sprint Calendar
| Day | Activities |
|---|---|
| Day 1 (Monday) | Sprint Planning (up to 4 hours), then work begins |
| Days 2 – 5 | Daily Scrum (15 minutes); development and testing |
| Day 6 or 7 | Backlog refinement session (about 1 hour); Daily Scrum |
| Days 8 – 9 | Daily Scrum; finish, test and integrate the work |
| Day 10 (Friday) | Sprint Review (up to 2 hours) and Sprint Retrospective (up to 90 minutes) |
The timeboxes above are scaled down in proportion to the Scrum Guide's limits for a one-month sprint. They are maximums, not targets; experienced teams often finish sooner.
Measuring Your First Sprints
After each sprint, note how much work the team completed. Measured in story points, this is called velocity. After three or four sprints, your average velocity becomes a useful guide for planning and forecasting. For example, if the team completes an average of 30 points per sprint and 180 points remain in the backlog, the remaining work will take roughly six more sprints. Treat velocity as a planning tool for the team, never as a performance target or a way to compare teams.
Scrum vs Kanban: Which Should Beginners Use?
| Factor | Scrum | Kanban |
|---|---|---|
| Cadence | Fixed-length sprints | Continuous flow |
| Roles | Product Owner, Scrum Master, Developers | No required roles |
| Planning | At the start of each sprint | Whenever capacity becomes available |
| Change during a cycle | Avoided if it endangers the Sprint Goal | Allowed at any time |
| Best for | Product development with regular releases | Support, maintenance and unpredictable work |
For new product development, Scrum gives beginners a helpful structure. For support and maintenance teams with unpredictable incoming work, Kanban is often a better fit.
Common Mistakes New Scrum Teams Make
- Overcommitting in the first sprint: start small and build confidence.
- No real Product Owner: without someone empowered to decide priorities, the team stalls or builds the wrong thing.
- Turning the Daily Scrum into a status report for a manager: it is a planning meeting for the Developers.
- Skipping the retrospective: it is how the team improves; dropping it locks in bad habits.
- Items too big to finish: split work so each item can be completed within a few days.
- Changing the sprint length every sprint: consistency makes planning and velocity meaningful.
- "Done" that is not really done: untested or unreviewed work creates hidden debt.
Frequently Asked Questions
How long should a sprint be for beginners?
Two weeks is the most common starting point. The Scrum Guide only says a sprint must be one month or less, so one-week and three-week sprints also work. Pick a length and keep it consistent.
Can I learn Scrum without a certification?
Yes. The Scrum Guide is free and short, and most teams learn by doing. Certifications from organisations such as Scrum.org or Scrum Alliance can help, but you do not need one to run Scrum well.
What happens if the team does not finish all the work in a sprint?
Unfinished items go back to the Product Backlog, where the Product Owner reprioritises them. Use the retrospective to understand why, and adjust how much work the team takes on next time.
How many people should be in a Scrum team?
The Scrum Guide says a Scrum Team is typically 10 or fewer people, including the Product Owner and the Scrum Master. Larger groups should split into several teams working on the same product.
Is the Scrum Master a project manager?
Not in the traditional sense. A Scrum Master coaches the team and removes obstacles but does not assign tasks or own the scope. The Product Owner manages priorities, and the Developers plan their own work.
Can Scrum work for a client project with a fixed budget?
Yes. Fix the budget and the number of sprints, and let the Product Owner prioritise the backlog so that the most valuable features are built first. See our guide to MVP development cost for how to plan a first release within a budget.
Conclusion
As this Scrum for beginners guide shows, Scrum is simple to start: three roles, five events, three artefacts and a commitment to inspect and adapt. Set a clear Product Goal and backlog, agree your Definition of Done, start with a two-week sprint and keep your first commitment small. After a few sprints, your team will have a predictable rhythm, reliable forecasts and a product that improves every two weeks.
Want an experienced Scrum team to build your product? We run transparent two-week sprints with regular demos, so you see real progress and stay in control of priorities. Book a free consultation today.