How should backlog refinement be viewed in Scrum?

• A. It is a one-time activity completed at project start
• B. It is a continuous activity where top items receive ongoing refinements
• C. It is the sole responsibility of the Scrum Master
• D. It should be done only after a release

Answer: (B)

Backlog refinement is an ongoing, collaborative activity in Scrum. The Product Owner keeps the backlog oriented by value and priority, but refinement is done with the Scrum Team to add detail, estimates, and acceptance criteria to the top items. By continuously polishing these high-priority items, the team ensures they are clear, small enough to be completed within a sprint, and ready to pull into Sprint Planning. This steady grooming helps with forecasting, reduces surprises, and keeps the backlog usable as needs evolve.

It’s not the result of a single early-project activity, not the sole responsibility of the Scrum Master, and not something to delay until after a release. It happens throughout the project lifecycle with input from the whole team, ensuring the top backlog items stay well defined and actionable.