DEVREVU · BUILD · PART 2 OF 3 · BEGINNER
Build · Part 2 — Sprints
You've captured your work as issues. Now put it in motion. Learn to plan, run, and track a focused cycle of work — one sprint at a time — on a board your whole team shares, with Computer as a teammate in the room.
Plan it. Run it. Learn from it.
A pile of issues isn't a plan. A sprint turns that pile into a focused, time-boxed cycle your team commits to, so "someday" becomes "this fortnight". The sprint board holds your cadence, the current and upcoming sprints, the backlog, and the analytics to reflect afterwards.
This part takes the issues from Part 1 and gives them a rhythm. You set up a board, navigate its views, plan a backlog, set a real goal, and collaborate as a team — including multiplayer sessions where everyone works with Computer live. Then you track sprint health and learn to read the signals instead of the charts.
The seven sections of Part 2
Section | What you'll do | Why it matters |
|---|---|---|
What is a sprint? | Grasp sprints, boards, and cadence. | Time-boxing turns an endless to-do pile into focus, rhythm, and reflection. |
Set up your board | Create a board with cycle length and buffer. | Set it once; every sprint follows the cadence. |
Navigate the board | Move between Backlog, Current, Planned, Previous; List, Board, Gantt. | Two axes — which sprint, and how you view it. |
Plan your backlog | Groom the backlog and move issues into a sprint. | Planning is one question: which issues make the cut this cycle? |
Sprint rituals | Set goals and collaborate on the Timeline. | A sprint is a shared commitment, not just a list. |
Multiplayer on Computer | Bring your team into a shared, live AI session. | No handoff docs — the shared Memory is already there for everyone. |
Track health & read signals | Use Sprint Insights, completion, spillover, carryover. | Know whether you're on track without a status meeting. |
WHAT'S INSIDE
The three movements of a sprint
Set up & plan
A board, a cadence, a backlog.
Create a sprint board with your team's cycle length and buffer, navigate its tabs and List/Board/Gantt views, then groom the backlog and commit the issues you'll finish this cycle.
Run it together
Goals, Timeline, and multiplayer.
Set 2-3 outcome goals, discuss on the Timeline, and bring the whole team into a shared live Computer session — @mention @computer to plan, track, and recap together.
Track & learn
Read the signals, not the charts.
Use Sprint Insights for completion rate, spillover, and carryover, read the burndown, and let Computer narrate the trends so a retro starts from insight, not raw numbers.
The sprint-health terms to know
Term | What it means |
|---|---|
Planned work | Issues added within a day of the sprint starting. |
Unplanned work | Issues added more than a day after it started. |
Completion rate | Issues completed before the sprint ends ÷ total issues; it locks when the sprint closes. |
Spillover | Any issue pushed to a future sprint. |
Carryover | An issue that keeps spilling over — 1x, 2x, or a 3x+ red flag. |
Planning adherence | How much of your committed work you delivered, versus overall completion. |
You gave your work a rhythm. In Part 3, zoom out to the roadmap.
Our customers
Resources
Initiatives
