Answering: “True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.”

False. One product has one Product Backlog, even when several teams work on it. Separate backlogs per team would fragment ordering and hide dependencies.

Exam Question

True or False: A Product Owner with multiple teams working on one product should maintain separate Product Backlogs for each team.

• A. True
• B. False

Correct Answer

B. False

Why This Is the Correct Answer

The Scrum Guide calls the Product Backlog “the single source of work undertaken by the Scrum Team.” When a product needs several Scrum Teams, the Guide says they should share the same Product Goal, Product Backlog and Product Owner. One ordered list lets the Product Owner make clear trade-offs across all the work, and it lets every team see what the others are doing. Teams can still tag items or view filtered slices to plan their Sprints, but there is only one backlog underneath. Separate backlogs would force the Product Owner to juggle competing orders and would make it harder to produce one integrated Increment.

Why the Other Options Are Wrong

A. True Separate backlogs per team break the single ordered list, create competing priorities and make integration harder.

Exam Tip

For multi-team setups, remember the triple: one Product Owner, one Product Backlog and one Product Goal per product. Anything per team is a trap.

Key Takeaways

• A product has a single Product Backlog.
• Multiple teams pull from the same ordered list.
• One backlog makes trade-offs and dependencies visible.