Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Bolstering the Backlog
One of the fundamental concepts in agile methods is that of a prioritized list of features for the team to develop against. This list of features is typically called a backlog and the roles with the backlog are simple: the “customer” prioritizes the work to do and the “team” agrees to work in priority order. Working in this manner allows the customer to change their mind and reprioritize dynamically while ensuring the team is always working on the highest priority items.
While it is common to prioritize features in a backlog, what is less common is to prioritize the stakeholders and their desired results. Creating a Results Backlog that clearly defines success--with measurable business objectives--will ensure the team stays focused on solving the right problem, not just the problem right.
The Product Backlog
Scrum, the most popular agile method, uses a Product Backlog to capture the set of features to be developed in future product releases. In practice, this backlog is often aligned with a Product Roadmap that may span months or even years.
Scrum, the most popular agile method, uses a Product Backlog to capture the set of features to be developed in future product releases. In practice, this backlog is often aligned with a Product Roadmap that may span months or even years.
Scrum also designates a Product Owner, a proxy for the customer, as the person responsible for managing the Product Backlog. The owner works closely with the marketing and sales teams to identify new product capabilities while also working with the development team to identify which features should be implemented…
Please log in or sign up below to read the rest of the article.
ADVERTISEMENTS
|
"When angry, count to four; when very angry, swear." - Mark Twain |