Sprints you can see move.

1. 1

   Open a cycle

   Name the sprint, set start and end dates, mark it active. One active cycle per board keeps progress math honest.
2. 2

   Fill the columns

   Cards start in todo with priority, estimate, due date, and an assignee. Drag toward done as work lands — positions persist per column.
3. 3

   Track against cards

   Contributors clock time linked to card_id, so the board shows actuals beside estimates while the sprint runs.
4. 4

   Close and convert

   At cycle end, completed cards stay as history; remaining estimates roll into the next cycle, and unbilled hours become a draft invoice.

Done estimates total 7.5 of 14 planned hours, so the cycle bar reads 54 percent. The doing card holds the risk: one high priority item with a named owner and a due date beats three unowned cards every time. At review the squad rolls the two todo cards into week 2 and converts the 7.5 unbilled hours toward a draft invoice. Prefer plain English? Read the kanban sprints guide, then reconcile logged hours in the time tracker.

1. 1

   Cycle progress reads zero

   Finished cards may sit outside the active cycle. Attach completed cards to the active cycle identifier, or close the stale cycle before opening the new one.
2. 2

   A dragged card snaps back

   Confirm squad membership first, then retry the move. The board persists positions per column, so a rejected write means the permission check or the position value failed.
3. 3

   Estimates always miss

   Compare clocked seconds per card across two full cycles, then re-estimate from those actuals. A chronic twofold miss means the card is secretly three cards: split it and estimate each slice.
4. 4

   Labels multiply without mercy

   Prune the label taxonomy monthly: archive synonyms, keep a tiny palette such as frontend, art, audio, and blocker. Filters stay useful only while the vocabulary stays small.