Product Backlog Refinement

Question 1

Why do we rank and refine user stories during backlog refinement?

Answer 1

So that the most important work is visible and ready to work in the next iteration.

Question 2

How do we evaluate each card in the backlog refinement?

Answer 2

By having focused discussions between the Product Owner, Team and SMEs to understand what the intention is, the potential challenges, the dependencies, and create an estimate in relation to the other cards.

Question 3

True or False

Backlog refinement is continual.

Answer 3

True

We are always refining the backlog to make sure we are working on user stories that are the most valuable. The ones with the highest priority have the most refinement.

Question 4

What is the length of a backlog refinement meeting in an iteration-based agile project?

Answer 4

Two to Three Hours

Question 5

What do refinement discussions drive?

Answer 5

Understanding (talking it out to get to a common understanding).

Question 6

Where do we use the acceptance criteria defined in the refinement discussions?

Answer 6

It becomes the product owner’s script for the product demo/review.