The Lego City Sprint Exercise
Everything you've learned so far — Sprints, estimation, the Product Backlog, the Definition of Done — in one hands-on exercise. Grab a box of Lego, gather a few people, and build a city in short, timeboxed Sprints.
How the Exercise Works
The goal is to feel what it's like to estimate and plan work you've never done before — not to build a perfect city.
What You Need
A box of mixed Lego bricks, 3–6 participants, a flat building surface, a timer, and a printed or written-out version of the backlog below. Optionally, a Planning Poker deck (or our online Planning Poker tool) for estimating.
The Timebox
Each Sprint is exactly 15 minutes of build time, with a few minutes before for Sprint Planning and a few minutes after for Sprint Review. Run 2–4 Sprints so the team can feel how their estimates and velocity change over time.
Running a Session
- Introduce the backlog. Show participants the Epics and User Stories below — this is "Lego City", the product they're building together.
- Estimate as a team. Before the first Sprint, estimate each User Story using Planning Poker and a Fibonacci-like scale. Nobody has built with this exact backlog before — that's the point. Compare notes when estimates differ.
- Sprint Planning (2–3 min). The team picks a Sprint Goal and selects the User Stories they believe they can finish in the next 15 minutes.
- Sprint (15 min). Build! Stick to the Acceptance Criteria. If a story is finished early, pull in the next one from the Product Backlog.
- Sprint Review (2–3 min). Check each finished story against its Acceptance Criteria and the team's Definition of Done. Only count items that are truly "Done".
- Retrospective (2–3 min). What slowed you down? Was the estimate close? What will you do differently next Sprint?
- Repeat. Run another Sprint. Most groups notice their velocity becomes more predictable — and their estimates more realistic — after just one or two Sprints.
The Lego City Backlog
Five Epics, each with its own User Stories and Acceptance Criteria — the real backlog used in live sessions of this course. Order them by value, estimate them, and start building.
Epic 1: Transporting Materials Around the City
As a resident, I want to be able to move blocks and materials around the city.
User Story 1.1: Tractor
As a resident, I want a tractor so I can easily move things around.
User Story 1.2: Tractor Garage
As a resident, I want a garage for my tractor so it's protected from the weather.
Acceptance Criteria:
- – The garage has a door and 3 walls
User Story 1.3: Loading Crane
As a citizen, I want a crane so I can load materials.
User Story 1.4: Tractor Trailer
As a resident with a tractor, I want a trailer so I can load things onto it.
Epic 2: Attractive Places to Live
There is a need for attractive houses in the city to get new residents excited about moving here.
User Story 2.1: House with Garden
As a resident, I'd like a house with a garden out front so I can enjoy the sun in summer.
Acceptance Criteria:
- – The garden has a fence
User Story 2.2: Carport for the Car
As a homeowner, I want a carport next to my house so my car is protected from the weather.
Acceptance Criteria:
- – The car fits in the carport
User Story 2.3: Car
As a resident, I'd like a car so I can drive to work.
Acceptance Criteria:
- – At least 2 people fit in the car
Epic 4: Public Transport
The city must offer public transport, since not all residents own a car.
User Story 4.1: Bus
As a city resident, I'd like to ride the bus to get around the city without my own car.
Acceptance Criteria:
- – Several people fit in the bus
User Story 4.2: Bus Stop
As a city resident, I'd like a covered bus stop so I can stay dry while waiting for the bus in the rain.
Acceptance Criteria:
- – The stop has a bench
User Story 4.3: Double-Decker Bus
As the mayor, I'd like a double-decker bus so more passengers can be transported at once.
Acceptance Criteria:
- – The bus has 2 floors
Epic 5: City Infrastructure
The city needs basic infrastructure.
User Story 5.1: Road Network
As the mayor, I need roads so residents can get around quickly.
Acceptance Criteria:
- – Doesn't have to be built from Lego bricks
User Story 5.2: Pedestrian Bridge
As a pedestrian, I'd like a bridge to cross the busy roads.
Acceptance Criteria:
- – Two Lego figures can comfortably cross the bridge
User Story 5.3: A River
As the mayor, I'd like a river to improve residents' quality of life.
Acceptance Criteria:
- – Doesn't have to be built from Lego bricks
Epic 6: Recreational Facilities
As a resident, I'd like recreational facilities so life in the city gains quality.
User Story 6.1: Outdoor Pool
As a citizen, I'd like an outdoor pool with a diving board.
Acceptance Criteria:
- – Water doesn't have to be made of Lego
- – The pool has an edge to sit on
- – The diving board is on a tower (at least 2 figures tall)
That's the Whole Course
You've covered the Scrum framework, the Scrum Team and Events, the Artefacts and Commitments, and now a real exercise to practice estimation and sprint planning. The best way to make it stick is to run the Lego City exercise with your own team.
Course created by Željko Kvesić, based on Scrum training sessions held in person.