Sprint board

Overview

The sprint board is the Native execution surface for the current sprint: a column per status (for example To do, In progress, Review, Done), with a card per task. Moving a card between columns updates its status for everyone instantly.

Every card carries enough context to act on without leaving the board: assignee, short description, and a comment thread for quick coordination. Opening a card gives you the full detail view when a decision needs more context.

In Connected mode, the equivalent execution surface may live in an external tracker such as Linear or Jira instead, with the GrowthOS board deep-linking out to it. Native teams do everything described here directly on the GrowthOS board.

What you can do here

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.

When to use

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.

Prerequisites

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.

Where to find it

Sidebar: project Sprint board
Accessible from the project overview once a sprint is confirmed.

Step-by-step

Open the active sprint board under the relevant project.
Scan columns to see current status distribution at a glance.
Drag a card to the next column as its status changes.
Open a card to edit the assignee, description, or leave a comment.
Flag and comment on any item that looks blocked.
Check in daily during standups to keep the board an accurate mirror of real progress.
Close or complete the sprint once the time window ends.

What success looks like

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.

Tips & best practices

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 may be hidden in MVP; use Team Analytics for the basics instead.

Common mistakes

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.