Skip to content

Sprint board

The sprint board is the Native execution surface for the current sprint: a column per status, a card per task. Moving a card updates status for everyone instantly.

Connect coding agent (on the board or Settings → API Keys & Agents) lets Cursor or Claude claim tasks, post ## Agent handoff comments, and mark DONE. Work one task at a time and confirm before claim.

In Connected mode, execution may live in Linear or Jira; agents must not overwrite tracker-synced status (TASK_SYNCED_READ_ONLY). Burndown, velocity, and retro views are not in the current product surface — use Team Analytics for basics.

  • View the active sprint as columns of status with a card per task.
  • Drag cards between columns to update status during standups or async work.
  • Open a card to edit its assignee, description, or add a comment.
  • Spot blocked items quickly and escalate them in comments.
  • Close out or complete the sprint once the time window ends.
  • Connect a coding agent and follow the sprint loop (one task per turn).
  • Connect a coding agent and follow the sprint loop (one task per turn).
  • Daily standups, to walk through what moved and what is blocked.
  • Continuous mid-sprint execution, whenever status changes.
  • End-of-sprint wrap-up, to confirm everything is in its final state.
  • A signed-in member account with product access.
  • A Planner seat to create or edit cards; Members can usually move their own assigned cards.
  • A confirmed sprint with items already in scope.
  • Sidebar: project Sprint board
  • Accessible from the project overview once a sprint is confirmed.
  1. Open the active sprint board under the relevant project.
  2. Scan columns to see current status distribution at a glance.
  3. Drag a card to the next column as its status changes.
  4. Open a card to edit the assignee, description, or leave a comment.
  5. Flag and comment on any item that looks blocked.
  6. Check in daily during standups to keep the board an accurate mirror of real progress.
  7. Close or complete the sprint once the time window ends.
  • The board reflects reality: nothing sits in a stale column for days without a comment.
  • Blocked items are visible and flagged, not silently stuck.
  • The sprint closes with every card in a final status, not left dangling.
  • Update your own cards right after finishing work rather than batching updates at the end of the day.
  • Use comments for quick coordination instead of switching to chat for every small question.
  • Burndown, velocity, and retro analytics are not on this board; use Team Analytics for the basics.
  • On Connected projects, do not let an agent change synced status.
  • Letting cards sit unmoved for days, which makes standups rely on memory instead of the board.
  • Closing a sprint with cards still in progress instead of moving or carrying them over explicitly.
  • Assigning a card without opening it to add enough description for the assignee to start.