A large product team features six different teams having ten members each, working on a project that involves four high level features. How many Product Backlogs should the team have?

Question

Options

• A1
• B4
• C6

• A
  94% (31)
• B
  3% (1)
• C
  3% (1)

Explanation

In Scrum, there is always one Product Backlog per product - regardless of how many teams are working on it or how many features it contains, because a single backlog ensures a unified, prioritized view of all work and prevents duplication or misalignment across teams. Option B (4) is wrong because the number of high-level features does not determine the number of backlogs; features are simply items or epics within the one backlog. Option C (6) is wrong because having six teams does not mean six backlogs - multiple Scrum teams working on the same product all draw from the same single backlog, which is owned by one Product Owner. A helpful memory tip: "One product = one Product Backlog" - anchor the count to the product, not the teams or features, and you'll never get this wrong on the exam.

No community discussion yet for this question.