The purpose of a retrospective is to allow a team to inspect and improve their methods and teamwork. Three questions should be asked and discussed during a retrospective: What is going well? What could we do differently? What areas could
be improved? Solutions are validated when they are identified. If successful, they can be added as part of the ongoing process. If solutions fail, the team can decide to try something else or go back to the earlier process. The other
responses are incorrect. The point of a retrospective is to improve upon approach, not air grievances; the team doesn’t switch roles in a retrospective; before each iteration begins, the product owner will prioritize the product backlog,
not in the retrospective.