Backlog
A prioritised list of work items (features, enhancements, bugs, and tasks) that the team needs to complete, serving as the single source of truth for what needs to be built or done.
In-Depth Explanation
The backlog is the ordered list of everything that is known to be needed in the product or project. It is a living document that evolves continuously as the team learns more about customer needs, market conditions, and technical realities.
Types of backlogs:
- Product backlog: The master list of all desired work for the product (owned by the product owner)
- Sprint backlog: The subset of product backlog items selected for the current sprint
- Release backlog: Items planned for a specific release
- Technical debt backlog: Technical improvements and refactoring items
Backlog item types:
- User stories: Descriptions of functionality from the user's perspective
- Epics: Large user stories that need to be broken down
- Bugs: Defects that need to be fixed
- Technical tasks: Infrastructure, refactoring, or tooling work
- Spikes: Time-boxed research or investigation tasks
- Chores: Maintenance and operational tasks
Backlog management best practices:
- Prioritisation: Order items by business value, risk, and dependencies
- Refinement (grooming): Regularly review, estimate, and clarify backlog items
- INVEST criteria: Stories should be Independent, Negotiable, Valuable, Estimable, Small, Testable
- Right-sized: Keep the backlog manageable (not a wish list of hundreds of items)
- Transparency: Visible to all stakeholders
- Progressive elaboration: Items near the top are well-defined; items further down are less detailed
Common prioritisation frameworks:
- MoSCoW: Must have, Should have, Could have, Won't have
- WSJF (Weighted Shortest Job First): Value divided by effort
- RICE: Reach, Impact, Confidence, Effort
- Value vs Effort matrix: Two-by-two grid for quick prioritisation
Business Context
A well-managed backlog ensures the team always works on the most valuable items, prevents scope creep, and provides transparency about priorities and upcoming work.
How Clever Ops Uses This
Clever Ops maintains transparent, prioritised backlogs for all client projects, ensuring we always deliver the highest-value work first. We help Australian businesses establish their own backlog management practices to improve project focus and delivery efficiency.
Example Use Case
"A product team maintains a prioritised backlog of 40 items, with the top 10 fully refined and estimated, ready for selection in the next sprint planning session."