What happens in a backlog refinement session?

• A. The product owner and lead developer prioritize the backlog until there are 2 weeks worth of stories that meet the DoR
• B. The product owner prioritizes the backlog and the lead developer ensures there are 2 weeks worth of stories that meet the DoD
• C. The team reviews user stories and ask questions until 2 weeks worth of stories meets the DoR
• D. The team reviews user stories and ask questions until 2 weeks worth of stories meets the DoD

Answer: (C)

Backlog refinement is about preparing upcoming work for sprint planning. The team reviews user stories, asks questions to clarify details, splits large items into smaller pieces, and adds or revises acceptance criteria so items are clear, understood, and estimable. The goal is to meet the Definition of Ready, meaning the items are prepared enough to be pulled into a sprint with a clear scope. The Definition of Done governs when work is considered finished, not when it should be started, so refinement focuses on readiness for planning rather than completion. That collaborative check—ensuring a set of stories meets the Definition of Ready—best captures what happens in a backlog refinement session.