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

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

• A. Sprint Backlog for the next Sprint
• B. The current state of the codebase
• C. The value of work in the Product Backlog
• D. Improvement of team dynamics

Answer: (A)

In a Sprint Retrospective, the focus is on reflecting on the past Sprint with the aim of identifying areas for improvement in team processes, collaboration, and practices. This meeting is intended to foster discussions that will help the team enhance its performance in future Sprints. Focusing on the Sprint Backlog for the next Sprint is not appropriate for a Sprint Retrospective. This is primarily because the Retrospective is retrospective in nature; it looks back at the completed Sprint rather than planning for the next one. Discussions about what will be worked on in the future Sprint belong in Sprint Planning, where the team collaboratively determines the next steps based on prioritized items from the Product Backlog. The other topics mentioned, such as the current state of the codebase, the value of work in the Product Backlog, and team dynamics, are relevant to the focus of a Sprint Retrospective. They each contribute to understanding how the team can improve and operate more effectively, making discussion around them valuable for continuous improvement.

In a Sprint Retrospective, the focus is on reflecting on the past Sprint with the aim of identifying areas for improvement in team processes, collaboration, and practices. This meeting is intended to foster discussions that will help the team enhance its performance in future Sprints.

Focusing on the Sprint Backlog for the next Sprint is not appropriate for a Sprint Retrospective. This is primarily because the Retrospective is retrospective in nature; it looks back at the completed Sprint rather than planning for the next one. Discussions about what will be worked on in the future Sprint belong in Sprint Planning, where the team collaboratively determines the next steps based on prioritized items from the Product Backlog.

The other topics mentioned, such as the current state of the codebase, the value of work in the Product Backlog, and team dynamics, are relevant to the focus of a Sprint Retrospective. They each contribute to understanding how the team can improve and operate more effectively, making discussion around them valuable for continuous improvement.