Skip to main content
Scrumagic
Start free Dashboard

For Scrum Masters

Practice facilitating Scrum before your first real team.

Scrum Master practice, not revision: run standups, planning poker and retrospectives with five AI teammates who push back. Protect the sprint goal, clear impediments, and see the result on your scorecard.

Start the Scrum Master simulation Go to your dashboard See the whole journey

Free plan · No credit card

18 steps · 5 phases · 8 scenarios

The ceremony workbench mid-debate: named AI teammates talk through the sprint in chat bubbles while the learner, as Scrum Master, prepares a reply.

1/5 Run the ceremony: your AI teammates argue their case, in character.

Screens from the real product, taken with a demo account.

Sound familiar?

  • You are studying for a Scrum Master certificate, and the questions describe situations you have never been in.
  • You know the vocabulary, but you have never facilitated a sprint where people disagree.
  • Your first real team is the worst place to practise: every mistake costs a real sprint.

What you get

Practice that fits the Scrum Master seat

  • Handle tangents and conflict in the room

    Teammates have their own personalities and push back in character. You keep each ceremony inside its timebox and clear a blocker the day it appears.

  • Facilitate estimation until the team agrees

    Developers vote, reveal and revise. You run the round, record the consensus and commit the sprint against the team's real capacity.

  • Protect the sprint when a sponsor wants more

    A sponsor pushes for one more feature. You take it to the Product Owner and hold the sprint as committed, and your scorecard records what you decided and why.

Phase by phase

Every step of a full Scrum project, from the Scrum Master's seat

You take the Scrum Master seat for the whole run, and every step happens in front of you, in order. You are at the table for all of them, and the decisions that belong to your seat are yours.

steps, from vision to release
18
of them with you at the table
18
decisions that are yours to make; the AI team makes the rest in front of you
14
  1. 01

    Initiate

    Agree why the project exists, who is involved and what the first release must deliver.

    You were engaged when the project was approved. In this phase you help the Sponsor and the Product Owner turn an idea into a charter the whole team can work from.

    Steps in this phase

    1. 1.1 Create project vision & charter Workshop At the table
    2. 1.2 Identify Scrum Master & business stakeholder(s) Workshop At the table
    3. 1.3 Form Scrum team Workshop At the table
    4. 1.4 Develop epics & personas Workshop At the table
    5. 1.5 Create prioritized backlog & DoD Workshop At the table
    6. 1.6 Conduct release planning Planning At the table

    What you do

    • Ratify that the Product Owner and the Sponsor both endorse the vision and the charter.
    • Confirm who holds each role and who signs off what.
    • Help form the team and agree how it will work together.
    • Take part in the workshops that turn the vision into epics, and rank the backlog with the team.
    • Choose the sprint length when you plan the release.
    Decisions that are yours (5)
    • Do both the Product Owner and the Sponsor endorse the vision and the charter?
    • Do you confirm the roles and the sign-off matrix?
    • Do you ratify the roster and the team norms?
    • Do you approve the ranked backlog and the Definition of Done?
    • How long should each sprint be? The plan is locked once you confirm.

    You practise

    • Stakeholder management
    • Backlog ordering
    • Scope control
  2. 02

    Plan and Estimate

    Turn the top of the backlog into a sprint the team can honestly commit to.

    The team turns the top of the backlog into a sprint it can honestly commit to, and you run each session.

    Steps in this phase

    1. 2.1 Create user stories Working session At the table
    2. 2.2 Estimate & commit user stories Planning poker At the table
    3. 2.3 Identify tasks Working session At the table
    4. 2.4 Estimate tasks Working session At the table
    5. 2.5 Update sprint backlog Planning At the table

    What you do

    • Check the drafted user stories are ready, and catch the ones that hide defects.
    • Facilitate planning poker, record the team's consensus and commit the sprint against its capacity.
    • Make sure the tasks, their dependencies and the hour estimates add up before the team freezes the sprint baseline.
    Decisions that are yours (5)
    • Are these stories ready for planning?
    • How much do you commit the team to this sprint?
    • Do you confirm the tasks and their dependencies?
    • Do you confirm the task estimates?
    • Do you freeze the sprint baseline? The sprint scope cannot change afterwards.

    You practise

    • Estimation
    • Thin slicing
  3. 03

    Implement

    Keep the sprint on track: run the board, hold the standup and protect the sprint scope.

    The sprint is under way. You keep it on track and shield it from new scope.

    Steps in this phase

    1. 3.1 Create deliverables Working session At the table
    2. 3.2 Conduct daily standup Standup At the table
    3. 3.3 Refine prioritized backlog Backlog refinement At the table

    What you do

    • Check the board on the representative day and deal with the impediments, risks and change requests that surface.
    • Run the daily standup: each developer reports what is done, what is next and what blocks them, and you decide how to respond to a blocker.
    • Sit in the backlog refinement session where the Product Owner triages a mid-sprint change request while the current sprint stays as committed.
    Decisions that are yours (2)
    • What do you do about the impediments on the board?
    • How do you respond to the blocker that was reported?

    You practise

    • Impediment handling
    • Scope control
  4. 04

    Review and Retrospect

    Show what was built, decide what counts as done and improve how the team works.

    The sprint ends with a demonstration and a look back at how the team worked.

    Steps in this phase

    1. 4.1 Demonstrate & validate sprint Review At the table
    2. 4.2 Retrospect sprint Retrospective At the table

    What you do

    • Sit in the review while the developers demonstrate the increment to the Sponsor and the Product Owner accepts or rejects each story.
    • Facilitate the Start, Stop and Continue retrospective and commit the team to its top improvements.
    Decisions that are yours (1)
    • Which improvements does the team commit to?

    You practise

    • Definition of Done
    • Honest demos
  5. 05

    Release

    Ship the working product and capture what the team learned.

    The product ships and the team closes the project.

    Steps in this phase

    1. 5.1 Ship deliverables Cutover At the table
    2. 5.2 Retrospect release Retrospective At the table

    What you do

    • Be at the cutover while the Product Owner authorises the release and the Sponsor accepts the deliverables.
    • Lead the project retrospective on the value delivered, the return on investment and the technical lessons, then close the project.
    Decisions that are yours (1)
    • Do you finalize the project? The scorecard is produced once you do.

    You practise

    • Release planning
    • Value visibility

