What is backlog?
Quick definition
An ordered list of work items, features, or tasks waiting to be started or prioritized. It represents everything that needs to be done but hasn't entered active work yet.
A backlog is a repository of all potential work items in a project that haven't been started or scheduled for immediate execution. In Kanban systems, the backlog serves as the upstream source feeding into active columns like 'To Do' and 'In Progress'. Items in the backlog are typically prioritized based on business value, urgency, dependencies, and team capacity, allowing teams to maintain a clear view of future work.
Backlogs are essential for managing scope creep and maintaining focus. Rather than attempting all requests simultaneously, teams pull items from the backlog into their workflow based on capacity and priorities. This pull-based approach prevents overload and enables better resource allocation. Backlogs can contain user stories, bug reports, feature requests, technical debt items, or any unit of work relevant to the project.
In development contexts, backlogs often undergo grooming (refinement) to ensure items are well-defined, estimated, and ready for implementation. AI coding agents and development teams use backlogs to understand the full scope of work, identify dependencies, and make informed decisions about what to tackle next. Clear backlogs reduce context-switching and improve team throughput.
Example
How it shows up in practice
A software team's backlog might contain: 'Implement user authentication', 'Fix database connection timeout', 'Add dark mode support', 'Refactor legacy payment module', and 'Create API documentation'. As the team completes sprint work, they pull the highest-priority items from the backlog into their 'To Do' column.
In Kanboard
In Kanboard, the backlog is typically represented as a separate swimlane or column before the main workflow columns. It serves as the holding area for unscheduled tasks, allowing teams to distinguish between planned work (in the backlog) and active work (in progress columns). Backlog items can be dragged into active columns when capacity allows, implementing a pull-based workflow system.
Frequently asked questions
How is a backlog different from a to-do list?
A backlog is a prioritized, managed collection of all future work items for a project, while a to-do list is typically personal and informal. Backlogs are refined, estimated, and used for capacity planning across teams. They represent organizational commitment to potential work.
What items belong in a backlog?
Backlogs contain user stories, feature requests, bug reports, technical debt, performance improvements, and documentation tasks. Any work item that hasn't been scheduled for immediate execution belongs in the backlog until prioritized and moved into active development.
How do teams prioritize backlog items?
Prioritization considers business value, customer impact, dependencies, technical feasibility, and team capacity. Many teams use frameworks like MoSCoW (Must, Should, Could, Won't) or weighted scoring to order items objectively and ensure high-value work gets done first.
Can AI agents access and manage backlogs?
Yes, AI coding agents can read backlog items via APIs, analyze priorities, decompose tasks, and suggest optimal execution sequences. They help teams triage work, identify dependencies, and automate backlog grooming tasks.