In a Scrum retrospective, which of the following categories are used to classify the feedback from the team?
Click on the arrows to vote for the correct answer
A. B. C. D.C.
In a Scrum retrospective, the team gathers feedback to identify what went well and what could be improved during the sprint. This feedback is usually categorized into the following two categories:
A. Direct and indirect feedback: Direct feedback is feedback that is provided directly to the person or team being reviewed. For example, if a team member provides feedback to another team member during a sprint review, that would be considered direct feedback. Indirect feedback is feedback that is provided through a third party. For example, if a team member provides feedback about another team member to the Scrum Master, that would be considered indirect feedback.
It is important to consider both direct and indirect feedback because it provides a well-rounded view of what went well and what could be improved during the sprint. Direct feedback is important because it allows team members to address issues immediately, while indirect feedback provides insights that might not have been recognized otherwise.
B. Pros and cons: This category of feedback is focused on identifying what worked well and what did not work well during the sprint. The team identifies the positive aspects of the sprint, such as accomplishments or successful team collaborations, as well as the negative aspects, such as missed deadlines or communication breakdowns.
C. Pluses and minuses: This is another way of categorizing pros and cons feedback. The team identifies the pluses or positives of the sprint, and the minuses or negatives of the sprint.
D. Likes and dislikes: This category of feedback is focused on identifying what team members enjoyed and did not enjoy about the sprint. This type of feedback is useful for understanding how team members feel about the work they are doing and can help identify areas where team morale could be improved.
Overall, the goal of categorizing feedback during a Scrum retrospective is to identify trends and areas of improvement. By grouping feedback into categories, the team can more easily identify patterns and make actionable plans to improve their processes in the next sprint.