A new agile project is starting. The project manager is asked to confirm the scope to address the concerns of one of the stakeholders. What should the project manager use to explain the project scope?

User stories are individual items within the product backlog, describing specific features from an end-user perspective, but they don't represent the entire project scope on their own.

The product backlog is the definitive source of all requirements and features for an agile project, listed in a prioritized order. It explicitly defines the current scope of the project and is continuously refined, making it the ideal tool to explain what the project encompasses to a stakeholder.

A product roadmap provides a high-level, strategic view of the product's evolution over time, but it lacks the detailed granularity needed to confirm the current project scope.

Business requirements documents are typically associated with traditional, waterfall methodologies and are less common or comprehensive for scope definition in agile projects, where the product backlog is preferred.