Key Takeaways
- A sprint is a repeatable loop: order the backlog, write small user stories, size them, plan, build, review and improve.
- The Scrum Guide gives sizing to the Developers and sets no fixed time for backlog refinement.
- Good stories are small enough for one sprint and come with acceptance criteria.
- Story points measure relative size, not hours. Use velocity to forecast, not to judge people.
- A retrospective only works if at least one improvement reaches the next sprint.
- RANIA Academy’s PMO-201 teaches these skills in 2 days, live online, from a launch price of $499.
Most teams don’t struggle with Scrum theory. They struggle in the first real sprint, when a messy backlog meets a fixed deadline. Stories are too big, estimates feel like guesses, and the retrospective turns into a complaint session.
This guide walks through a full sprint in seven practical steps. It covers how to order a backlog, write user stories, size work with story points, plan the sprint, run the Daily Scrum, and turn each retrospective into real improvement.
These are the skills taught in RANIA Academy’s PMO-201 Agile & Scrum Foundations course, part of the Project Management & Operations pathway. If you need the basics first, read our complete guide to the Agile Scrum foundation course in Australia, which explains the roles, events and artefacts. This article picks up where that guide stops: actually doing the work.
What does it mean to run a sprint in Scrum?
Running a sprint means working through a repeatable loop inside a fixed timebox of one month or less. The team refines the Product Backlog, plans the sprint around a Sprint Goal, inspects progress daily, and closes with a Sprint Review and Retrospective. Each loop should produce a usable Increment and one improvement to how the team works.
The Scrum Guide, written by Ken Schwaber and Jeff Sutherland, defines the framework. It deliberately leaves the tactics to the team. The table below shows where the practical work sits.
| Stage | What happens | Output | Typical failure |
|---|---|---|---|
| Backlog ordering | Product Owner orders items toward the Product Goal | Ordered Product Backlog | The backlog is a wish list |
| Refinement | Items are clarified, split and sized | Items ready for selection | Vague, oversized items reach planning |
| Sprint Planning | Team agrees why, what and how | Sprint Goal and Sprint Backlog | Overcommitment |
| Daily Scrum | Developers adapt the plan toward the goal | Updated plan for the next 24 hours | A status report to a manager |
| Sprint Review | Team and stakeholders inspect the Increment | Adapted Product Backlog | A demo with no feedback |
| Retrospective | Team inspects its own process | One concrete improvement | Complaints with no action |
Notice that the loop starts before the sprint does. Most sprints are won or lost during backlog work, not on day one.
Step 1: Build and order the Product Backlog
The Product Backlog is an ordered list of what the product needs. The Product Owner is accountable for it. The Scrum Guide ties it to a single Product Goal, which is the future state the team is working toward.
Ordering matters more than listing. Put the items that deliver the most value, or remove the most risk, at the top. Many teams use a simple technique such as MoSCoW (must, should, could, won’t) or a value-versus-effort grid. Scrum doesn’t require either one. Pick one and apply it consistently.
Keep the top of the backlog small, clear and detailed. Keep the bottom rough. Detailed work on items you won’t touch for months is mostly wasted effort.
Step 2: Write user stories the team can build
A user story describes a small piece of value from the user’s point of view. The classic format is:
As a [type of user], I want [a goal], so that [a benefit].
Illustrative example for a council booking site: “As a resident, I want to book a community meeting room online, so that I don’t have to phone during business hours.”
Next, add acceptance criteria. These are the conditions that prove the story works. Many teams write them in Given/When/Then form:
- Given I have chosen an available room and time, when I submit my details, then I receive a booking confirmation.
- Given the room is already booked, when I select it, then I see the next available times.
Check every story against INVEST
The INVEST checklist, coined by Bill Wake, is a quick quality test for any story.
| Letter | Test | Ask yourself |
|---|---|---|
| I | Independent | Can we build it without waiting on another story? |
| N | Negotiable | Is the detail still open to conversation? |
| V | Valuable | Does a user or the business benefit? |
| E | Estimable | Do we understand it well enough to size it? |
| S | Small | Does it fit inside one sprint? |
| T | Testable | Do the acceptance criteria let us verify it? |
If a story fails “Small”, split it. Split by workflow step (search, book, pay, cancel), by rule variation, or by user type. Avoid splitting by technical layer, such as “build the database”. A layer delivers nothing a user can see.
Step 3: Refine the backlog
Quick answer: Backlog refinement is the ongoing work of breaking Product Backlog items into smaller, clearer pieces. The Scrum Guide treats it as a continuous activity rather than a formal event, and it sets no fixed time allocation. An item is ready for selection when the team can finish it within one sprint.
The Product Owner and Developers refine together. The Product Owner brings the value and priorities. The Developers bring the technical and delivery view. Older editions of the Scrum Guide suggested spending up to ten per cent of capacity on refinement. The 2020 edition doesn’t prescribe a figure, so treat ten per cent as a rough starting heuristic only.
Many teams also keep a “Definition of Ready” as a working agreement. That can help conversation. It isn’t a Scrum Guide artefact, and it shouldn’t become a rigid gate. Scrum.org makes the broader point that arriving at Sprint Planning with an unrefined backlog signals a problem upstream.
Step 4: Estimate with story points and Planning Poker
Quick answer: Story points measure the relative size of a backlog item, combining effort, complexity and uncertainty. They are not hours. Under the Scrum Guide, the Developers who will do the work are responsible for sizing. The Product Owner can help them understand trade-offs but doesn’t set the estimate.
Relative sizing works because people compare better than they predict. Saying “this story is about twice the size of that one” is easier than saying “this will take 11 hours”. Most teams score with a modified Fibonacci sequence (1, 2, 3, 5, 8, 13), because the growing gaps reflect growing uncertainty. Asana’s story points guide is a useful plain-English reference.
How Planning Poker works
- Pick a small, well-understood reference story and give it a value, such as 3.
- The Product Owner reads the next story. The Developers ask questions.
- Each Developer privately chooses a card, then everyone reveals at once.
- The highest and lowest voters explain their thinking. The team re-votes until estimates converge.
Planning Poker was popularised by Mike Cohn of Mountain Goat Software. Its value is the discussion, not the number. Revealing together stops one loud voice anchoring the group.
If a story keeps landing on 13 or higher, treat that as a signal to split it. That’s a common team heuristic, not a Scrum rule.
Is an estimate a commitment, and what is velocity?
No. An estimate is a forecast. Over several sprints, the points you actually finish give you a rough velocity. Use it to forecast how much might fit in a future sprint. Don’t use it to rank people or compare teams, because points mean different things on different teams. Velocity isn’t part of the Scrum Guide either, and other sizing methods exist, including T-shirt sizes and right-sizing. Scrum.org describes several.
Step 5: Plan the sprint
Quick answer: Sprint Planning answers three questions: why is this sprint valuable, what can be done, and how will the chosen work get done. The output is a Sprint Goal and a Sprint Backlog. It is timeboxed to a maximum of eight hours for a one-month sprint, and shorter for shorter sprints.
Start with the Sprint Goal. It is a single objective that gives the sprint coherence, such as “residents can book and cancel a room online”. Then the Developers select the items they believe they can finish and plan how to build them.
Be honest about capacity. Count leave and public holidays, which differ between Australian states and territories. Under-commit slightly. A team that finishes early can pull in more work. A team that misses its goal repeatedly stops trusting its own plan.
Step 6: Run the sprint: Daily Scrum and Definition of Done
The Daily Scrum is a 15-minute event for the Developers. Hold it at the same time and place each day. Its purpose is to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours. It is not a status report to a manager.
A visible board helps. Teams commonly use Jira, Trello or Azure DevOps. Build the habits first, then choose the tool. The Scrum Master’s job here is to help remove impediments and keep the events useful, not to assign tasks.
The Definition of Done is the shared quality standard every item must meet before it counts. Partly finished work doesn’t count. Scrum.org’s three steps to Done notes that an unclear Definition of Done or poorly sized items are common root causes when teams can’t deliver a Done Increment.
Step 7: Review the Increment and run a useful retrospective
| Sprint Review | Sprint Retrospective | |
|---|---|---|
| Looks at | The product Increment | The team’s own way of working |
| Who attends | Scrum Team and stakeholders | Scrum Team |
| Output | Feedback that adapts the Product Backlog | One or more concrete improvements |
| Maximum length (one-month sprint) | 4 hours | 3 hours |
In the review, show working product and invite feedback. Don’t present slides about intentions.
In the retrospective, use a simple format such as Start/Stop/Continue, then choose one improvement and make it visible. The Scrum Guide says the most impactful improvements should be addressed as soon as possible, and they can be added to the next Sprint Backlog. That is how continuous improvement becomes real.
Example: if stories kept spilling over last sprint, the improvement might be “split any story above 8 points during refinement”. That links the retrospective straight back to Steps 2 to 4.
Six common mistakes in a first sprint
- Planning from an unrefined backlog. Large, vague items make estimates meaningless.
- Treating story points as hours. Points are relative, so converting them to time defeats the purpose.
- Letting someone other than the Developers set estimates. The Scrum Guide gives sizing to the people doing the work.
- Adding scope mid-sprint without a trade-off. The Sprint Goal protects focus. Scope is renegotiated with the Product Owner as the team learns.
- Skipping the retrospective when busy. That removes the improvement loop.
- Having no shared Definition of Done. “Done” then means something different to each person.
How this plays out in Australian workplaces
If your team works on or alongside government digital services, agile delivery is the norm. The Digital Transformation Agency’s Digital Service Standard expects agencies to work in an agile way. Sprint skills are therefore directly relevant to many delivery roles.
Teams spread across states also face practical issues: public holidays, AEST and AEDT differences, and hybrid schedules that make a consistent Daily Scrum time harder. Agree these rules in your first retrospective rather than discovering them mid-sprint.
Many teams now use AI assistants to draft user stories and acceptance criteria. That can save time, but each draft still needs checking against INVEST and real user needs. Our guide to writing better AI prompts at work helps, and how AI is changing project management jobs shows where these skills are heading. If your sprints sit inside a wider transformation program, see why digital transformation projects fail and the Digital Transformation & Technology courses.
Where a foundations course fits
You can learn parts of this from the Scrum Guide and free articles. What a facilitated course adds is practice: writing stories, sizing them with other people, and planning a sprint with someone who can correct you in the moment.
PMO-201 Agile & Scrum Foundations maps directly onto this guide:
| PMO-201 learning outcome | Where it appears here |
|---|---|
| Agile mindset, values and principles | The reasoning behind the whole loop (see the Agile Manifesto) |
| Scrum roles, events and artefacts | Steps 3, 5, 6 and 7 |
| Backlogs, user stories and estimation | Steps 1 to 4 |
| Running sprints and continuous improvement | Steps 5 to 7 |
Course details: 2 days, 14 hours of learning, live online, intermediate level. The launch price is $499 AUD, and GST is not currently applicable. Weekday cohorts run Monday, Wednesday and Friday from 6:00 pm to 9:00 pm Sydney time (AEST/AEDT). Weekend workshops run Saturday from 9:00 am to 4:00 pm. Public intake dates are confirmed in the monthly timetable, so contact the team for the next one.
Please note: RANIA Academy courses are non-accredited professional development. They are not nationally recognised qualifications under the Australian Qualifications Framework, and RANIA Academy is not a CPD-accrediting body. Check whether your professional body accepts the course and how it counts the hours. If you want a formal Scrum credential, you will still need a separate exam from a body such as Scrum.org or Scrum Alliance. Our pillar guide compares the pathways.
Want the next intake dates?
Tell us your preferred format and we’ll confirm the next available intake. Ask for the next intake dates or call 0468 167 862.
What to learn after PMO-201
- PMO-101 Project Management Fundamentals (2 days, $449): useful if you came from an agile team and need the wider project view.
- PMO-202 Stakeholder Engagement & Communication (1 day, $299): strengthens Sprint Review conversations.
- PMO-301 Operations & Process Improvement (2 days, $499): extends retrospective thinking into wider operations.
- Professional Delivery & Change Leadership Series: a longer pathway for leading delivery and change.
- Employability & Career Readiness: communication, problem-solving and collaboration skills that Scrum teams rely on.
You can also browse the full course catalogue.
Training a whole team?
Teams learn Scrum fastest when they practise on their own backlog together. RANIA Academy can arrange in-house delivery or a customised program. Talk to an advisor or call 0468 167 862.
Frequently Asked Questions
How long is a sprint in Scrum?
A sprint is a fixed-length event of one month or less. Many teams choose two weeks. The length stays consistent so the team can build a reliable rhythm.
What should happen before the first sprint?
The team needs a Product Goal and an ordered, refined Product Backlog with enough items ready for selection. Then Sprint Planning can set a Sprint Goal.
Who writes the user stories?
The Product Owner is accountable for the Product Backlog and may delegate the writing. In practice, the whole Scrum Team contributes during refinement.
Do I have to use story points?
No. The Scrum Guide doesn’t require a specific technique. Developers are responsible for sizing, and teams may use story points, T-shirt sizes or right-sizing.
How much time should backlog refinement take?
The 2020 Scrum Guide sets no fixed allocation. Older editions mentioned up to ten per cent of capacity, which some teams still use as a rough heuristic.
What is the difference between a Sprint Review and a Retrospective?
The Review inspects the product Increment with stakeholders. The Retrospective inspects the team’s own process and produces improvements.
Can I learn Scrum without a certification?
Yes. A foundations course builds working knowledge of backlogs, stories, estimation and sprints. A formal credential such as PSM or CSM needs a separate exam.
What does PMO-201 cover and cost?
PMO-201 covers Agile values, Scrum roles, events and artefacts, backlogs, user stories, estimation, and running sprints. It runs 2 days live online at a $499 launch price. Contact the team for the next intake.
Disclaimer: Course content, pricing, learning hours, delivery modes and dates are indicative and may be updated by RANIA Academy. Please confirm current details at the time of enrolment. Descriptions of the Scrum Guide and third-party frameworks are summaries, so check the original sources before relying on them for a professional decision.

0 Comments