Backlog Refinement

What is the main purpose of Backlog Refinement?

• To remove items from the Product Backlog

• To add new items to the Product Backlog

• To clarify, prioritize and estimate items in the Product Backlog

Answer explanation

The primary goal of Backlog Refinement is to ensure that the Product Backlog is prioritized, estimated, and refined to the point where the Development Team can begin work on the items during the next Sprint.

Who is responsible for Backlog Refinement in Scrum?  

• The Scrum Master

• The Product Owner

• The Development Team

• All of the above

Answer explanation

Backlog Refinement is a collaborative effort that involves the entire Scrum Team, including the Product Owner, Development Team, and Scrum Master.

During Backlog Refinement, what is the main role of the Development Team?  

• To provide time estimates for each item in the Product Backlog

• To prioritize the Product Backlog based on business value

• To clarify requirements and identify dependencies for each item in the Product Backlog

• To negotiate with stakeholders on the scope of each item in the Product

What is the purpose of estimating user stories during Backlog Refinement?  

• To determine how long it will take to complete each user story

• To determine the level of effort and complexity of each user story

• To prioritize user stories based on business value

• To identify dependencies between user stories

Who is responsible for ensuring that each user story is clear, concise, and well-defined?  

• The Scrum Master

• The Product Owner

• The Development Team

• All of the above

What is the purpose of the Definition of Ready (DoR)?  

• To ensure that each user story is well-defined and ready for implementation

• To ensure that the team has a shared understanding of each user story

• To define the acceptance criteria for each user story

• To determine the level of effort and complexity of each user story

How much time should be spent on Backlog Refinement each Sprint?  

• 2 hours per Sprint

• There is no set time limit for Backlog Refinement, but it is recommended that teams spend at least 10% of their capacity on backlog refinement activities

• 4 hours per Sprint

• 1 hour per Sprint

What is the difference between story points and time estimates?  

• Story points are a measure of the complexity and effort required to complete a Product Backlog item, while time estimates are a measure of the amount of time it will take to complete the item.

• Story points are a measure of the amount of time it will take to complete a Product Backlog item, while time estimates are a measure of the complexity and effort required to complete the item.

• Story points and time estimates are the same thing.

• Story points are used for Sprint planning, while time estimates are used for Backlog Refinement.

Answer explanation

Story points and time estimates are both used in Scrum, but they measure different aspects of Product Backlog items. Story points are a relative measure of complexity and effort, while time estimates are an absolute measure of time. Story points are often used for Sprint planning and forecasting, while time estimates may be used during Backlog Refinement to help the Scrum Team understand the scope of work.

Who is responsible for prioritizing the Product Backlog? 

• The Scrum Master

• The Product Owner

• The Development Team

• The stakeholders

When does Backlog Refinement typically take place? 

• At the beginning of each Sprint

• Throughout the Sprint, as needed

• At the end of each Sprint

• Only when new Product Backlog items are added

Answer explanation

Backlog Refinement is an ongoing process that happens throughout the Sprint, as needed. It is not a one-time event that only takes place at the beginning or end of the Sprint. The purpose of Backlog Refinement is to ensure that the Product Backlog is well-refined, ordered, and ready for Sprint planning. The Scrum Team may choose to spend more or less time on Backlog Refinement, depending on the needs of the team and the product.