You'll see columns — typically Backlog, To Do, In Progress, and Done — and the ability to create cards and drag them between columns.

Don't overthink this — something simple works fine.

Cover a mix of work types, and give each card a short, specific title — not "Fix stuff."

Drag your top 2–3 cards to the top of the Backlog column. Ask yourself honestly: if you could only do one of these this week, which would it be, and why?

This is the moment of "sprint planning" — deciding what you're committing to work on next, as opposed to everything you'd eventually like to do.

Move a card to In Progress when you'd genuinely be working on it, and to Done only when it's genuinely finished — not "basically finished."

Resist moving three or four cards into In Progress at once. Real agile teams find this one of the hardest habits to keep — unfinished work in progress is invisible progress, and it hides problems.

Turn "looks finished" into something specific and checkable.

Save it once it reflects a realistic small sprint — a handful of prioritised cards, a small To Do, and clear acceptance criteria.

Create 10–12 cards for your fictional product, spanning features, bugs, and chores — enough variety that not everything can obviously fit in one sprint.

Read through your backlog and pick the 5–6 cards you genuinely believe are small enough to finish in one sprint. Move only those into To Do — leave the rest in Backlog on purpose.

Even a few minutes apart counts as a "day" of the sprint. Move cards through In Progress to Done as you complete each one — resist moving everything at once at the end.

Pick one card and don't finish it for a while, the way real work sometimes stalls on a dependency or unexpected complexity.

At the end of the sprint: how many of your original 5–6 planned cards genuinely reached Done? Write the number down — use the tracker in the demo below to see it worked out for you.

Were the cards too big? Did something unplanned interrupt you? Did you plan too optimistically? There's no wrong answer — the goal is noticing, not judging yourself.

Look back: how many cards did you plan for that sprint, and how many actually reached Done? That completion ratio is a rough personal "velocity" — a measure of how much realistic work you can actually get through in a sprint.

Write down, honestly:

Build a fresh backlog (or reuse leftover cards from Lab 2), and this time actually apply your retro change — for example, planning fewer cards, or splitting big cards before the sprint starts.

Move cards through the columns as real work would progress, and let it run over more than one sitting.

Count planned vs. finished, exactly as you did in Lab 2. Use the calculator below to compare both sprints side by side.

It's fine if the answer is "not really" — that's still a useful, real finding, and it's exactly what a real retro is for.

Save this as your final project for this tool.