CTFL-AT Exam Dumps - Certified Tester Foundation Level Agile Tester

Regression of software is the risk that a change in one part of the software causes a defect in another part of the software that was previously working correctly. Regression of software is a high risk in agile projects because there is code churn due to change in business needs over several sprints. Code churn is the amount of code that is added, modified, or deleted in a software project over time. Code churn can indicate the volatility and complexity of the software, and the frequency and magnitude of the changes. In agile projects, code churn can be highbecause the business needs and the user requirements can change rapidly and frequently over several sprints, which are short iterations of development and testing. This means that the software is constantly evolving and adapting to the changing needs, and that the existing functionality and quality may be affected by the new or modified code. Therefore, regression of software is a high risk in agile projects, and it requires effective testing strategies and techniques to prevent, detect, and fix the regression defects. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 2.3.2, page 17; ISTQB® Glossary of Testing Terms2, version 4.0, pages 36 and 55

Comprehensive and Detailed Explanation From Exact Extract:

FromCTFL-AT Syllabus v4.0, Section 2.4Testing and Iterations, it states:

"In Agile projects, developers and testers work together to ensure the correct functionality is delivered during the iteration. Business representatives and testers may also validate the software during development to provide quick feedback."

This confirms thatOption Dis correct —collaborative testingby stakeholders and testers during development is a core Agile practice.

Option Ais incorrect — testing doesnot waitfor "done"; it occursconcurrentlywith development.

Option Bmisrepresents Agile — performance isn't based on metrics like defect counts.

Option Cis true in general, butdoes not directly answerthe integration of testing and development activities.

Comprehensive and Detailed Explanation From Exact Extract:

From theISTQB CTFL-AT Syllabus v4.0, Section 1.2The Fundamentals of Agile Software Development, Kanban is explained as:

"In Kanban, work is visualized using a board that shows tasks in various states of progress. The transparency of the workflow helps teams identify bottlenecks, improve flow, and collaborate effectively."

This directly supportsOption C, whereKanban boardsare used for visualizing active tasks — increasingtransparencyandprogress visibility.

Let’s clarify the other options:

Option A: The five values listed —communication, simplicity, feedback, courage, and respect— are associated withExtreme Programming (XP), not Kanban.

Option B: Scrumdoes not prescribe specific testing techniques, but italso does not dictate how development must be done, which makes this atrick answerthat’s partially true butnot complete or precise enoughto be correct.

Option D: The roles areincorrectly named. The correct Scrum roles are:

Product Owner,

Scrum Master,

Developers (Development Team is no longer a formal term post-2020 Scrum Guide)

A whole-team approach is a way of working in agile projects where all team members share the responsibility for delivering high-quality software that meets the customer’s needs. This means that testers, developers, business analysts, and other roles collaborate closely throughout the project lifecycle, and use their different skills and perspectives to contribute to the quality of the product. A benefit of this approach is that it enables the team to leverage the various skill sets within the team to the benefit of the project, such as testing skills, coding skills, domain knowledge, user experience, etc. This can lead to faster feedback, better communication, higher productivity, and more innovation. References: ISTQB® Foundation Level Agile Tester Syllabus1, Section 1.1.1, page 7; ASTQB Agile Tester Certification Resources, Section 1.1.1, page 7.

Comprehensive and Detailed Explanation From Exact Extract:

From theCTFL-AT Syllabus v4.0, Section 5.1, it states:

"The team uses the retrospective to review how they worked during the iteration, including planning accuracy and team collaboration, and to identify actionable improvements."

Thus,Option Dis correct — retrospectives help reflect on iterationplanning accuracy, team dynamics, andefficiencyto improve future iterations.

Option Ais incorrect — retrospectives aim to focus on what the teamcan improve, not just on external hindrances.

Option Bis false — Agile retrospectivesrequire follow-up, often in the form ofaction itemstracked in the next iteration.

Option Cis incorrect —Product Ownerand possibly others may contribute, depending on team context.