PSPO II Practice Question

Scrum Essentials: One Product, One Backlog

Question

A separate Product Backlog is needed for every:(choose the best answer)

Options

  • A A. Product.
  • B B. Scrum Team.
  • C C. Portfolio.
  • D D. Program.
  • E E. All of the above.

Answer

  • A. Product.

Explanation

A Product Backlog is a crucial artifact in Scrum that defines the work needed to create and maintain a product. Therefore, a separate Product Backlog is necessary for every distinct Product. Each Product has unique requirements, stakeholders, and market conditions, necessitating a tailored approach to its development. Option B, 'Scrum Team,' is incorrect because a Scrum Team can work on the same Product and share a single Product Backlog. Option C, 'Portfolio,' is misleading as portfolios consist of multiple Products, each of which should have its own backlog. Similarly, Option D, 'Program,' does not apply since programs typically encompass several Products, and each Product should maintain its own backlog. Option E, 'All of the above,' is also incorrect for the same reasons mentioned. In summary, the need for a separate Product Backlog is essential for effective management and prioritization specific to each Product.

Expert Author

MR

Marcus Rodriguez

Product Owner & Business Analyst

Backlog management, stakeholder collaboration, user stories

Why Other Options Are Wrong
Option B ('Scrum Team') is incorrect because multiple Scrum Teams can collaborate on a single Product Backlog. Each Team focuses on aspects of the product but does not require separate backlogs. Option C ('Portfolio') is misleading; a portfolio may consist of multiple Products, and each Product should have its own backlog to address its unique needs. Option D ('Program') is incorrect as it typically encompasses several Products, making it impractical to manage all the details in one backlog. Finally, Option E ('All of the above') is wrong since it incorrectly implies that all these entities need separate backlogs when only Products do.
Real-World Application
In a software development company, the team is working on two distinct Products: a mobile app and a web platform. Each Product has its own stakeholders and requirements. Consequently, the team maintains separate Product Backlogs for each Product to prioritize features and improvements efficiently, ensuring that each backlog reflects the unique needs of its respective Product.
Common Pitfalls
  • Assuming multiple teams working on a single product need separate backlogs.
  • Confusing Product Backlogs with program or portfolio management.
  • Not recognizing the importance of tailoring backlog items to specific product needs.

Key Concepts

Product Backlog Scrum Team Stakeholders Prioritization Incremental Development

Scrum Guide Reference

Scrum Guide 2020, Section 3.1: The Product Backlog