Achieve the CTFL-AT Exam Best Results with Help from ISQI Certified Experts
Provide CTFL-AT Practice Test Engine for Preparation
The CTFL-AT certification exam covers topics such as agile testing fundamentals, agile testing methods, testing in the agile team, and tools and techniques used in agile testing. Candidates are expected to have a good understanding of the agile development process and its application to testing. They are also required to demonstrate their ability to develop and execute test cases, identify defects, and collaborate effectively with the development team.
The CTFL-AT exam is an extension of the ISTQB Certified Tester - Foundation Level (CTFL) certification program. The CTFL-AT certification is a recognition of the tester's ability to apply Agile principles and practices to software testing. CTFL-AT exam covers various topics such as Agile testing process, testing techniques in Agile projects, and Agile testing tools and methods.
The CTFL-AT exam is an extension of the ISTQB Certified Tester - Foundation Level (CTFL) exam. Candidates who pass the CTFL-AT exam will receive an additional certification that demonstrates their knowledge of agile testing methodologies. The CTFL-AT exam covers topics such as agile development principles, testing in agile projects, and tools and techniques for agile testing. CTFL-AT exam is designed to test the candidate's knowledge and understanding of these topics and their ability to apply them in real-world scenarios.
NEW QUESTION # 16
You are working in a software development company which, for many years, used a sequential development model and was organized into separate departments for each functional group (e.g. business analysts, developers, testers) located within their own office space. Your organization has recently changed to a SCRUM agile framework. Which of the following is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model?
- A. Co-located teamwork means that all team members, including developers and testers, must sit together in the same office, so they can quickly communicate face-to-face.
- B. Credibility means that the tester must share information with the stakeholders about the test process so that they find the selected test strategy and testing activities trustworthy.
- C. Resilient testing means that the testing process is capable of dealing with rapid changes throughout the development process with test plans being updated during each iteration.
- D. Cross-functional teamwork means that all team members contribute to testing in various ways. For example, involving people with the test strategy, test planning and execution as well as test reporting.
Answer: D
Explanation:
Explanation
Cross-functional teamwork is an important organizational and behavioral best practice for a tester in the SCRUM team that should have also been practiced when using the sequential model. Cross-functional teamwork means that all team members, regardless of their functional roles, collaborate and share their skills and knowledge to achieve a common goal. In the context of testing, this means that testing is not seen as a separate activity or phase, but as an integral part of the development process. All team members contribute to testing in various ways, such as:
Involving people with the test strategy, test planning and execution as well as test reporting. This can help ensure that the testing activities are aligned with the business objectives, the user needs, and the technical requirements. It can also help improve the test coverage, the test quality, and the test efficiency.
Sharing the responsibility for testing among the team members. This can help reduce the workload and the dependency on a single tester or a testing team. It can also help increase the feedback and the communication among the team members, and foster a culture of quality and learning.
Leveraging the diverse skills and perspectives of the team members. This can help enhance the test design and the test execution by applying different techniques, tools, and approaches. It can also help identify and address the risks, the issues, and the opportunities for improvement from various angles. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 1.2.1, page 9; ISTQB Glossary of Testing Terms2, version 4.0, page 16.
NEW QUESTION # 17
Which of the following statements about the Planning poker test estimate technique are CORRECT?
1) Planning poker is a consensus based technique using a deck of cards.
2) A low test estimate usually means the story should be broken down into multiple smaller stories.
3) A high test estimate usually means the story should be broken down into multiple smaller stories.
4) One poker round is played and then consensus has to be reached.
5) The risk level of each backlog item should be decided before the poker session.
- A. 1, 3, 5
- B. 1, 2, 4
- C. 2, 3, 4
- D. 1, 2, 3
Answer: A
Explanation:
Planning poker is a consensus-based technique for agile estimation, using a deck of cards with predefined numerical values, usually based on the Fibonacci sequence or a modified version12. Therefore, statement 1 is correct. A high test estimate usually means that the user story or task is too complex, ambiguous, or risky, and should be broken down into multiple smaller stories that are easier to understand and estimate13. Therefore, statement 3 is correct. The risk level of each backlog item should be decided before the poker session, as it can affect the estimation process and the prioritization of the work14. Therefore, statement 5 is correct. Statement 2 is incorrect, as a low test estimate usually means that the user story or task is simple, clear, and well-defined, and does not need to be broken down further13. Statement 4 is incorrect, as planning poker can involve multiple rounds of estimation, reveal, and discussion, until the team reaches a consensus or agrees to defer the item12. References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section 3.3.1, Test Automation1; 2: ASTQB Agile Tester Certification Resources, Section 3.3.1, Test Automation2; 3:
Planning Poker: An Agile Estimating and Planning Technique3; 4: Planning poker: The all-in strategy for Agile estimation - Asana4
NEW QUESTION # 18
Which of the following tools would you expect to be the most useful to report defects found during exploratory testing sessions in Agile projects?
- A. Tools that capture and log activities performed on an application during its use
- B. Tools that generate data to populate an application's database
- C. Application lifecycle management (ALM) and task management tools
- D. Continuous integration and build distribution tools
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.1Exploratory Testing:
"Exploratory testing benefits from tools that record tester activity, allowing the tester to reproduce and document issues found during unscripted testing sessions." Option Dis correct -activity capture toolshelp testerslog, replay, and reportfindings effectively in exploratory sessions.
* Option Ais for test data preparation, not reporting.
* Option Bis related to integration, not exploratory testing.
* Option Chelps track tasks but lacks session capture features.
References:
CTFL-AT Syllabus v4.0, Section 3.1
Learning Objective (K2) - Use appropriate tools during exploratory testing
NEW QUESTION # 19
Which of the following statements about Agile software development approaches is true?
- A. In Kanban, transparency of content and progress of tasks is usually done with the visualization of the active tasks, for example on a public whiteboard
- B. Communication, simplicity, feedback, courage, and respect are the five fundamental values of Kanban to guide development
- C. Scrum is an Agile management framework that defines three roles: the Scrum Owner, the Product Master, and the Development Team
- D. Scrum does not provide guidance on how development has to be done in a Scrum project but prescribes the adoption of specific testing techniques
Answer: A
Explanation:
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 - increasing transparencyandprogress 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) References:
CTFL-AT Syllabus v4.0, Section 1.2
Scrum Guide 2020 - Official Roles
Learning Objective (K1) - Recognize common Agile development practices
NEW QUESTION # 20
Which of the following is NOT a statement of value from the Agile Manifesto?
- A. Responding to change over following a plan.
- B. Working software over comprehensive documentation
- C. Processes and tools over individuals and interactions.
- D. Customer collaboration over contract negotiation.
Answer: C
Explanation:
The Agile Manifesto is a declaration of four values and twelve principles that guide the Agile software development approach12. The four values of the Agile Manifesto are12:
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to change over following a plan
These values emphasize the importance of human collaboration, working product, customer feedback, and adaptability over rigid processes, extensive documentation, fixed contracts, and predefined plans. The values do not imply that the items on the right are not important, but rather that the items on the left are more important and should be prioritized.
Therefore, the statement that is NOT a value from the Agile Manifesto is B, as it contradicts the first value of the Agile Manifesto. The correct statement should be "Individuals and interactions over processes and tools". References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 1.
NEW QUESTION # 21
Which of the following statements is FALSE regarding early and frequent feedback?
- A. Early feedback decreases the amount of time needed for system testing.
- B. Early feedback helps to deliver a product that better reflects what the customer wants.
- C. Early feedback provides the Agile team with information on its productivity.
- D. Early feedback promotes early discovery and resolution of quality problems.
Answer: A
Explanation:
Explanation
Early and frequent feedback is one of the core values of Agile development. It helps the Agile team to deliver features with the highest business value first, to discover and resolve quality problems as soon as possible, to provide information on the team's productivity and progress, and to ensure that the product meets the customer's expectations and needs. However, early feedback does not necessarily decrease the amount of time needed for system testing, as system testing is still an important activity in Agile projects to verify the integration and functionality of the whole system. Early feedback may reduce the number of defects found in system testing, but it does not eliminate the need for system testing. References: ISTQB Foundation Level Agile Tester Extension Syllabus1, page 10; ISTQB Agile Tester Sample Exam2, question 11.
NEW QUESTION # 22
Which of the following statements about Agile retrospectives is true?
- A. All of the improvements identified in an Agile retrospective must be implemented as soon as possible during the next iteration
- B. Agile retrospectives should focus exclusively on improving negative aspects, without wasting time in discussions on what worked well during the iteration
- C. An Agile retrospective should be held at the end of an iteration only when the number of story points completed by the team in that iteration is lower than the team velocity
- D. Metrics such as burndown charts, velocity, and number of stories completed could be effectively used during Agile retrospectives for process improvement
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 5.1Agile Retrospectives and Process Improvement, it states:
"Retrospectives are used to reflect on what went well and what could be improved. They should include qualitative insights and quantitative measures such as velocity, burndown charts, and number of stories completed." Therefore,Option Cis correct, as using metrics to support process improvement is arecommended best practicein retrospectives.
* Option Ais incorrect - retrospectivesshould include what went well, not just negatives.
* Option Bis inaccurate - not all improvements must be implemented immediately; they areprioritized and plannedbased on capacity and impact.
* Option Dis false - retrospectives are heldat the end of every iteration, regardless of story points completed.
References:
CTFL-AT Syllabus v4.0, Section 5.1
Learning Objective (K2) - Understand the purpose and outcomes of retrospectives
NEW QUESTION # 23
Which of the following statements about a test charter are CORRECT?
1) It is used mainly in exploratory tests.
2) It is used to monitor a test process.
3) It may make reference to user stories.
4) It contains notes taken during a test session.
5) It is used to outline the company test policy.
- A. 2, 3, 4
- B. 2, 4, 5
- C. 1, 3, 4
- D. 1, 2, 5
Answer: C
Explanation:
Explanation
A test charter is a document that describes the scope, objective, and approach of an exploratory testing session.
It is used mainly in exploratory tests to guide the tester's actions and record the findings. A test charter may make reference to user stories, requirements, risks, or other sources of information that are relevant to the testing mission. A test charter also contains notes taken during a test session, such as test ideas, test results, bugs, issues, and observations. A test charter is not used to monitor a test process, as it is not a formal metric or report. It is also not used to outline the company test policy, as it is specific to a particular test session and context. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.3, page 18; ASTQB Agile Tester Certification Resources, Section 2.2.3, page 18; How to Write an Exploratory Test Charter, Creating an Exploratory Testing Charter, What is Exploratory Testing?.
NEW QUESTION # 24
Which of the following statements best describes test-driven development?
- A. A way of developing software where the test cases are developed, and often automated, before the software to run those test cases has been written
- B. An approach to software development based on iterative incremental development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams
- C. A way of testing software where test design and test execution occur at the same time, guided by a test charter during time-boxed testing sessions
- D. A high-level description of the test levels to be performed and the testing within those levels for an organization or programme (one or more projects)
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 3.2Test-Driven Development, it states:
"Test-Driven Development (TDD) is a practice where test cases are written before the code is developed.
Typically, these tests are automated, and the code is written to make the tests pass." This directly matchesOption A, making it the correct and complete answer.
Let's review the other options:
* Option Bdescribes atest strategy, not TDD.
* Option Cis a definition ofAgile software development, not TDD.
* Option Ddescribesexploratory testing, not TDD.
References:
CTFL-AT Syllabus v4.0, Section 3.2
Learning Objective (K2) - Understand the principles of test-driven development
NEW QUESTION # 25
You have been asked to execute an exploratory testing session on Park & Ride system. The test charter has been titled as "Buy a bus ticket". As a result, a number of defects were reported, the titles of which are listed below.
Which defect is out of scope for the given test charter?
- A. Failed to buy a bus ticket when the network connection to the Central System is down.
- B. Payment for parking ticket is restricted to cash only (no credit card supported).
- C. Failed to buy a bus ticket after 18:00.
- D. Price for a bus ticket was calculated incorrectly.
Answer: B
Explanation:
The test charter for the exploratory testing session is focused on buying a bus ticket, not a parking ticket.
Therefore, any defect related to the payment for parking ticket is out of scope for the given test charter. The other defects are related to the functionality, usability, or reliability of buying a bus ticket, which are in scope for the test charter. References: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing1, Section 2.3.2.1 Test Charter2; ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter3
1: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version 2014, Section 2.3.2 Exploratory Testing 2: ISTQB Certified Tester Foundation Level Agile Tester Extension Syllabus, Version
2014, Section 2.3.2.1 Test Charter 3: [ISTQB Glossary of Testing Terms, Version 3.2, 2017, Definition of Test Charter]
NEW QUESTION # 26
Which of the following is NOT a typical task performed by the tester within an Agile team?
- A. Working with business stakeholders to clarify requirements.
- B. Ensuring all project status meetings are held according to the plan.
- C. Ensuring the appropriate testing tasks are scheduled during iteration planning.
- D. Suggesting improvements in team retrospectives.
Answer: B
Explanation:
Explanation
The tester within an Agile team is not responsible for ensuring all project status meetings are held according to the plan. This is typically a task for the Scrum Master, who facilitates the meetings and ensures that the team follows the Agile principles and practices. The tester within an Agile team is responsible for ensuring the appropriate testing tasks are scheduled during iteration planning, suggesting improvements in team retrospectives, and working with business stakeholders to clarify requirements. These are all tasks that contribute to the quality of the software and the testing process, as well as the collaboration and communication within the team and with the customers. References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.1, page 171; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question
2.3.1-1, page 82
NEW QUESTION # 27
What is the main benefit of the Test Pyramid?
- A. It helps in evaluating the amount of test cases needed.
- B. It means testing is involved early in the development cycle.
- C. It shows complexity of testing activities.
- D. It acts as a metric for testing progress.
Answer: A
Explanation:
Explanation
The Test Pyramid is a model for organizing tests in a way to make the process of testing faster, efficient and cost-effective. This model focusses on getting maximum functional testing getting covered by faster and less brittle tests like Unit and API tests1. The main benefit of the Test Pyramid is that it helps in evaluating the amount of test cases needed for each level of testing. The Test Pyramid suggests that the number of test cases should decrease as we move up the pyramid, from unit tests to integration tests to end-to-end tests. This is because unit tests are more granular, isolated, and easy to write and maintain, while end-to-end tests are more complex, dependent, and brittle. The Test Pyramid also helps in balancing the test coverage and the test execution time, as unit tests provide high coverage and low execution time, while end-to-end tests provide low coverage and high execution time. By following the Test Pyramid, teams can optimize their testing efforts and resources, and ensure that they have a sufficient and effective test suite for their software. References:
ISTQB Foundation Level Agile Tester Syllabus, Section 2.2.1, page 16; ASTQB Agile Tester Certification Resources, Section 2.2.1, page 16; What is Test Pyramid : Getting started with Test Automation Pyramid, The Practical Test Pyramid - Martin Fowler, Testing Pyramid: What Is It and How To Use It | Solvd.
NEW QUESTION # 28
Which of the following allows a developer to define accurate unit tests focused on business needs?
- A. Behavior-Driven Development
- B. Test-Driven Development
- C. Acceptance Test-Driven Development
- D. Design-Driven Development
Answer: C
NEW QUESTION # 29
A Scrum project is aimed at developing an online travel website based on an IBE (Internet Booking Engine), to provide booking of flights. The website will allow customers to specify their travel requirements, and once these requirements are received, the website will offer a list of available flights which customers can book. A single Scrum team will work on this project and the project will start with a Sprint Zero.
Which of the following statements best describes how a tester on the Scrum team should contribute during the Sprint Zero?
- A. While the other team members are working on the project plan, the tester should individually create an initial test strategy for all test levels
- B. The tester should work together with the rest of the team to produce the list of the product backlog items that the team will commit to deliver at the end of the first regular sprint
- C. The tester should individually produce the list of the product backlog items that the team will commit to deliver at the end of the first regular sprint
- D. The tester should work together with the rest of the team to identify the product backlog and create an initial system architecture and high-level prototypes
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
FromCTFL-AT Syllabus v4.0, Section 2.2Release and Iteration Planning:
"During early phases like Sprint Zero, testers collaborate with the team to identify the product backlog, define high-level test strategies, and contribute to the overall planning and architecture discussions." Therefore,Option Ais correct - testerscollaborate from the beginning, not as isolated contributors.
* Option BandDsuggestindividual work, which isagainst Agile principles.
* Option Cis incorrect - the backlog items committed for Sprint 1 are determined duringSprint Planning, not in Sprint Zero.
References:
CTFL-AT Syllabus v4.0, Section 2.2
Learning Objective (K2) - Understand tester contributions during early Agile planning
NEW QUESTION # 30
Which of the following describes the frequency with which usually all changes made to the software are merged and all changed components are integrated regularly in a continuous integration process?
- A. At least once a week
- B. At least once a month
- C. At least once per iteration
- D. At least once a day
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
From theCTFL-AT Syllabus v4.0, Section 4.2Continuous Integration, it states:
"Continuous integration involves integrating code into a shared repository several times a day. Each integration is verified by an automated build and automated tests." Hence,Option D-at least once a day- correctly reflects best practice in continuous integration.
* Option A(once per iteration) andB,Care far too infrequent to meet the goals of CI.
* The objective is to detect integration issuesearly and often, which is only achievable throughdaily (or more frequent)integrations.
References:
CTFL-AT Syllabus v4.0, Section 4.2
Learning Objective (K2) - Understand frequency and purpose of continuous integration
NEW QUESTION # 31
Which ONE of the following is an example of a typical "Business-oriented work product"?
- A. The released product.
- B. A user manual.
- C. Acceptance testing entry criteria.
- D. Usability testing test results.
Answer: C
NEW QUESTION # 32
Which agile development approach incorporates the following practices:
* a project is divided into iterations called sprints
* each sprint results in a potentially releasable/shippable product?
- A. Extreme Programming
- B. Continuous Integration
- C. Kanban
- D. Scrum
Answer: D
Explanation:
Explanation
Scrum is an agile development approach that incorporates the following practices:
a project is divided into iterations called sprints, which are typically 2-4 weeks long each sprint starts with a planning meeting, where the team selects a subset of user stories from the product backlog to work on each sprint ends with a review meeting, where the team demonstrates the potentially releasable/shippable product increment to the stakeholders and collects feedback each sprint also includes a retrospective meeting, where the team reflects on the process and identifies areas for improvement123 References: 1: ISTQB Foundation Level Agile Tester Syllabus, Section
2.1, Agile Software Development1; 2: ASTQB Agile Tester Certification Resources, Section 2.1, Agile Software Development2; 3: What is Agile? | Atlassian3
NEW QUESTION # 33
User Story: As a user I want to be able to calculate tax percentage based on amount of income.
What is the best black box test design technique for verifying the accuracy of this user story?
- A. User story testing - test that the user can enter an income amount and get a result.
- B. Statement testing - test all statements in income calculation.
- C. Equivalence partitioning - test with low, medium and high income.
- D. State transition testing - test all states of income entry.
Answer: C
Explanation:
Explanation
The best black box test design technique for verifying the accuracy of this user story is equivalence partitioning. Equivalence partitioning is a technique that divides the input domain of a system into classes or groups that are expected to behave similarly. By testing one value from each class, the tester can reduce the number of test cases while still achieving good coverage. In this case, the input domainof the system is the amount of income, which can be divided into classes based on the tax percentage applied to different income ranges. For example, if the tax percentage is 10% for income below 10,000, 20% for income between 10,000 and 20,000, and 30% for income above 20,000, then the equivalence classes are: low income (<10,000), medium income (10,000-20,000), and high income (>20,000). By testing one value from each class, such as
5,000, 15,000, and 25,000, the tester can verify that the system calculates the correct tax percentage for each income range. This technique is more efficient and effective than testing all possible values of income, or testing only one value of income, or testing the states of income entry, or testing the statements in income calculation. References: ISTQB Foundation Level Agile Tester Syllabus1, Section 2.3.1, page 19; ISTQB Foundation Level Agile Tester Extension Sample Exam Questions2, Question 5, page 6.
NEW QUESTION # 34
Which one of the following is a testable acceptance criterion?
- A. The solution shall support business processes.
- B. The tools for testing are tested before use and are meeting the requirements.
- C. The response time to confirm a customer submission must not exceed 5 seconds.
- D. The system shall be easy to use.
Answer: C
Explanation:
Explanation
A testable acceptance criterion is a condition that can be verified or measured objectively by the tester, customer, or stakeholder. It should be specific, measurable, achievable, relevant, and time-bound (SMART). A testable acceptance criterion should also be written from the user's perspective, achievable within the sprint, and written before development begins1.
Among the four options, only option C meets these criteria. It is specific (the response time to confirm a customer submission), measurable (must not exceed 5 seconds), achievable (within the technical and business constraints), relevant (to the user's needs and expectations), and time-bound (must be met in every sprint). It is also written from the user's perspective, testable (by measuring the response time), and written before development (as part of the user story definition).
Option A is not testable because it is vague and subjective. What does it mean to support business processes?
How can this be verified or measured? Option B is also not testable because it is subjective and ambiguous.
What does it mean to be easy to use? How can this be verified or measured? Option D is not testable because it is not written from the user's perspective. It is an internal quality criterion for the testing team, not an acceptance criterion for the product or feature.
References: ISTQB Foundation Level Agile Tester Syllabus, Section 2.3.2, page 182; ISTQB Foundation Level Agile Tester Sample Exam Questions, Question 2.3.2-2, page 93
NEW QUESTION # 35
Which of the following is the BEST way for a test team to keep its independence when working in an Agile development environment?
- A. Locate the team that develops the test automation framework in a different location to the Agile development team.
- B. Share the Test Strategy with the Agile development team, but not the details of the Test Cases.
- C. Co-locate only some of the testers with the Agile development team, while the rest of the testers are in a different location.
- D. Assign testers to be members of the Agile team, but ensure the testers report to a different manager than the developers.
Answer: D
NEW QUESTION # 36
Which of the following sentences related to Risk-based testing is CORRECT?
- A. Risk-based testing fits well in Agile development processes, as risks are easy to identify when the work is divided into user stories.
- B. Risk-based testing does not fit well in Agile development processes, as short iterations mandate short test times.
- C. Risk-based testing fits well in Agile development processes, as risks are analyzed twice - during release and iteration planning.
- D. Risk-based testing does not fit in Agile development processes, as each iteration focuses on limited parts of the product.
Answer: A
NEW QUESTION # 37
Which of the following statements best describes Agile software development?
- A. Agile software development is a software development approach whereby lines of code (production and
/or test) of a component are written by two programmers sitting at a single computer - B. Agile software development tends to break a project into a number of iterations, where each iteration represents a separate phase of sequential development and thus in which testing is performed during the last iteration
- C. Agile software development tends to adopt an iterative incremental lifecycle, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams
- D. Agile software development tends to break a project into a series of increments, each of which delivers a portion of functionality through a series of mini-Waterfalls where all phases of the Waterfall are completed before proceeding to the next increment
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract:
From theISTQB CTFL-AT Syllabus v4.0, Section 1.1Agile Software Development and the Agile Manifesto, the Agile approach is described as:
"Agile software development uses iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing and cross-functional teams." Option C reflects this exact concept, highlighting both theiterative-incremental lifecycleand the collaborative natureof Agile teams.
* Option A refers specifically topair programming, a practice used inExtreme Programming (XP), but it's not a definition of Agile as a whole.
* Option B mistakenly describes asequential (Waterfall-like)iteration structure where testing is delayed.
* Option D describes ahybrid or phased approach, not consistent with core Agile principles.
References:
CTFL-AT Syllabus v4.0, Section 1.1
Agile Manifesto Principles
Learning Objective (K1) - Identify Agile Software Development Approaches
NEW QUESTION # 38
......
Detailed New CTFL-AT Exam Questions for Concept Clearance: https://www.topexamcollection.com/CTFL-AT-vce-collection.html
CTFL-AT Exam Preparation Material with New CTFL-AT Dumps Questions.: https://drive.google.com/open?id=1_VBVwLXACwFdVP3hAxVnUyM5KMtPhkOx
