A customer brings a new requirement and requests a rough estimate. The task resembles a previous deliverable. How should the product owner respond?

The correct answer is to review the similar user story, note its story points and velocity, and sketch the time required for the new requirement. In an agile context, user stories and story points are used to estimate effort. Velocity helps predict how much work a team can complete in an iteration. By comparing the new requirement to a similar, previously estimated user story, the product owner can leverage existing data to provide a rough, relative estimate. Reviewing the current backlog and backlog refinement to identify gaps for fulfilling the requirement is a good practice but doesn't directly address providing a rough estimate for the new requirement. Examining the WBS and cost estimate for similar work is more aligned with traditional project management and less with agile estimation techniques like story points. Consulting the lessons learned register for prior effort and experience is valuable for process improvement but less direct for providing a quick, rough estimate for a new, specific requirement.