1. Introduction
A key idea in modern testing is the shift-left approach: start testing activities as early as possible. One important early testing activity is reviewing work products (e.g., requirements, designs, user stories). This question asks which review practice is best for all software development lifecycles.
[한국어 요약]
요즘 테스트에서는 Shift-left 개념이 중요합니다.
즉, 요구사항·설계 같은 산출물을 가능한 한 일찍 리뷰하는 것이 핵심입니다.
이 문제는 어떤 리뷰 방식이 모든 SDLC에 공통으로 좋은 방식인지 묻습니다.
2. Sample Question
Which of the following is a good testing practice that applies to all software development lifecycles?
- a) Testers should review work products as part of the next development phase
- b) Testers should review work products as soon as drafts are available
- c) Testers should review work products before test analysis and test design begin
- d) Testers should review work products immediately after they are published
3. Correct Answer
✔ Correct Answer: b)
Option b) is correct because reviewing work products as soon as drafts are available supports early defect detection. This is a core part of the shift-left approach and works in sequential, iterative, and agile lifecycles.
[한국어 요약]
정답은 b)입니다.
초안이 나오는 즉시 테스터가 리뷰하면, 결함을 가장 이른 시점에 발견할 수 있어 모든 SDLC에서 좋은 관행이 됩니다.
4. Why the Other Options Are Not Correct
a) Review in the next development phase — ✖ Not correct
If testers wait until the next phase, flawed work products may already have been used to create design, code, or test cases. This leads to rework and extra cost. It is not true shift-left testing.
[한국어 요약]
a는 틀렸습니다. 다음 단계까지 기다리면, 이미 그 결함 있는 문서를 기반으로 개발·테스트가 진행되어 재작업이 커집니다.
b) Review as soon as drafts are available — ✔ Correct
This is the best practice. Early reviews of draft requirements, designs, and user stories allow defects to be found before implementation starts. This reduces cost and supports high quality.
[한국어 요약]
b는 초안 단계에서 바로 리뷰하므로 결함을 가장 싸고 빠르게 잡을 수 있는 이상적인 방식입니다.
c) Review before test analysis and design begin — ✖ Not correct
Testers typically review the test basis (requirements, user stories, etc.) as part of test analysis. The statement suggests a timing that does not match the usual structured process.
[한국어 요약]
c는 Test Analysis 과정 안에서 리뷰가 이루어진다는 일반적인 흐름과 맞지 않습니다.
d) Review after work products are published — ✖ Not correct
If testers wait until documents are final and published, then any defects they find are already in the official version. Fixing them will be more expensive and cause more disruption.
[한국어 요약]
d는 문서가 이미 “공식 배포”된 후에야 결함을 찾는다는 뜻이라, 너무 늦은 시점의 리뷰입니다.
5. Summary
A good testing practice for all lifecycles is to review work products as early as possible. Reviewing drafts enables shift-left testing, reduces rework, and improves quality— which is why option b) is the best answer.
[한국어 요약]
모든 SDLC에서 공통으로 좋은 테스트 관행은 “가능한 한 이른 시점에 리뷰하는 것”입니다.
초안 단계 리뷰(선택지 b)가 Shift-left와 품질 향상에 가장 잘 부합합니다.
Related: More ISTQB posts