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
  15% (8)
• B
  71% (37)
• C
  4% (2)
• D
  10% (5)

Explanation

The Scrum Master's role includes facilitating transparency and communication across the team and stakeholders, making them the most appropriate person to compile and present a summary report of Sprint outcomes such as new functionality and defect activity. The Product Owner (A) focuses on backlog prioritization and product vision - their lens is on what comes next, not documenting what was completed. The Development Team (C) is responsible for delivering the work itself; burdening them with report preparation at Sprint end distracts from Sprint Review participation and Retrospective engagement. Option D (no report) is tempting if you're thinking of pure Scrum, where the Sprint Review meeting replaces formal reports - but this question asks who best prepares one if required, so eliminating all options isn't the right move here.

Memory tip: Think of the Scrum Master as the "process steward" - anything related to tracking, transparency, and communicating team progress to the organization falls in their lane, even if it's not a Scrum artifact by name.

No community discussion yet for this question.