Through the Scrum Master’s eyes

8 projects, and what each asks of you

Every project runs the same 18-step process. Only the fictional business, the stakes and the pressure on the team change.

  • Beginner Web app 4 sprints $45,000 budget Start here

    Tutor Booking Web App

    Take a tutoring collective from a sponsor's first request to a launch-ready booking app.

    As a Scrum Master: A Sponsor who asks for calendar sync three times is not an enemy: the Sponsor is afraid of looking behind the competition. Your job is to keep the sprint steady, take each idea to the Product Owner, and clear a blocker such as a full staging database the day it appears, so that no request has to be squeezed in.

  • Intermediate Web app 4 sprints $35,000 budget Start here

    Donation Portal

    Build a donation portal for a food bank where everyone has an opinion, and only a few get a vote.

    As a Scrum Master: Nobody on this project is the enemy, and almost everyone has an opinion. The sign-off matrix at the start is where the weeks ahead were won or lost: once it said who advises and who decides, every relayed request had a place to go. Keep taking them to the Product Owner, clear the processor's and the domain's blockers the day they appear, and keep the ceremonies short enough that volunteers can come to them.

  • Expert Migration 6 sprints $128,000 budget Start here

    Legacy Migration

    Replace a 15-year-old billing system with zero new features and a sponsor who cannot see progress.

    As a Scrum Master: On this project nothing looked different, and the hardest part of your job was making the work visible. A review that shows a new screen would have been a lie, so the review had to show numbers: rules matched, mismatches explained, the reconciliation variance falling. Protect the team from the request that arrives as a favour while you are rewriting anyway, and when the sponsor is nervous, give them the figures and not a feature.

  • Beginner Web app 4 sprints $40,000 budget

    E-commerce Storefront

    Help a family-run homewares shop go from craft-fair stall to launch-ready online store before the holiday rush.

    What it asks of a Scrum Master

    A sponsor with a new idea every week is not an enemy: the Sponsor is afraid of missing a date. Your job is to keep the sprint steady, take each idea to the Product Owner, and clear the small blockers, like missing payment keys, the day they appear, so that no request has to be squeezed in.

  • Intermediate Mobile app 5 sprints $60,000 budget

    Fitness App

    Ship an app-store-ready fitness app for an investor demo, with one very tempting risky feature.

    What it asks of a Scrum Master

    An investor can make a founder feel that every week without a new feature is a lost week. Shield the sprint by taking each request to the Product Owner, splitting it, and clearing the small blockers, like an account still being verified, the day they appear. Then nothing has to be squeezed in, and nothing waits on a store that cannot be hurried.

  • Advanced Mobile app 5 sprints $120,000 budget

    Mobile Banking App

    Launch a credit-union mobile app where "done" means secure, reviewed and auditable.

    What it asks of a Scrum Master

    On this project the date was never the only thing that could be wrong. A story can work and still not be done, and the team needs someone to say so out loud: the sandbox, the licence, the reviewer and the pipeline were all yours to clear the day they appeared. Keep the compliance requirement on the table when it arrives, keep the pen-test fix and the date in the same conversation at the review, and keep the ceremonies short enough that the people who must review a payment can still attend.

  • Advanced API 4 sprints $70,000 budget

    Logistics API

    Ship a partner-facing API where other people's code depends on every decision you make.

    What it asks of a Scrum Master

    On this project the customer is another team's code, and a change that looks small to you can stop their build. The blockers that mattered were the ones outside the team, the gateway quota, the partner's credentials and the sandbox that shared a database with staging, and they were yours to chase the day they appeared. When the status request arrived it did not need a yes or a no from you: it needed to go to the Product Owner with a size and a split, and the review needed to show real calls and not mocks.

  • Expert Data platform 5 sprints $108,000 budget

    Hospital Data Platform

    Deliver hospital operations dashboards where every story passes its tests and the data still lies.

    What it asks of a Scrum Master

    On this project the dashboards were the tip and the data was the iceberg, and the hardest work was the work nobody could see. Your job was to make it visible: to put the nursing and finance definitions of an occupied bed in one room, to clear the access and the masking problems the day they appeared, and to use the review to show the sponsor the checks, the gaps and the numbers, not just the charts. A review that shows only what looks good is the review that leads to a wrong number on a ward at seven in the morning.

