The Chief Scrum Master is a part of the Scrum Core Team that assembles to retrospect the project and to identify, document, and internalize the…

The Retrospect Project process is conducted at the end of a project to identify, document, and internalize lessons learned. According to the Scrum Body of Knowledge (SBOK™ Guide), the primary reference for the ScrumStudy SMC certification, several tools can be used during the Retrospect Project Meeting. These include Speed Boat, a technique to identify what helped the project (wind in the sails) and what hindered it (anchors). Additionally, SWOT Analysis (Strengths, Weaknesses, Opportunities, Threats) and Gap Analysis are listed as formal techniques to assess project performance and identify areas for improvement in future projects. Therefore, all three options are correct.

C. Proof of Concept: A Proof of Concept is used to validate the feasibility of a technical approach or business idea before or during development, not as a tool for retrospective analysis after a project is complete.

1. A Guide to the Scrum Body of Knowledge (SBOK™ Guide)

3rd Edition. (2017). SCRUMstudy

VMEdu

Inc.

Section 14.2.2

Tools for Retrospect Project: This section explicitly lists the tools used in this process.

Section 14.2.2.2

Speed Boat: "Speed Boat is a technique that can be used to conduct the Retrospect Project Meeting." (p. 318)

Section 14.2.2.5

SWOT Analysis: "SWOT analysis is another tool that can be used during the Retrospect Project Meeting to identify the strengths

weaknesses

opportunities

and threats for the project." (p. 319)

Section 14.2.2.6

Gap Analysis: "Gap analysis can be used to compare the project’s actual performance with the desired or planned performance." (p. 319)

Section 8.3.2.5

Proof of Concept: This tool is described as part of the 'Create Deliverables' process

used to "prevent wasted time and effort on approaches that may not work." (p. 198)