CTFL 1.5.2: Recall the advantages of the whole team approach
K1Syllabus section 1.5.2
3 original PrepBench practice questions for learning objective 1.5.2 of the CTFL 4.0 syllabus. Try the examples below and check each answer against its syllabus reference.
Practice questions
Question 1
Which outcome follows from team members sharing the same physical or virtual workspace in the whole team approach?
- A high level of test independence is preserved
- Communication and interaction among team members are facilitated
- Testing becomes the sole responsibility of members with testing skills
- Business representatives decide on test automation without developers
Show answer
- A high level of test independence is preservedA shared workspace supports interaction; the approach does not preserve a high level of test independence.
- Correct answer: Communication and interaction among team members are facilitatedCo-location in a physical or virtual workspace facilitates communication and interaction.
- Testing becomes the sole responsibility of members with testing skillsEveryone is responsible for quality, and any team member with the necessary skills may perform a task.
- Business representatives decide on test automation without developersTesters work with developers to decide on test automation approaches; business representatives do not decide alone.
A shared physical or virtual workspace facilitates communication and interaction among team members. The whole team approach makes everyone responsible for quality, while testers collaborate with business representatives on suitable acceptance tests and with developers on test strategy and test automation. A high degree of independence may instead be needed in contexts such as safety-critical work.
Syllabus section 1.5.2
Question 2
Which of the following is a stated benefit of the whole team approach?
- It creates synergy by letting the team's various skill sets be leveraged for the project
- It gives one nominated owner clear accountability for the product's quality
- It keeps testers' judgement free of the team's own assumptions about the product
- It lets safety-critical work rely on the team rather than on separate independent testers
Show answer
- Correct answer: It creates synergy by letting the team's various skill sets be leveraged for the projectCreating synergy from the team's various skill sets is a stated benefit of the approach.
- It gives one nominated owner clear accountability for the product's qualityEveryone on the team is responsible for quality, so accountability is shared rather than assigned to one owner.
- It keeps testers' judgement free of the team's own assumptions about the productDistance from the team's assumptions describes independence of testing; the whole team approach shares a workspace.
- It lets safety-critical work rely on the team rather than on separate independent testersThe approach may not always be appropriate: safety-critical situations may still need high independence.
The whole team approach improves team dynamics, enhances communication and collaboration within the team, and creates synergy by allowing the various skill sets within the team to be leveraged for the benefit of the project. In it, any team member with the necessary knowledge and skills can perform any task, and everyone is responsible for quality.
Syllabus section 1.5.2
Question 3
In which situation might the whole team approach NOT be appropriate?
- When the whole team shares a single co-located workspace
- When all the team members are willing to collaborate closely
- When everyone on the development team is responsible for quality
- When a high level of test independence is needed, e.g. safety-critical
Show answer
- When the whole team shares a single co-located workspaceA shared co-located workspace supports the whole team approach, not a reason against it.
- When all the team members are willing to collaborate closelyWillingness to collaborate suits the whole team approach rather than ruling it out.
- When everyone on the development team is responsible for qualityShared responsibility for quality is a feature of the whole team approach, not a limit.
- Correct answer: When a high level of test independence is needed, e.g. safety-criticalWhere high test independence is needed (e.g. safety-critical), it may not fit.
The whole team approach may not always be appropriate depending on context. For instance, in some situations such as safety-critical development, a high level of test independence may be needed, which the whole team approach does not provide.
Syllabus section 1.5.2
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.