Sprints

What it is

Sprints organize tasks into time-boxed iterations within a workstream. Each sprint has a status lifecycle, start/end dates, a goal statement, and panels for capacity planning, branch strategy configuration, and agent orchestration.

Why it matters

Sprints give delivery teams cadence. By batching tasks into iterations, teams can set achievable goals, measure velocity, and coordinate gate evaluations at sprint boundaries.

Key concepts

Status: planning, active, completed, cancelled — lifecycle states for each sprint
Sprint number: Sequential identifier within a workstream
Sprint goal: A short statement describing what the sprint should achieve
Workstream scope: Each sprint belongs to a workstream via workstreamId
Sprint card: SprintCard shows sprint name, number, status badge, date range, goal, and workstream name
Sprint filters: SprintFilters narrow the list by status, workstream, or date range
Capacity planner: SprintCapacityPlanner helps estimate how much work fits in a sprint
Branch strategy panel: BranchStrategyPanel configures Git branching conventions per sprint
Orchestration panel: SprintOrchestrationPanel lets you kick off an agent orchestration run scoped to a sprint

How to use it

Navigate to [Program] > Sprints.
View sprint cards grouped by status.
Click a card to open the sprint detail page.
On the detail page, review assigned tasks, use the capacity planner, and configure branching strategy.
Start an orchestration run from the orchestration panel to dispatch AI agents for sprint work.
Transition the sprint through planning > active > completed as work progresses.