What should be the first step a team should take to feed potential problems into the Problem-Solving workshop?

A. Review feedback from the System Demo

B. Identify enablers needed to build out the Architectural Runway

C. Conduct a short team retrospective

D. Analyze quantitative & qualitative metrics

Correct Answer is

C. Conduct a short team retrospective

Explanation

The first step a team should take to feed potential problems into the problem-solving workshop is to conduct a short team retrospective.

Here’s why this step is crucial and precedes others:

• Review feedback from the System Demo: While feedback from the System Demo is valuable, it primarily focuses on what was delivered and how it was received by stakeholders. This feedback might not capture all the underlying problems or challenges faced by the team during the iteration.


• Identify enablers needed to build out the Architectural Runway: Identifying enablers is important for future planning and ensuring the team can deliver value continuously. However, this step is more about addressing future needs rather than identifying current or past problems.


• Conduct a short team retrospective: This is the correct first step. A retrospective provides a structured way for the team to reflect on their work, processes, and challenges encountered during the iteration. It’s a dedicated time to identify what went well, what didn’t, and what could be improved. The insights gained from a retrospective directly feed into identifying potential problems for the Problem Solving workshop, making it the most logical and effective starting point.


• Analyze quantitative & qualitative metrics: While analyzing metrics is important for understanding performance and outcomes, it’s a step that ideally follows the identification of problems. Metrics can help quantify the impact of identified problems and track improvements over time, but they might not alone reveal the root causes of issues without the context and insights gained from a team retrospective.

Conducting a short team retrospective allows the team to collaboratively reflect on and identify issues based on their recent experiences, making it the most effective and inclusive way to surface potential problems for further exploration in a Problem-Solving workshop.

Other SAFe Scrum Master Question – What is one problem with phase-gate Milestones?