SMC practice question 7 of 25

Which of the following is NOT an objective of a Retrospect Sprint Meeting?

Full set: 148 questions

Domain Review and Retrospect Phase

Answer options
A: Identify process improvements
B: Identify best practices
C: Identify new product features Correct answer
D: Identify process problems and bottlenecks
Correct Answer:
C. Identify new product features
Explanation

The Retrospect Sprint Meeting is focused on inspecting and adapting the process, not the product. Its objectives are to reflect on the completed Sprint to identify what went well, what did not go well, and what can be improved for the next Sprint. This includes discussing team dynamics, tools, and processes. Identifying new product features is the purpose of other activities and meetings, such as Prioritized Product Backlog Grooming, and is driven by the Product Owner based on stakeholder needs and business value. The retrospective is strictly for process improvement.

Why Incorrect

A. Identifying process improvements is the primary goal of the Retrospect Sprint Meeting.
B. Discussing what went well helps the team recognize and continue using effective practices.
D. Identifying problems and bottlenecks is crucial for creating an action plan to improve in the next Sprint.

References

1. A Guide to the Scrum Body of Knowledge (SBOK® Guide), 3rd Edition. SCRUMstudy, VMEdu, Inc., 2017, Section 12.1, p. 279. "The purpose of this meeting is to identify opportunities for improvement in the Sprint that has just concluded, which can be implemented in future Sprints."

2. A Guide to the Scrum Body of Knowledge (SBOK® Guide), 3rd Edition. SCRUMstudy, VMEdu, Inc., 2017, Figure 12-2, p. 281. The outputs of the Retrospect Sprint process are "Agreed Actionable Improvements," "Assigned Action Items and Due Dates," and "Updated Scrum Guidance Body Recommendations," none of which include new product features.

Scroll to Top