Which is the most accurate description of a backlog in agile?

Question

Options

• AThe backlog is the sum of all the story point sizes for the features actually completed in each project iteration.
• BThe backlog is the ordered list of all the work and helps the teams see how to deliver the highest value without creating waste.
• CThe backlog is the ordered list of all the completed work and helps the teams see how to deliver value without creating waste.
• DThe backlog is the ordered list of all the work, shows the work completed, and shows the effect of team members multitasking.

• A
  5% (2)
• B
  92% (34)
• D
  3% (1)

Explanation

Option B is correct because in Agile (particularly Scrum), the product backlog is a prioritized ("ordered") list of all work yet to be done - features, fixes, improvements - and its ordered nature ensures the team always works on the highest-value items first, minimizing waste. A is wrong because it describes velocity, not the backlog - velocity measures story points completed per sprint. C is wrong because the backlog contains remaining work, not completed work; completed items are tracked in the sprint review/done column. D is wrong because while the backlog is ordered, it doesn't track completion status or team multitasking - those are concerns of a sprint board or team metrics.

Memory tip: Think of the backlog as a prioritized wish list - it's forward-looking (what we want to do, ordered by value), not a history of what's been done.

No community discussion yet for this question.