1. Introduction
Retrospectives are a structured opportunity for the team to reflect on the last release cycle and identify process improvements. They play a central role in continuous improvement and help teams evolve their practices over time. This question asks which argument BEST justifies holding retrospectives regularly.
[한국어 요약]
회고는 팀이 지난 작업을 돌아보고 프로세스를 개선할 기회를 제공하는 중요한 활동입니다.
이 문제는 매 릴리즈마다 회고를 해야 하는 가장 타당한 이유를 묻습니다.
2. Sample Question
Which of the arguments below would you use to convince your manager to organize retrospectives at the end of each release cycle?
- a) Retrospectives are popular and clients would appreciate us adding them
- b) Retrospectives save money because they gather immediate product feedback
- c) Retrospectives help identify process weaknesses that feed into continuous process improvement
- d) Retrospectives embrace values like courage and respect that are essential for improvement
3. Correct Answer
✔ Correct Answer: c)
Option c is correct because retrospectives are a direct mechanism for identifying process weaknesses and generating actionable items for a continuous improvement program. When teams regularly reflect and follow up on identified issues, process quality increases over time.
[한국어 요약]
정답은 c)입니다.
회고는 프로세스의 약점을 발견하고 이를 개선 활동으로 연결해 조직의 지속적 개선을 가능하게 합니다.
4. Why the Other Options Are Not Correct
a) Retrospectives are popular with clients — ✖ Not correct
Retrospectives are an internal team activity and have very little relevance to clients. Their purpose is process improvement, not customer satisfaction.
[한국어 요약]
a는 틀렸습니다. 회고는 내부 프로세스 개선을 위한 활동이며, 고객과는 관련이 거의 없습니다.
b) Retrospectives collect product feedback — ✖ Not correct
Retrospectives focus on process improvement, not product feedback. End-user feedback is gathered differently (e.g., reviews, demos), and users do not participate in retrospectives.
[한국어 요약]
b는 틀렸습니다. 회고는 제품 피드백이 아닌 팀·프로세스 개선을 위한 활동입니다.
d) Retrospectives embrace courage and respect — ✖ Not correct
Courage and respect are values from Extreme Programming (XP), not retrospectives specifically. They are not the primary reason for holding retrospectives.
[한국어 요약]
d는 XP의 핵심 가치 설명일 뿐, 회고를 해야 하는 이유와 직접적 관련이 없습니다.
5. Summary
The strongest justification for holding retrospectives is that they enable systematic, continuous process improvement.
By identifying and acting on process weaknesses every cycle, teams steadily improve their effectiveness and product quality.
refer to FL-2.1.6
[한국어 요약]
회고는 팀의 프로세스를 지속적으로 개선할 수 있게 해주는 핵심 활동입니다.
따라서 가장 설득력 있는 근거는 프로세스 약점 파악 및 개선 활동 연결입니다.
Related: More ISTQB posts