4weird.com/docs/remastery/kanban-sprints · Wave 1

Kanban sprints, in plain English

Each squad gets a visual board at /squads/[id]/kanban: columns of cards you drag between stages, grouped into time-boxed sprints (cycles) with a progress bar. Status: planned — the board UI lane is building it now; nothing to click yet outside this guide.

How the planned board works

• Columns: stages like To do → In progress → Done. Drag a card from one column to another to change its stage.
• Cards: one unit of work — title, description, priority, hour estimate, due date, labels, assignee.
• Priorities: low, medium, high, urgent — urgent cards get the loudest badge.
• Estimates: each card carries an hour estimate (e.g. 2.5h) that feeds sprint progress and the time tracker.
• Sprints (cycles): a named window with start and end dates (e.g. “Sprint #4, ends in 3 days”) plus a 0–100% progress bar computed from finished cards.
• Keyboard + pointer: cards are draggable by mouse/touch and movable by keyboard.

Data shapes (planned schema)

Access is squad-scoped: board owners and squad members only (planned RLS). Cards can link to time entries, so logged hours roll up against the card's estimate.

FAQ

• Is there a board I can open today? Not yet — /squads/[id]/kanban is planned. Squad project lists live at /squads.
• Do estimates move coins? No. Estimates are planning numbers; only the guarded checkout moves coins.
• Who can move cards? Squad members on that board (planned permission rule).
• How is sprint progress computed? From finished cards against the cycle total: done estimates divided by planned estimates, shown as 0 to 100 percent.
• What happens to unfinished cards? They roll into the next cycle with fresh positions; the closed cycle keeps its history.
• Where do logged hours appear? Time entries linked by card id show beside the estimate; see the time tracking guide.

Running your first sprint in five steps

1. Name the sprint and fix the dates. One active cycle per board: a title plus a start and end date, for example "Sprint 4, March 3 to March 16".
2. Write cards small. One card per shippable slice with a verb first: "Wire raid lobby presence", not "Lobby stuff". Small cards finish; vague cards linger.
3. Estimate in hours, then assign. Every card gets an hour number and exactly one owner. Unowned cards rot in todo; owned cards move.
4. Drag daily, review weekly. Move cards as work lands so the board mirrors reality. At review, demo done cards, roll leftovers forward, and retire blockers in the open.
5. Close honestly. Mark the cycle complete, keep its history readable, and open the next cycle from the rolled-over remainder. Velocity is what you finished, not what you planned.

Worked example: Sprint 4

The GraveGain raid squad plans 14 hours across six cards. Midweek the board looks like this:

Done estimates total 7.5 of 14 planned hours, so progress reads 54 percent. The squad demo covers the three done cards, the owner of the lobby card names a landing date, and the two todo cards roll into Sprint 5. Logged time is reconciled per card in the time tracker; the full board reference lives in the squad kanban reference.

Troubleshooting

• Progress bar frozen at zero? Done cards may be attached to a closed cycle. Reattach them to the active cycle and the bar will recalculate.
• Card will not drag? Confirm you are a member of the board's squad, then retry. Rejected moves mean the permission check failed, not that the card is cursed.
• Estimates always wrong? After two cycles, compare logged seconds per card against the guesses and re-estimate from actuals. Cards that miss twofold are usually three cards wearing a trench coat: split them.
• Too many cards in progress? Cap doing at two per person. Park the excess back in todo with owners and dates instead of starting everything at once.

Next: Squad workspaces · Time tracking · All docs