Running a sprint
Day-by-day rhythm for a two-week cycle, from planning meeting to retro.
Monday of week 1 — planning
Open the Cycles page and move the upcoming cycle to active. Open the backlog (task list filtered by cycleId = null) and drag tasks into the cycle by setting cycleId. Be honest about capacity — a cycle overloaded on day one is a cycle that slips.
End planning when the team agrees on a committed set. Anything you add mid-cycle is a stretch, not a commitment.
Daily — standup on the board
Open the cycle page and switch to Board view grouped by status. Walk the board right-to-left: done, in_progress, todo. For each in-progress task, owner answers “what's the next step?” — not “what did I do yesterday.” Keep it under 10 minutes.
Mid-cycle — check the burn
Open the cycle's Gantt view around day 5. If the “done” column is suspiciously empty, raise it early. Mid-cycle is when you can still cut scope — end of cycle is when you're writing apologies.
Move anything clearly not landing to the next cycle by updating cycleId. Don't leave it in the active cycle and let it roll silently.
End of cycle — close and retro
On the final day, move the cycle to completed. Based keeps the record — you can always look at who shipped what and when.
Open the cycle page and use the embedded doc area to write the retro. A simple three-column structure works: what went well, what didn't, what to change. Link to specific task records as evidence — the back-links let you revisit the story later.
Unfinished tasks
When a cycle closes with tasks still in todo or in_progress, decide per-task: bump to the next cycle, send to the backlog, or cancel. “Carry everything forward” is the default that rots a backlog — be willing to cancel.