CST Product Backlog Refinement 3

Question 1

The 'Definition of Ready' (DoR) is sometimes used to gatekeep items entering a Sprint. What is the main risk of enforcing a strict DoR?

Accepted Answer

It can become a bureaucratic barrier that slows delivery and violates Scrum's empirical nature

Answer

A rigid DoR can create a mini-waterfall 'analysis phase' and reduce team agility by blocking imperfect but workable items.

Question 2

During refinement, the team consistently finds that items near the top of the backlog have poor acceptance criteria. This is best addressed by:

Accepted Answer

Coaching the Product Owner to collaborate with Developers when writing acceptance criteria

Answer

Acceptance criteria quality improves through collaborative Product Owner–Developer conversations, not unilateral writing.

Question 3

A team using Planning Poker during refinement reaches wildly divergent estimates. What should happen next?

Accepted Answer

Facilitators reveal the cards, high and low estimators share reasoning, then re-estimate

Answer

Divergent estimates indicate differing assumptions; discussion surfaces those differences before re-estimating.

Question 4

Non-functional requirements (e.g., performance, security) are best handled in the Product Backlog by:

Accepted Answer

Incorporating them into the Definition of Done and/or individual backlog items where relevant

Answer

Non-functional requirements should be woven into the DoD and explicitly noted on relevant backlog items to ensure they are always met.

Question 5

An item that is too large to complete in a single Sprint is called an:

Accepted Answer

Epic

Answer

An epic is a large user story that must be broken down into smaller stories before it can be pulled into a Sprint.

(CST) Certified Scrum Trainer Practice Test