SCRUM - Scrum Framework Managing the Product Backlog Questions and Answers 1 — Questions and Answers
Question 1: Who has the final say on the order of the Product Backlog?
- The stakeholders, because they represent the needs of the market.
- The Developers, because they know the technical effort required.
- The Scrum Master, because they are accountable for the Scrum process.
- The Product Owner, because they are accountable for maximizing product value. (Correct answer)
Correct answer: The Product Owner, because they are accountable for maximizing product value.
According to the Scrum Guide, the Product Owner is the sole person accountable for managing the Product Backlog, which includes ordering the items to best achieve goals and missions. While they take input from stakeholders and Developers, the final decision on ordering rests with the Product Owner.
Question 2: A Product Owner is managing a large Product Backlog. How should the level of detail for Product Backlog Items (PBIs) generally vary within the backlog?
- All items should have the same level of exhaustive detail to ensure clarity.
- Items at the bottom should be the most detailed to allow for long-range planning.
- Items at the top should be more detailed and clearer than items at the bottom. (Correct answer)
- The level of detail should be random, as the backlog is emergent and constantly changing.
Correct answer: Items at the top should be more detailed and clearer than items at the bottom.
Items at the top of the Product Backlog are candidates for upcoming Sprints and therefore need to be clear, well-understood, and detailed enough for the Developers to select and work on. Items lower down the order are further from implementation and can remain less detailed until they move up.
Question 3: What is the primary purpose of Product Backlog refinement?
- To gain formal sign-off on requirements from all stakeholders.
- To add detail, estimates, and order to Product Backlog Items. (Correct answer)
- To assign specific tasks to individual Developers for the next Sprint.
- To review and approve the work completed in the current Sprint.
Correct answer: To add detail, estimates, and order to Product Backlog Items.
Product Backlog refinement is the ongoing activity of breaking down and further defining Product Backlog items into smaller, more precise items. This includes adding details like descriptions, order, and size to prepare them for future Sprints.
Question 4: The Product Backlog has a single, long-term commitment associated with it that provides context and a target for the Scrum Team to plan against. What is this commitment called?
- The Sprint Goal
- The Product Goal (Correct answer)
- The Definition of Done
- The Release Plan
Correct answer: The Product Goal
The Product Goal is the commitment for the Product Backlog. It describes a future state of the product, serving as a long-term objective for the Scrum Team. The rest of the Product Backlog emerges to define what will fulfill the Product Goal.
Question 5: A Product Owner has identified a new feature. While they are accountable for the Product Backlog, they are currently overwhelmed with stakeholder meetings. What is an acceptable way to handle the creation of the new Product Backlog Item (PBI)?
- The Product Owner must write the PBI themselves, as they are solely responsible.
- The Scrum Master should write the PBI to remove this impediment for the Product Owner.
- The Product Owner can delegate the responsibility of writing the PBI to the Developers. (Correct answer)
- The stakeholders should form a committee to write and approve the PBI.
Correct answer: The Product Owner can delegate the responsibility of writing the PBI to the Developers.
The Scrum Guide states that the Product Owner is accountable for effective Product Backlog management, but they may delegate the responsibility to others. It is common and acceptable for Developers to help write PBIs, with the Product Owner remaining accountable for their content and order.
Question 6: Which of the following is the BEST description of the Product Backlog?
- A static, comprehensive list of all requirements signed off at the beginning of a project.
- A plan for the current Sprint, managed by the Developers.
- An emergent, ordered list of what is needed to improve the product. (Correct answer)
- A list of technical tasks and bug fixes that must be completed before the next release.
Correct answer: An emergent, ordered list of what is needed to improve the product.
The Scrum Guide defines the Product Backlog as an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. It is not static and contains more than just technical tasks or bug fixes.
SCRUM - Scrum Framework Managing the Product Backlog Questions and Answers 1
Who has the final say on the order of the Product Backlog?