Back to Importance of Scrum Retrospectives

Feedback

5 minutes 5 Questions

Feedback is the cornerstone of Scrum retrospectives. At its core, a retrospective is a feedback session about the sprint that has just ended. It offers a dedicated avenue for providing and receiving feedback from peers. Feedback within this context is used both in a positive sense (praise, acknowle…

Feedback in Scrum Retrospectives Guide

The Scrum Retrospective is an important part of the Scrum methodology. It's a meeting that takes place after each sprint. The purpose is to reflect on the sprint that just finished and identify opportunities for improvement.

Why is it important?
Feedback in scrum retrospective is crucial because it allows the team to reflect on their work and find ways to improve. It brings transparency and fosters a culture of continuous improvement.

What is it?
Feedback is the team's thoughts, observations, and opinions about the last sprint. It covers what worked well, what didn't, and what improvements can be made for the next sprint.

How does it work?
Each team member has the opportunity to express their feedback. Then, the team discusses the feedback and decides on actions for improvement.

Exam Tips: Answering Questions on Feedback
When answering exam questions on feedback in scrum retrospectives, remember the following:

Be clear: Ensure you understand what the question is asking
Be concise: Keep your answers to the point
Use examples: Use practical examples to demonstrate understanding

Test mode:

Exam (Timed)

Practice (With explanations)

Start practice test

CSM - Feedback Example Questions

Test your knowledge of Feedback

Question 1

During a Sprint Review, the Scrum Team receives feedback from stakeholders about a recently completed feature. Some stakeholders suggest changes that could significantly improve the user experience. However, implementing these changes would require additional time and effort. What should the Scrum Team do?

Document the feedback, discuss it during the Sprint Retrospective, and consider it for future sprints based on priority and capacity. Immediately start working on the changes, even if it means extending the current sprint to accommodate the extra work. Defer the feedback to the next sprint planning without further discussion, as the current sprint goals have already been met. Implement the changes right away and present the updated feature in the next Sprint Review, ensuring the stakeholders' feedback is incorporated promptly.

Correct Answer: Document the feedback, discuss it during the Sprint Retrospective, and consider it for future sprints based on priority and capacity.

The best approach is to document the feedback received during the Sprint Review and discuss it during the Sprint Retrospective. The Sprint Review is primarily intended to gather feedback and insights, not to make immediate changes to the product. The Scrum Team should prioritize the feedback based on its value and align it with the product goals. During the Sprint Retrospective, the team can discuss how to incorporate the feedback in future sprints, considering the available capacity and other priorities. Making significant changes immediately or extending the current sprint goes against the principles of Scrum, which emphasize maintaining a sustainable pace and adhering to the sprint goals. Deferring the feedback without further discussion may lead to missed opportunities for improvement and neglect valuable stakeholder input. By documenting the feedback, discussing it in the Sprint Retrospective, and considering it for future sprints, the Scrum Team can effectively address stakeholder suggestions while maintaining the integrity of the Scrum framework.

Question 2

After releasing a new software update, the team starts receiving a mix of positive and negative feedback from users. It’s challenging to navigate through the feedback and prioritize actions. What should be the approach in this scenario?

Ignore the negative feedback and focus on the positive ones. Use a feedback matrix to prioritize and classify the feedback responses based on their impact and urgency. Immediately fix issues from all negative feedbacks. Completely roll back the software update.

Correct Answer: Use a feedback matrix to prioritize and classify the feedback responses based on their impact and urgency.

The best approach in such scenario is to 'use a feedback matrix to prioritize and classify the feedback responses based on their impact and urgency.' This approach is the most efficient because it considers all feedback, both positive and negative, and prioritizes them based on their importance and urgency. This ensures the most crucial and impactful issues are addressed first. The option to 'ignore the negative feedback and focus on the positive ones' is not sensible as it disregards potentially critical issues that need rectification. Similarly, 'immediately fix issues from all negative feedbacks' can cause teams to spread resources too thin and not address the most impactful issues first. Furthermore, 'completely roll back the software update' is a drastic measure that should only be considered if the update causes significant disruption or issues. This is not indicated by the scenario as it mentions a mix of positive and negative feedback.

Question 3

A team member consistently provides feedback that is not constructive or relevant to the project. How should the team lead handle this?

Demand that the team member only provide positive feedback. Provide one-on-one coaching for the team member on how to give effective and constructive feedback. Ask other team members to provide feedback on the team member's behavior, hoping it will lead to self-improvement. Ignore the team member's feedback and continue the project as planned. Immediately remove the team member from the project. Discourage the team member from participating in any discussions or meetings.

Correct Answer: Provide one-on-one coaching for the team member on how to give effective and constructive feedback.

Coaching the team member on giving effective feedback promotes personal growth and improves team dynamics. The other options do not solve the issue or might create a negative work environment, which goes against Agile principles.

🎓 Unlock Premium Access

Certified ScrumMaster + ALL Certifications

🎓 Access to ALL Certifications: Study for any certification on our platform with one subscription
3861 Superior-grade Certified ScrumMaster practice questions
Unlimited practice tests across all certifications
Detailed explanations for every question
CSM: 5 full exams plus all other certification exams
100% Satisfaction Guaranteed: Full refund if unsatisfied
Risk-Free: 7-day free trial with all premium features!

Start Your Free 7-Day Trial