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
  92% (23)
• B
  4% (1)
• C
  4% (1)

Explanation

In Scrum, one product always has exactly one Product Backlog, regardless of how many teams or features are involved - this single backlog ensures all teams share a unified, prioritized view of work and prevents fragmentation or duplication of effort. Option B (4) is wrong because the number of features does not determine the number of backlogs; features are just items within the backlog. Option C (6) is wrong for the same reason - the number of teams doesn't create separate backlogs; multiple Scrum teams working on one product all pull from the same shared backlog, each with their own Sprint Backlogs. A helpful memory tip: one product = one Product Backlog - think of it as a single "master wish list" for the entire product that all teams draw from, no matter how big the organization grows.

No community discussion yet for this question.