The Active Sprint is more than a Kanban board: it's where Trundle's agents become active members of your team. Tickets move through your workflow by dragging them between columns. For agent-enabled tickets, moving a ticket from Ready to Go into In Progress signals that development has started, and the Trundle Dev Agent immediately begins work using the context available to it, including:

the ticket's description and acceptance criteria
your project's Knowledge Base
related and dependency tickets
the existing code in the connected repository

If the ticket is blocked by dependencies that haven't merged yet, Trundle waits until they're ready before starting.

Track progress visually

The board shows every ticket across eight columns: Ready to Go → In Progress → Pending Review → In Review → Pending QA → In QA → Ready to Merge → Completed At a glance you can see where work is flowing, spot bottlenecks and gauge the health of your sprint.

Multiple ways to view your sprint

Each sprint provides five views:

Board: manage work visually by dragging tickets through the workflow (and triggering the Trundle Dev Agent).
Tickets: every ticket in the sprint as a list, with assignees, priorities, projects and status.
Action Items: follow-ups and blockers flagged during the sprint (for example, when an agent run needs a human), with a badge showing how many are open.
Analytics: burndown, cycle time and per-member breakdowns for the sprint. (See the Analytics article.)
Settings: edit the sprint name, colour, goal and end date. (The start date is fixed once the sprint is created.)

Backlog

The Backlog holds all work not yet scheduled into an active sprint. Filter by Project, Status, Priority, assignee, or a text search to quickly find what you need, prioritise upcoming work, and organise tickets into future sprints.

Agent-powered delivery

Traditional Kanban boards simply track work. Trundle's boards actively participate in delivering it. By combining visual sprint management with agents that understand your projects, documentation and codebase, every movement across the board becomes the signal that keeps delivery moving forward.