Which two of the following are appropriate topics for discussion during a Sprint Retrospective? (Choose two.)

The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Scrum Team inspects the last Sprint regarding individuals, interactions, processes, tools, and its Definition of Done. Therefore, discussing how the team collaborates (interactions) and identifying high-priority process improvements are central to this event. The outcome is an actionable plan for improvement in the upcoming Sprint, which may include adding specific improvement items to the next Sprint Backlog.

B. The order of items in the Product Backlog is the accountability of the Product Owner and is typically discussed during Product Backlog refinement, not the Sprint Retrospective.
D. Documenting acceptance criteria is an activity of Product Backlog refinement, which focuses on preparing items for future Sprints, not inspecting the process of the completed Sprint.

1. Schwaber

K.

& Sutherland

J. (2020). The Scrum Guide. Scrum.org.

Page 12

"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 supports option C).

Page 12

"Sprint Retrospective": "The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the next Sprint." (This supports option A).

Page 9

"Product Backlog": "The Product Owner is also accountable for effective Product Backlog management

which includes: ... Ordering Product Backlog items". (This supports the reasoning for why option B is incorrect for this event).

2. Dingsøyr

T.

Dybå

T.

& Moe

N. B. (2018). A systematic review of the factors that contribute to the success of software process improvement. IEEE Transactions on Software Engineering

44(6)

588-605. https://doi.org/10.1109/TSE.2017.2699822

Section 3.2.2

"Retrospectives": The paper analyzes retrospectives as a key practice for continuous improvement

emphasizing their role in reflecting on the process and team collaboration to identify actionable improvements

which aligns with options A and C.

3. University of California

Berkeley. (n.d.). CS 169 Software Engineering Course Materials. EECS Department.

In lectures on Agile and Scrum

the Sprint Retrospective is defined as the event for the team to reflect on its own process ("what went well

what could be improved") and create a plan for improvements in the next Sprint. This distinguishes it from product-focused activities like backlog ordering or writing acceptance criteria.