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

The primary objective of the Retrospect Sprint Meeting is to inspect the previous Sprint with regard to the processes, tools, people, and relationships within the Scrum Team. The team collaboratively discusses what went well, what could be improved, and creates a plan for implementing process improvements in the next Sprint. This meeting is focused on improving the team's effectiveness and quality of work (how the team works). Identifying new product features (what the team builds) is outside the scope of this meeting; that function is managed in the Product Backlog and addressed during events like Product Backlog Refinement and Sprint Planning.

A. Identifying process improvements is a core objective of the Sprint Retrospective, as the team seeks to adapt and enhance its way of working.

B. Identifying best practices is part of reflecting on what went well, ensuring that successful techniques are continued in future Sprints.

D. Identifying process problems and bottlenecks is a fundamental purpose of this meeting, allowing the team to address impediments and improve workflow.

1. SCRUMstudy

A Guide to the Scrum Body of Knowledge (SBOK® Guide)

3rd Edition.

Page 295

Section 12.3: The guide states

"The purpose of the Retrospect Sprint Meeting is for the Scrum Team to inspect the previous Sprint

identify what went well and what did not

and make improvements for future Sprints." It explicitly focuses on process

not product features. The outputs listed are "Agreed upon Actionable Improvements" and "Updated Scrum Guidance Body Recommendations

" which relate to process enhancement.

2. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide.

Page 10

"Sprint Retrospective": "The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went with regards to individuals

interactions

processes

tools

and their Definition of Done." This definition clearly excludes the discussion of new product functionality.

3. Stray

V.

Sjøberg

D. I.

& Dybå

T. (2016). The daily stand-up meeting: A grounded theory study. Journal of Systems and Software

114

101-124.

DOI: https://doi.org/10.1016/j.jss.2016.01.004

While focused on the daily stand-up

this and similar academic studies on Scrum meetings consistently differentiate the purpose of each ceremony. The retrospective is universally defined in academic literature as a mechanism for process improvement and team reflection

distinct from product planning activities.