Plan one sprint. Drag work from the Product Backlog into the Sprint Capacity grid. Each block represents a backlog item; its size in cells equals its story points.
The three card types
🔴 Sprint Goal candidates🟠 Important🟢 Nice-to-have
A sprint must commit to exactly one 🔴 Sprint Goal item. 🟠 Important items support the goal. 🟢 Nice-to-have fills capacity if room remains, but should not crowd out 🟠.
Capacity
The grid is 40 points (8 columns × 5 rows). Healthy commitment is 80–90% — leave buffer for the unexpected (bugs, sick days, scope discoveries), but don't under-commit either.
Steps
1
Drag a 🔴 Sprint Goal block into the grid first — pick exactly one.
2
Add 🟠 Important items that support the goal.
3
Fill remaining capacity with 🟢 Nice-to-have only if room is left.
4
Click Start Sprint to evaluate your plan and read the lesson.
5
Click a placed block to pick it up again. Reset clears the board.
What you'll learn
Why a sprint should have a single focused goal, the sweet spot for capacity utilization, and why "fits" is not the same as "matters" when prioritizing.