1. Introduction
Early and frequent feedback is an important concept emphasized in modern development approaches such as Agile. This question asks which benefit directly relates to receiving feedback early and often.
Note (EN/KR):
Early feedback reduces misunderstandings and helps teams correct issues before they grow.
초기·지속적인 피드백은 오해를 줄이고 문제를 크게 만들기 전에 수정할 수 있도록 돕습니다.
2. Key Concepts
-
Early Feedback – receiving comments, insights, or corrections as early as possible.
초기 피드백: 가능한 한 빠르게 의견과 수정 포인트를 받는 것. -
Frequent Feedback – repeating this process regularly to avoid late surprises.
지속적 피드백: 피드백을 반복적으로 받아 늦은 단계에서의 문제를 방지. -
Main Benefit: Helps teams align on requirements, preventing misunderstandings.
핵심 장점: 요구사항에 대한 오해를 줄이고 팀 간 이해를 맞추는 데 도움.
3. Practice Question
❓ Question
Which of the following is a benefit of early and frequent feedback?
- a) It improves the test process for future projects
- b) It forces customers to prioritize their requirements based on agreed risks
- c) It provides a measure for the quality of changes
- d) It helps avoid requirements misunderstandings
✅ Correct Answer: d)
📘 Explanation (EN/KR)
-
a) Not correct. Feedback can help improve future test processes, but this does not require feedback to be early or frequent.
피드백은 향후 테스트 프로세스 개선에 도움 되지만, 그것이 반드시 조기·지속적인 피드백을 의미하지는 않습니다. -
b) Not correct. Feedback does not force customers to prioritize requirements; prioritization is based on business value and risk.
피드백은 고객이 요구사항 우선순위를 강제로 정하게 하는 요소가 아닙니다. -
c) Not correct. There is no single recommended way to measure the quality of changes. This is not listed as a benefit of early feedback.
변경 품질을 측정하는 표준 방식은 없으며, 이는 초기 피드백의 장점으로 언급되지 않습니다. -
d) Correct. Early and frequent feedback helps clarify expectations and prevents misunderstandings about requirements.
조기·지속적인 피드백은 요구사항 오해를 줄이고 기대치를 명확히 하는 데 가장 효과적입니다.
✔ Therefore, option (d) is the correct benefit of early and frequent feedback.
✔ 따라서 (d)가 조기·지속적 피드백의 실제 장점입니다.
📊 Summary Table
| Option | Statement Summary | Correct? | Explanation |
|---|---|---|---|
| a | Improves test process for future projects | ❌ No | Doesn't require early or frequent feedback 조기·지속적일 필요 없음 |
| b | Forces customers to prioritize requirements | ❌ No | Prioritization is not based on feedback 우선순위는 피드백 기반이 아님 |
| c | Provides measure of change quality | ❌ No | Not listed as a benefit 장점으로 언급되지 않음 |
| d | Prevents requirements misunderstandings | ✔ Yes |
Early feedback clarifies expectations 초기 피드백으로 기대치 명확화 |
4. Summary & Call to Action
Early and frequent feedback reduces misunderstandings, improves collaboration, and supports faster correction of issues before development progresses too far.
초기·지속적인 피드백은 오해를 줄이고 협업을 강화하며, 개발이 너무 진행되기 전에 문제를 빠르게 수정할 수 있도록 도와줍니다.
refer to : FL-3.2.1
Related: More ISTQB Posts