Omniscio

PM Sprints

Sprint management for Mission Control boards: time-boxed iterations with a planned, active and completed lifecycle, item assignment from the board toolbar, velocity stats recorded on completion, and retrospectives generated either from a template or by an AI model. Covers the lifecycle, velocity tracking, and where each part lives.

On this page

What it is

PM Sprints — listed in Settings → Lab as Sprints / Cycles — is sprint management for Mission Control boards: time-boxed iterations with velocity tracking, item assignment, and AI-powered retrospectives.

Sprints let you organize board items into time-boxed iterations. Each sprint has a title, optional goal, start/end dates, and a status that moves through a fixed lifecycle: planned, active, completed.

Where to find it

Sprints are driven from the board itself. Items are assigned to or removed from sprints via the board toolbar's sprint selector, and completing a sprint opens a completion modal with a rollover toggle. A retrospective can be generated for any completed sprint. Dashboard widgets render burndown, velocity, and planned-vs-unplanned charts from the recorded sprint history.

The sprint selector shows only while BOTH are on: the board's own Sprints feature and the Sprints switch (pmSprintsEnabled, on by default). Turning the switch off hides the selector on every board and makes the sprint and backlog CLI routes answer 404 with featureOff: "pm-sprints". The same rule holds for the other Mission Control feature switches: documents, saved views, feature profiles, automations, approval workflows and What next each 404 their CLI routes while their own switch is off.

How it behaves

Items are assigned to or removed from sprints via the board toolbar's sprint selector. When you complete a sprint, it records velocity stats (points planned vs completed, items total vs completed, carry-over count, duration) and optionally rolls incomplete items into an auto-created next sprint with an auto-incremented title.

A retrospective can be generated for any completed sprint. Two paths are available depending on the board's AI comfort setting: a template-based summary (always free) or an LLM-generated analysis via Anthropic Haiku (30-second timeout, $5/day spend cap, 1024 max tokens).

Reusing a sprint title

Titles are not unique: a board may reuse a name across cycles. What the create path looks at is only whether the name is currently taken by a sprint that is still open.

  • Creating a sprint whose title matches a still planned or active sprint returns that existing sprint instead of making a second one. That is what keeps a double-submitted create, or a retried rollover, from producing a duplicate.
  • Creating a sprint whose title matches a completed sprint makes a genuinely new planned sprint carrying the goal and dates you sent. The completed sprint is never returned and never blocks the name.
  • The same rule covers rollover: if the auto-incremented next title is already held by a completed sprint from an earlier cycle, rollover creates a fresh sprint and carries the incomplete items into that, so items never land on a finished sprint.

Sprint lifecycle

  1. Create -- inserted with status planned, auto-positioned at the end
  2. Start -- transitions to active; emits a sprint_started board event for automations
  3. Assign / Unassign -- moves items between the backlog (sprint_id = NULL) and the active sprint
  4. Complete -- records a PmSprintHistory row with velocity stats; optionally carries over incomplete items into a new sprint; emits sprint_ended
  5. Retrospective -- analyzes the sprint history (template or LLM path)

Velocity tracking

Sprint history rows feed two queries: getSprintHistoryForBoard (raw history) and getSprintVelocityTrend (aggregated trend points). Dashboard widgets in features/dashboard/widgets/ render burndown, velocity, and planned-vs-unplanned charts from this data.

Sharing between teammates

Sprints travel with their board: anyone who can see a board sees its sprints, and an item moved into a sprint shows the same sprint for every one of them. A team guest is no exception — a guest sees exactly the sprints of the boards they were granted and nothing from a board they were not. Sprint history and velocity are computed locally and are not shared yet.

Sprints arrive inside the board's own read, so they inherit the board's access rules and its live updates instead of having a sync path of their own. Creating, editing, starting, completing and deleting a sprint pushes on the next sync; anything already on a computer when sharing first turns on is uploaded rather than discarded.

The whole project management system this sits inside is described in mission-control.md, the parent page, and the sibling that plans work at a larger scale than a single iteration is pm-goals.md. If you want the view that gathers what is assigned to you personally, read pm-my-work.md. Every other page in this library is listed in INDEX.md.

Last verified 2026-11-04