In lean agile, which statement best describes the business backlog?

In lean agile, which statement best describes the business backlog?

• A. It is a fixed technical document with no business input
• B. It is a prioritized list of business requirements and user stories
• C. It is a detailed architecture blueprint
• D. It is a regulatory compliance log

Answer: (B)

In Lean-Agile, the business backlog is the living, prioritized queue of work that delivers business value. It contains business requirements and user stories, ordered by value, risk, and dependencies, and is continually refined by the product owner with input from stakeholders. This setup lets the team pull the most valuable work into upcoming iterations, adapt to feedback, and avoid over-planning or rigid, fixed documents. It’s not a fixed technical document and it’s not a detailed architecture blueprint or a regulatory log—the backlog focuses on what delivers value to the business and guides development accordingly.

In Lean-Agile, the business backlog is the living, prioritized queue of work that delivers business value. It contains business requirements and user stories, ordered by value, risk, and dependencies, and is continually refined by the product owner with input from stakeholders. This setup lets the team pull the most valuable work into upcoming iterations, adapt to feedback, and avoid over-planning or rigid, fixed documents. It’s not a fixed technical document and it’s not a detailed architecture blueprint or a regulatory log—the backlog focuses on what delivers value to the business and guides development accordingly.