See every project in detail

Skills you build

What you practise, and where

How it works

  1. 01

    Pick a project and the Scrum Master seat

    Choose one of 8 scenarios. The AI plays the other five roles.

  2. 02

    Go through all 18 steps

    Read the inputs, join the discussion and make the call at the decision gate. One new step unlocks each day, so there is time to think between sessions.

  3. 03

    Read your scorecard

    See how you did and why, export it as a PDF report, then try another seat or a harder project.

Plans

Start free. Upgrade when you're ready.

Payments by Paddle · 14-day refunds · Cancel any time · Prices exclude taxes where they apply

Full pricing and billing details

Questions people ask

What is Scrumagic?

Scrumagic is a browser-based Scrum training simulator. You take one role on a six-person team and run a fictional project from vision to release, while AI teammates play everyone else.

Is this a certification, or exam prep?

Scrumagic is not an official certification and it does not replace one. If you are studying for an exam, it gives you hands-on practice with the situations the questions describe. Beyond the exam, it builds practical knowledge and real experience of running a whole project, and your result is a scorecard, not a certificate.

How long does a run take?

It depends on the scenario and how many sprints it has. One new step unlocks each day, so a run unfolds over days, not in one sitting. Phase 1 has six steps, so it takes at least six days. Each scenario card lists its sprints and budget.

What do I get for free?

Phase 1 of any scenario, in any role, with no credit card. Phase 1 covers vision and charter through release planning. One new step unlocks each day, and Pro adds Phases 2 to 5.

How is my score calculated?

From the decisions you record: budget adherence, estimation accuracy, business value delivered and Scrum compliance. Fixed rules compute it, never how the conversation felt. When a run ends you can export the scorecard as a PDF report.

Which roles can I play?

Scrum Master, Product Owner or Developer. Every scenario can be played in all three, and the AI teammates play the other roles.

Practising another role?

Ready to run your first sprint?

Pick a project and take the Scrum Master seat. Your AI team is waiting.

Start the Scrum Master simulation Go to your dashboard

Free plan · No credit card

We use analytics cookies to see which pages help and which don't. Scrumagic works the same whichever you choose, and you can change your mind any time from "Cookie settings" in the footer. Privacy Policy.