A Scrum team working on multiple epics complains that they are constantly being pushed to complete more work than they think can be completed. Apparently, the product owner has constantly overloaded each of the past 8 sprints. Which single report can instantly prove their statement?

The Velocity Chart is the most appropriate report to instantly prove the team's statement. This chart visually compares the amount of work the team committed to at the start of a sprint (Commitment) against the amount of work they actually completed (Completed). If the product owner has consistently overloaded sprints, the chart will display a clear pattern over the past 8 sprints where the 'Commitment' bar is consistently taller than the 'Completed' bar. This provides immediate, historical evidence to support the team's claim of being overloaded.

B. Cumulative Flow Diagram: This diagram tracks the status of work items over time, showing workflow and identifying bottlenecks, but it does not directly compare sprint commitments to completed work.
C. Sprint Report: This report details the outcome of a single sprint. While useful, it would require examining eight separate reports to see the pattern, failing to "instantly prove" the statement in one view.
D. Control Chart: This chart measures the cycle time for individual issues, focusing on the efficiency and predictability of completing work items, not the overall sprint scope versus capacity.
E. Epic Burndown: This report tracks progress against a single epic. The scenario involves multiple epics and the problem is at the sprint level, making this report too narrowly focused.

1. Atlassian Documentation, "Velocity Chart": "The Velocity Chart shows the amount of value delivered in each sprint... The chart tracks the following: Commitment: The total estimate of all issues in the sprint when it begins. Completed: The total estimate of all issues completed in the sprint." This source confirms the chart's primary function is to compare committed vs. completed work per sprint. (Source: Atlassian, Jira Software Cloud Documentation, "Reports", "Velocity Chart").

2. Atlassian Documentation, "Sprint Report": "The Sprint Report shows a list of issues in each sprint. It's useful for your Sprint Retrospective meetings, and for mid-sprint progress checks." This confirms its scope is limited to a single sprint. (Source: Atlassian, Jira Software Cloud Documentation, "Reports", "Sprint Report").

3. Atlassian Documentation, "Cumulative Flow Diagram": "The cumulative flow diagram is an area chart that shows the various statuses of work items for a particular project over time." This highlights its focus on workflow states rather than sprint commitments. (Source: Atlassian, Jira Software Cloud Documentation, "Reports", "Cumulative Flow Diagram").