Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 1.3The Whole-Team Approach, it states:
"The whole-team approach involves all team members (including developers, testers, and business representatives) working together as a team, sharing responsibility for the quality of the product."
It also says:
"In Agile projects, the whole-team approach promotes collaboration and communication across roles to achieve common goals, including quality assurance."
Thus,Option Bis correct, as it captures thecollaborative nature and shared responsibilitythat the whole-team approach aims to foster.
Option Arefers toPlanning Poker or relative estimation, not directly the whole-team concept.
Option Cdescribes the"Three Cs" (Card, Conversation, Confirmation)model of user stories, not the whole-team approach specifically.
Option Dmisinterprets Agile; while team members are encouraged to becross-functional, deep expertise is still valued, and "generalist only" is not a requirement of the whole-team approach.
[References:, CTFL-AT Syllabus v4.0, Section 1.3, Learning Objective (K2) – Understand benefits of the whole-team approach, ===========, ]
Submit