Sprint Planning
Sprints are time-boxed delivery cycles. The SDM creates sprints at the project level, assigns tasks to developers, and uses AI-powered estimation to plan capacity.
Creating a Sprint
Create the sprint
From the project sprint view, the SDM creates a new sprint with a name, start date, and end date. Team capacity is defined — how many hours each developer has available for this cycle.
Assign tasks
Tasks from the backlog are dragged into the sprint or assigned via the task detail view. Each task is assigned to a specific developer.
AI-powered estimation suggests hours per task based on the complexity score and the developer's profile. The SDM can accept or override the estimate.
Review capacity
The sprint planning view shows total assigned hours against each developer's available capacity. Over-allocation is flagged — the SDM can rebalance before the sprint starts.
Start the sprint
Once planning is complete, the sprint moves to Active. Tasks appear on the sprint board and developers can begin work.
Sprint Lifecycle
| Status | Description |
|---|---|
| Planning | Sprint created, tasks being assigned, capacity being set |
| Active | Development in progress, sprint board is live |
| Completed | All tasks done, retrospective data and velocity metrics available |
AI-Powered Estimation
Konductro uses the Anthropic API to estimate task effort. The estimation considers:
- Task complexity — derived from the story's complexity score and the decomposition detail
- Developer profile — past velocity and experience with similar work
- AI tooling availability — whether the developer uses CLI plugins that accelerate delivery
Estimates are suggestions, not mandates. The SDM always has final say.
Sprint Board
The sprint board provides a real-time view of all tasks in the active sprint, organised by status:
- To Do — assigned but not yet started
- In Progress — developer has started work
- PR Open — pull request created, awaiting review
- In QA — merged and being tested
- Done — all test phases passed
Task cards show the assignee, estimated hours, and current status. Status transitions happen automatically as work progresses — no manual board updates.