Definition
A backlog is a prioritised list of tasks, features, fixes, and improvements that a team plans to work on. It acts as a single source of truth for everything that needs doing on a project, ordered by importance. Items at the top are worked on next; items lower down are acknowledged but not yet scheduled. In software development, a backlog is typically managed by a product owner or project lead who decides what gets priority based on business value, urgency, and dependencies.
Why It Matters
Without a backlog, work requests arrive from multiple directions and compete for attention with no clear ranking. Teams end up either firefighting whichever request shouts loudest or losing track of important tasks altogether. A well-maintained backlog gives everyone — the development team, stakeholders, and the client — visibility into what is being worked on now, what is coming next, and what has been deliberately deferred. It also makes sprint planning and capacity discussions far more productive because the conversation starts from an agreed list rather than scattered emails and verbal requests.
Example
A logistics company commissions a custom dashboard. During discovery, forty feature requests surface: live tracking maps, driver messaging, automated route suggestions, invoice generation, and more. Rather than promising everything at once, the team builds a backlog. The first sprint tackles the live tracking map and driver status panel because those deliver immediate operational value. Invoice generation, while important, sits further down the list and is scheduled for month two. When the client later requests a fuel cost report, it is added to the backlog and prioritised against the remaining items rather than interrupting work already in progress.