The product owner needs to know how many user stories have been completed during a two‑week sprint. How should the project manager respond?

The burndown chart is the most appropriate tool to share with the Product Owner because it visually represents the remaining work in a sprint against time. It clearly shows the progress of user stories completed and the team's velocity, directly answering the Product Owner's need for a quantitative update on completed work. Using retrospectives to report completed work is incorrect because retrospectives are for process improvement, not for reporting sprint progress. Inviting the Product Owner to standup meetings is good for transparency but doesn't provide a consolidated, visual overview of completed stories as effectively as a burndown chart. Having a face-to-face conversation is a valid communication method, but it's less efficient and less data-driven than providing a burndown chart for this specific request.