How often does the Product Owner compare work remaining with previous Sprint Reviews?

The correct choice reflects the Product Owner's role during the Sprint Review, which is to assess progress and gather feedback on the work completed. The comparison of work remaining with previous Sprint Reviews occurs at least every Sprint Review because this is a key moment where the team inspects the increment of the product and assesses how much work is left versus how much was previously expected.

This practice helps the Product Owner to understand trends, make informed decisions about prioritization, and adjust the Product Backlog based on the team’s velocity and feedback received during the review. Engaging in this comparison regularly ensures that stakeholders have a clear understanding of progress and alignment on future goals.

In contrast, the other options suggest either too frequent assessments that do not align with the Scrum framework, or infrequent checks that might hinder the ability of the team to adapt and respond to change effectively. By only focusing on Sprint Reviews, the Product Owner can leverage collective reflections on progress, which is essential for continuous improvement.