Skip to main content
Scrumagic
Start free Dashboard

For developers

Learn why Scrum asks developers to estimate and commit, by doing it.

Cast your own planning poker vote, break the work into tasks, commit the sprint, and sit through the standup, the review and the retrospective, with a team that behaves like a real one.

Start the Developer simulation Go to your dashboard See the whole journey

Free plan · No credit card

18 steps · 5 phases · 8 scenarios

The team formation workshop from the Developer seat: the learner sits in the meeting beside the Product Owner, the Scrum Master and the other developers, with a first line ready to post.

1/6 Join the team: AI teammates talk the work through in character.

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

Sound familiar?

  • Ceremonies feel like overhead when nobody has explained what each one is for.
  • Estimating feels arbitrary until you have to defend a number to the rest of the team.
  • You are about to join your first Scrum team and have never seen a whole sprint from the inside.

What you get

Practice that fits the Developer seat

  • Estimate together and defend your number

    You cast your own planning poker vote, hear why the others voted differently and revise, and the team records its consensus.

  • See what each event is for

    Sit through the planning, the daily standup, the review and the retrospective as one of the developers, and watch how each one changes what the team does next.

  • Commit to what the team can really deliver

    You confirm the task estimates and commit the sprint against the team's capacity, then freeze the baseline so the scope cannot creep.

Phase by phase

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

You take a developer seat for the whole run, and the project unfolds in front of you in order: from the first workshops to the release. You are at the table for most steps, and the few that happen before you join are marked.

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

    Initiate

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

    The Sponsor and the Product Owner shape the vision and confirm the roles before you join. You come in when the team is formed.

    Steps in this phase

    1. 1.1 Create project vision & charter Workshop Not at the table
    2. 1.2 Identify Scrum Master & business stakeholder(s) Workshop Not 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

    • Join the team formation and agree how the team will work together.
    • Take part in the workshop that turns the vision into epics, and help rank the backlog by value and risk.
    • Help agree the Definition of Done, then plan the release with the team.

    Decisions that are yours

    None in this phase: the AI team decides in front of you, and you see why.

    You practise

    • Risk management
    • Definition of Done
  2. 02

    Plan and Estimate

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

    This is the developers' phase: the team turns the top of the backlog into a sprint it can honestly commit to.

    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 with the team.
    • Cast your own planning poker vote, hear the others, revise and reach consensus, then commit the sprint against the team's capacity.
    • Break the committed stories into tasks, map what depends on what and estimate each task in hours.
    • Claim your tasks and freeze the sprint baseline.
    Decisions that are yours (3)
    • How much do you commit the team to this sprint?
    • 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 and you see what keeps it on track.

    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

    • Work through the board on the representative day, where impediments, risks and change requests surface.
    • Take your place at the daily standup, where each developer reports what is done, what is next and what blocks them.
    • Sit in the backlog refinement session where a mid-sprint change request is triaged for a future sprint.

    Decisions that are yours

    None in this phase: the AI team decides in front of you, and you see why.

    You practise

    • Impediment handling
    • Risk management
  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.

    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

    • Demonstrate the increment with the other developers to the Sponsor, and see the Product Owner accept or reject each story against the Definition of Done.
    • Take part in the Start, Stop and Continue retrospective and the team's top improvements.

    Decisions that are yours

    None in this phase: the AI team decides in front of you, and you see why.

    You practise

    • Honest demos
    • Quality gates
  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.
    • Look back with the whole team on the value delivered and the technical lessons.

    Decisions that are yours

    None in this phase: the AI team decides in front of you, and you see why.

    You practise

    • Contract stability
    • Release planning

Through the Developer’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.

  • Advanced API 4 sprints $70,000 budget Start here

    Logistics API

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

    As a Developer: A breaking change costs a partner a sprint they did not plan, and that is the sentence to say out loud when someone asks for a simple rename. Keep the docs and the implementation in step by failing the build when they disagree, report a blocker the day you see it, and demo with real calls from a client that looks like the partner's, not with a mocked response that cannot be wrong.

  • 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 Developer: The payment work is the riskiest thing you build, so say so early and put honest hours on it. Report a blocker at the standup the day it appears, and demo only what meets the Definition of Done, so that "done" means what a tutor or a family could really use.

  • Advanced Mobile app 5 sprints $120,000 budget Start here

    Mobile Banking App

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

    As a Developer: A money-moving story is done when it has been reviewed by a second developer, security-tested and written to the audit log, and not before. Say so when you demo it, report the pen-test finding the day you see it and not the day it is asked for, name the sandbox and the licence as blockers instead of working around them, and choose the staged rollout and the way back before the release rather than during it.

  • 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 Developer

    A story that looks like a lookup can hide a week of work: when the courier's rules arrive by zone and weight, say so and put honest hours on it. Report the missing payment keys at the standup, and demo with real product photos, not placeholders, so that "done" means what a customer would see.

  • 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 Developer

    A demo on a simulator proves very little about a phone in someone's hand. Say early when battery use or the notification permission looks risky, estimate the offline sync as the hard problem it is, and show your work on a real device. A store release cannot be quietly taken back, so prepare it as one that will not need to be.

  • Intermediate Web app 4 sprints $35,000 budget

    Donation Portal

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

    What it asks of a Developer

    A gift page is a promise about people's money. Put the card-testing risk on the table before the first release, estimate the retry for failed monthly payments with real hours, plan the volunteer developer's work in small pieces that survive an away week, and raise the donor who needs large text before a reviewer has to. Demo what is finished and say what is not.

  • 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 Developer

    Report what the data does the moment you see it: the records with no discharge time, the extract that arrived with names in it, the table that is a day out of date. Estimate ingestion with the real extract in mind and not the sample, demo on the real data and say what it cannot yet do, and never let a chart that looks right stand in for a number you have checked.

  • Expert Migration 6 sprints $128,000 budget

    Legacy Migration

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

    What it asks of a Developer

    Port the rules, do not rewrite them: fifteen years of billing is in the stored procedures, and the way to keep it is to prove each rule against a test that captures what the old system did. Report a parity mismatch the day you see it, say what share is explained and what is not, and write down what the retiring engineer knows while he is still in the building.

See every project in detail

Skills you build

What you practise, and where

How it works

  1. 01

    Pick a project and the Developer 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.

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.

Who are the AI teammates?

Five named characters, each with a fixed role and personality, who remember your earlier decisions during a run. A large language model, reached through OpenRouter, writes their lines, and the model behind them can change as better ones appear. The process, the decision options and the scoring are fixed rules in our code, so a score never depends on how a model answered that day.

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 Developer seat. Your AI team is waiting.

Start the Developer 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.