Sprints

Sprints are timeboxed periods for focused work. kendo supports the full sprint lifecycle: planning, execution, and completion.

Sprint Lifecycle

1. Planning

Create a new sprint and assign issues to it. During planning:

• Review the backlog and select issues for the sprint
• Estimate effort and set priorities
• Assign issues to team members

Only one sprint can be active at a time per project. Additional sprints stay in the planned state until the active sprint completes.

2. Active Sprint

Activate a sprint to start the timebox. During an active sprint:

• The board filters to show sprint issues by default
• Team members work through issues, moving them across lanes
• Time can be logged against sprint issues

3. Completion

Complete a sprint when the timebox ends:

• Issues in the final lane are marked as done
• Unfinished issues automatically return to the backlog
• The sprint moves to completed status

Sprint Statuses

Status	Description
Planned	Sprint created but not yet started
Active	Currently running — only one per project
Completed	Sprint finished, archived for reference

Managing Sprints via MCP

AI assistants can manage sprints through MCP tools:

"Create a new sprint called 'Sprint 12' in project KD"
"Complete the active sprint in project KD"

Available MCP operations: create, update, and complete sprints. See the API Reference for details.

See Also

• Quick Start — Running your first sprint
• Issues & Board — Assigning issues to sprints
• Time Tracking — Logging time during sprints
• Projects — Project-level sprint configuration