Answering: “What is the key concern when multiple Scrum Teams are working from the same Product Backlog?” (PSM I)

The key concern when several Scrum Teams share one Product Backlog is minimizing dependencies between them. Dependencies slow teams down and make integrated Increments harder to deliver.

Exam Question

What is the key concern when multiple Scrum Teams are working from the same Product Backlog? (choose the best answer)

• A. Clear definition of requirements.
• B. Making sure there’s enough work for everyone on each team.
• C. Meeting original scope projections.
• D. Minimizing dependencies between teams.
• E. Maximizing velocity.

Correct Answer

D. Minimizing dependencies between teams.

Why This Is the Correct Answer

When teams work from one Product Backlog, they must still produce one integrated Increment that meets a shared Definition of Done. Every dependency between teams creates waiting, coordination overhead and integration risk. If one team is blocked by another, neither may reach Done by the end of the Sprint. Good practices include organizing as feature teams, refining items together to spot dependencies early, and ordering work to reduce cross-team blocking. Scrum.org’s Nexus framework is built around this same concern, making cross-team dependencies visible and resolving them.

Why the Other Options Are Wrong

A. Clear definition of requirements. Clarity helps, but it is not specific to multiple teams. Requirements also emerge, so full upfront definition is not the goal.

B. Making sure there is enough work for everyone. Keeping people busy is not the aim. Delivering an integrated, valuable Increment is.

C. Meeting original scope projections. Scope is expected to change in Scrum. Holding to original projections is a traditional project concern.

E. Maximizing velocity. Velocity is a planning aid, and maximizing it does not improve integration or value.

Exam Tip

In multi-team questions, dependencies and integration are the recurring themes. Pick the answer that reduces them.

Key Takeaways

• Dependencies are the main risk when teams share a product.
• Teams must still deliver one integrated Increment.
• Busy teams and high velocity are not the goal.