PSM-II · Question #10
Which approach would you recommend to ensure that the Product Backlog items discussed at Sprint Planning are well understood, actionable, and easier to forecast?
The correct answer is D. Having the Development Team use some time during each Sprint to help the Product Owner. Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement…
Question
Which approach would you recommend to ensure that the Product Backlog items discussed at Sprint Planning are well understood, actionable, and easier to forecast?
Options
- AHaving a separate group of business analysts and functional testers analyzing high-ordered
- BHaving the Product Owner work with stakeholders between the end of the last Sprint and before
- CHaving the business analysts in the Development Team create the upcoming Product Backlog
- DHaving the Development Team use some time during each Sprint to help the Product Owner
How the community answered
(53 responses)- A2% (1)
- B6% (3)
- C9% (5)
- D83% (44)
Explanation
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog. This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items. During Product Backlog refinement, items are reviewed and revised. The Scrum Team decides how and when refinement is done. Refinement usually consumes no more than 10% of the capacity of the Development Team. However, Product Backlog items can be updated at any time by the Product Owner or at the Product Owner's discretion.
Topics
Community Discussion
No community discussion yet for this question.