Sprint Planning Game

Goal

Plan a realistic 2-week sprint for a small cross-functional team. Items have competency requirements (which roles work on them) and duration in days. The team has fixed FE / BE / QA capacity and pre-existing time off and meetings — drag items into the timeline so the work actually fits.

The three card types

🔴 Sprint Goal candidates 🟠 Important 🟢 Nice-to-have

Each card label shows the competencies it spans (e.g. FE+QA · 3d) — placing it occupies those rows for the given number of days. A sprint must commit to exactly one 🔴 Sprint Goal item.

Blocked cells (real availability)

Striped cells on the timeline are not available for sprint work — the time is already committed:

PLANSprint Planning (Mon, all roles)

CONFQA conference (mid-sprint)

OFFBE planned time off

REVIEWSprint Review + Retro (Fri, all)

Capacity & bottlenecks

Total capacity = sum of non-blocked cells across FE, BE, QA. Healthy total commitment is 80–90%, but watch the per-competency bars — a single role at 100% is a bottleneck even if the total looks fine. The constraint dominates, not the average.

Steps

1

Drag a 🔴 Sprint Goal item onto the timeline first — pick exactly one.

2

Items snap to their required competency rows. Position horizontally to choose which days the work happens.

3

Add 🟠 Important items that support the goal. Watch competency utilization, not just total.

4

Fill remaining capacity with 🟢 Nice-to-have if room is left in the right competencies.

5

Click Start Sprint to evaluate. The result shows per-competency bars and the lesson.

6

Click a placed block to pick it up again. Reset clears the board.

What you'll learn

Bottleneck-aware planning, why competency mix matters more than total points, and how real availability (meetings, conferences, time off) shapes what can actually fit.

Sprint Planning Game — Advanced

Sprint Timeline

Product Backlog