1. Introduction
In ISTQB Foundation Level, the whole-team approach is an essential Agile principle. This approach emphasizes collaboration and shared responsibility among all team members. In this post, we analyze Exam B Question 8 to identify the true advantage of the whole-team approach.
[한국어 요약]
Whole-team Approach는 Agile의 핵심 원칙 중 하나로, 팀 전체의 협업과 공동 책임을 강조합니다.
이 글에서는 Exam B Q8 문제를 분석해 어떤 선택지가 진정한 장점인지 설명합니다.
2. Sample Question
Which of the following is an advantage of the whole-team approach?
- a) It allows team members to take on any role at any time
- b) It only needs a single team to support the complete development project
- c) It embeds business representatives alongside developers in the same team
- d) It generates a team synergy that benefits the entire project
3. Correct Answer
✔ Correct Answer: d)
By utilizing each team member’s individual strengths, the whole-team approach naturally enhances collaboration, improves communication, and creates team synergy. This synergy helps the project progress more efficiently and results in better overall outcomes.
[한국어 요약]
정답은 d)입니다. Whole-team Approach는 팀원들의 다양한 능력을 조합하여 강력한 팀 시너지를 만들어내는 것이 가장 큰 장점입니다.
4. Why the Other Options Are Not Correct
a) It allows team members to take on any role at any time
This is not correct. The whole-team approach does encourage flexibility, but it does not claim that every member can perform every role at any time. Members should only take on tasks they are competent and qualified to handle.
[한국어 요약]
a는 틀렸습니다. Whole-team은 역할 유연성을 인정하지만, 모든 팀원이 모든 역할을 할 수 있다는 의미는 아닙니다.
각 팀원은 자신이 충분한 역량을 가진 역할만 맡습니다.
b) It only needs a single team to support the complete development project
Incorrect. The whole-team approach describes how one Agile team internally collaborates. It does not imply that one team is enough for an entire large-scale project. Project size, complexity, and scope determine how many teams are needed.
[한국어 요약]
b는 틀렸습니다. Whole-team은 “하나의 팀 내부 협업 방식”을 말하는 것이지,
전체 프로젝트를 한 팀이 수행할 수 있다는 의미가 아닙니다.
c) It embeds business representatives alongside developers in the same team
Also incorrect. Although collaboration with business representatives (e.g., Product Owner) is important, the whole-team approach does not mean they participate in every decision or activity. Over-involving business roles would slow down the team unnecessarily.
[한국어 요약]
c는 틀렸습니다. 비즈니스 담당자와 협력은 중요하지만,
그들이 모든 기술적 의사결정에 참여해야 한다는 뜻은 아닙니다.
모든 일에 관여하면 오히려 팀 속도가 저하됩니다.
5. Summary
The whole-team approach enhances collaboration, encourages shared responsibility, and creates strong team synergy—this is why option d is the correct answer. Understanding this helps testers apply Agile principles more effectively in real projects.
[한국어 요약]
Whole-team Approach의 핵심은 협업 강화와 팀 시너지 창출입니다.
이 때문에 d가 올바른 선택지입니다.
Related: More ISTQB posts