A customer requests a report that summarizes functionality added and defects found and fixed, right at the end of a Sprint. Who may best prepare this report?

Question

Options

• AThe Product Owner
• BThe Scrum Master
• CThe team
• DThis type of report should not be prepared.

• A
  6% (2)
• B
  77% (27)
• C
  14% (5)
• D
  3% (1)

Explanation

B is correct because the Scrum Master's role includes facilitating transparency, tracking sprint progress, and communicating outcomes to stakeholders - making them the natural fit to compile and present a summary of functionality added and defects resolved at sprint's end.

A (Product Owner) is wrong because the PO focuses on the product backlog, prioritization, and business value - not on generating internal progress reports. Their concern is what to build next, not documenting what was just completed.

C (The Team) is wrong in this context because the development team's responsibility is delivering the Increment, not producing administrative reports. While they inform the content, the Scrum Master owns the reporting function.

D is a trap - this type of sprint summary report is entirely appropriate and useful for stakeholders, release notes, and organizational transparency.

Memory tip: Think "SM = Status + Metrics." The Scrum Master handles anything that communicates sprint health and progress outward to the organization, while the team handles the work and the PO handles the what and why.

No community discussion yet for this question.