At the start of a new agile project, a stakeholder asks for confirmation of the scope. What should the project manager use to explain the project scope?

The product backlog is the correct answer because it is a prioritized list of all known features, functions, requirements, enhancements, and fixes needed for the product. In an agile context, it serves as the single source of truth for all work to be done and effectively defines the project scope. User stories are individual items within the product backlog, but they don't represent the entire scope on their own. The product roadmap provides a high-level, strategic view of the product's evolution over time, not the detailed scope for the current project. A business requirements document (BRD) is a traditional project management artifact and is less common in agile projects, where the product backlog fulfills a similar purpose but with more flexibility and iterative refinement.