Sprints organize work into time-boxed iterations. Tasks are the individual units of work within a sprint.
Auto-planning a sprint
Select one or more features from the roadmap, then click "Plan Sprint." Aira will:
- Break each selected feature into concrete tasks
- Estimate effort hours for each task
- Suggest assignments based on team member skills and current workload
- Respect sprint capacity limits
Tasks are generated iteratively — each one appears in the UI as it's created, streamed via SSE. You see each task as Aira produces it rather than waiting for the entire plan.
The task board
The Board page shows a Kanban view of the current sprint with columns:
- Backlog — Tasks not yet started
- To Do — Tasks ready to begin
- In Progress — Active work
- In Review — Waiting for review
- Done — Completed tasks
Drag tasks between columns to update their status. The board shows assignee avatars, priority indicators, and effort estimates.
Task detail dialog
Click any task to open its detail view. Every task has:
| Field | Description |
|---|---|
| Title | Short description of what needs to be done |
| Description | Detailed requirements and context |
| Solutions | Proposed implementation approaches |
| Acceptance criteria | Conditions that must be met for the task to be complete |
| Complexity | Relative complexity rating |
| Priority | Urgency ranking |
| Estimate (hours) | Expected effort |
| Type | Task category (development, design, testing, documentation, etc.) |
| Assignee | The team member responsible |
| Sprint | Which sprint the task belongs to |
| Status | Current state (backlog, todo, in_progress, review, done) |
| Due date | Optional deadline |
Sprint management
Creating a sprint
Sprints are created automatically during auto-planning or manually from the Sprints page. Each sprint has:
- Sprint number — Sequential identifier
- Goal — What the sprint aims to achieve
- Start and end dates — The time box
- Capacity — Total available hours across the team
Sprint lifecycle
planning → active → completed
Only one sprint can be active at a time. Starting a sprint makes it the current sprint shown on the Board page.
Capacity tracking
Sprint capacity is calculated from team member availability. Each team member has configured hours per sprint (see Team). The Sprints page shows:
- Total capacity hours
- Allocated hours (sum of task estimates)
- Remaining capacity
- Per-member utilization
Backlog
Tasks not assigned to any sprint live in the backlog. You can move tasks between the backlog and sprints by editing the task or dragging between sprint views.
Manual task creation
Create tasks manually from the Board or Sprint pages. Provide a title, description, and any fields you want to set. Manual tasks can be associated with features or left standalone.
Moving tasks between sprints
If a task isn't completed during its sprint, move it to the next sprint by editing the sprint assignment. Tasks retain their full history across sprint moves.