Backlog Refinement Quiz

What is the primary purpose of Backlog Refinement in Scrum?

• Assign tasks to team members

• Finalize the Sprint Goal

• Ensure Product Backlog items are ready for future sprints

• Decide the Sprint Backlog

Who is responsible for estimating Product Backlog items during refinement?

• Scrum Master

• Product Owner

• Development Team (Developers)

• Stakeholders

When does Backlog Refinement typically occur?

• During the Sprint Review

• Only at the beginning of the project

• Regularly throughout the Sprint

• At the end of each Sprint

Which of the following is a good outcome of Backlog Refinement?

• All backlog items are committed to a sprint

• Stories are broken down, clarified, and estimated

• The Product Owner writes test cases

• Team velocity is calculated

What is Planning Poker used for in Backlog Refinement?

• Deciding Sprint Goals

• Prioritizing features

• Estimating story point effort collaboratively

• Assigning stories to team members

What is the ideal time allocation for Backlog Refinement in a Sprint (for a 2-week sprint)?

• 8 hours

• 
  4 hours

• 2 hours

• No time limit

What is a common outcome of effective Backlog Refinement?

• Sprint Backlog is finalized

• Stories are moved to Done

• Backlog items meet the Definition of Ready

• Burndown chart is updated

Who is responsible for prioritizing items in the Product Backlog?

• 
  Scrum Master

• 
  Development Team

• Product Owner

• Project Manager

During refinement, the team starts discussing tasks and hours. What should they do?

• 
  Continue — it’s good planning practice

• Stop and defer task breakdown to Sprint Planning

• Skip the story entirely
  

• Ask the Scrum Master to decide

Why should large stories (epics) be split during refinement?

• To reduce the Product Backlog size

• To improve Sprint velocity
  

• To make them deliverable within a single sprint

• To avoid involving the PO