ISTQB CTFL-AT Certified Tester Foundation Level Agile Tester Exam Dumps and Practice Test Questions Set 8 Q141-160

Visit here for our full ISTQB CTFL-AT exam dumps and practice test questions.

Question 141: 

Which Agile principle emphasizes that the highest priority is to satisfy the customer through early and continuous delivery of valuable software?

A) Responding to change
B) Deliver working software frequently
C) Customer collaboration over contract negotiation
D) Working software over comprehensive documentation

Answer: B) Deliver working software frequently

Explanation:

Option A, responding to change, emphasizes the Agile value of flexibility. Agile teams are encouraged to adapt to evolving requirements rather than rigidly adhering to a plan. While responding to change is critical for accommodating new insights or evolving customer needs, it does not explicitly ensure that the customer receives tangible value quickly. Adaptability is about process responsiveness, not about the timing of delivering usable software to the customer. Therefore, while important, this option does not directly capture the principle of continuous value delivery.

Option C, customer collaboration over contract negotiation, highlights the importance of working closely with the customer and maintaining open lines of communication. Agile values dialogue and shared understanding over formal agreements. Collaboration ensures that development aligns with business needs, and it fosters trust and transparency. However, collaboration alone does not guarantee that functional software is delivered to the customer in incremental, usable portions. A team can collaborate frequently without necessarily providing regular working increments, which is why this option is not the best fit.

Option D, working software over comprehensive documentation, underscores that functional code takes precedence over exhaustive documentation. Agile encourages minimal but sufficient documentation, focusing on producing outputs that provide actual business value. While this option reflects the emphasis on delivering something tangible rather than just planning or documenting, it still does not directly address the frequency and timing of delivery. Delivering working software is about the cadence of increments, which ensures value is realized continuously rather than at the project’s end.

Option B, deliver working software frequently, is the correct choice because it explicitly focuses on the iterative delivery of functional increments to the customer. This principle ensures that customers can see, use, and provide feedback on actual software early in the development cycle. Frequent delivery allows teams to validate assumptions, uncover issues quickly, and adapt features based on real usage. It directly ties to customer satisfaction by providing a steady stream of tangible value, reducing the risk of building features that may not meet customer needs, and supporting the Agile goal of iterative improvement. By delivering incrementally, the team enhances predictability, builds trust, and enables continuous learning and adjustment, fully aligning with the principle of satisfying the customer through early and continuous delivery.

Question 142: 

Which Agile artifact represents the list of work items the team plans to complete in the current sprint?

A) Product Backlog
B) Sprint Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Sprint Backlog

Explanation:

Option A, Product Backlog, is a prioritized list of all desired features, enhancements, and fixes for the product. It reflects the full scope of the product vision, managed by the Product Owner, and contains items that may be implemented in the future. While essential for planning, it does not provide a focused, time-boxed plan for what the team will achieve in the current sprint. It is a broader planning artifact rather than a tactical execution guide.

Option C, Burndown Chart, is a visual tool used to track remaining work over time. It helps monitor progress toward completing sprint goals, but it does not specify the tasks themselves. A burndown chart shows trends and completion rates, providing insight into whether the team is on track, but it is not a list of work items or actionable tasks.

Option D, Definition of Done, establishes the criteria that a backlog item must meet to be considered complete. It ensures quality and consistency across increments but does not contain the specific tasks planned for a sprint. It serves as a shared agreement on completion standards rather than a planning or execution artifact.

Option B, Sprint Backlog, is correct because it is a detailed list of tasks, user stories, and work items that the team has committed to completing during the current sprint. The Sprint Backlog allows the team to focus on the sprint goal, provides transparency about progress, and serves as a living document updated daily to reflect ongoing work. It bridges the gap between the strategic Product Backlog and day-to-day execution, ensuring that the team has a clear plan of action and can adapt as work progresses. This artifact embodies the Agile principles of transparency, iterative planning, and delivering value in a short cycle.

Question 143: 

Which of the following is a primary purpose of the Definition of Done?

A) Set coding standards
B) Define when work is complete and ready for release
C) Prioritize backlog items
D) Replace acceptance criteria

Answer: B) Define when work is complete and ready for release

Explanation:

Option A, setting coding standards, is a development practice that ensures code quality and consistency across a team. Coding standards guide developers on formatting, naming conventions, and best practices but do not define when an item is fully completed or ready for release. Therefore, while coding standards support quality, they are not the primary purpose of the Definition of Done.

Option C, prioritizing backlog items, is typically the Product Owner’s responsibility. Prioritization ensures that the team works on the most valuable or urgent features first. The Definition of Done does not address which items to select or in what order; rather, it establishes completion criteria that apply to every item.

Option D, replacing acceptance criteria, is incorrect because the Definition of Done complements acceptance criteria rather than replacing them. Acceptance criteria define what a product feature must achieve to meet user requirements, while the Definition of Done sets a standard for overall completion, including testing, integration, and documentation. They work together to ensure quality and readiness.

Option B, defining when work is complete and ready for release, is correct because the Definition of Done provides a shared understanding among team members of what constitutes a completed backlog item. It ensures that every increment meets quality standards, is potentially shippable, and aligns with stakeholder expectations. The Definition of Done reduces ambiguity, increases transparency, and helps maintain consistency across iterations. By adhering to a well-defined DoD, teams can deliver reliable, high-quality increments with confidence, supporting Agile principles of frequent delivery and continuous improvement.

Question 144: 

Which Agile ceremony is primarily focused on improving team processes?

A) Sprint Review
B) Sprint Retrospective
C) Sprint Planning
D) Daily Stand-up

Answer: B) Sprint Retrospective

Explanation:

Option A, Sprint Review, focuses on inspecting the product increment and gathering stakeholder feedback. Its purpose is to ensure that the delivered functionality aligns with expectations and provides value, not necessarily to improve internal team processes.

Option C, Sprint Planning, is the event where the team plans the work for the upcoming sprint. It defines the sprint goal and selects backlog items but is task-focused rather than improvement-focused.

Option D, Daily Stand-up, is a short daily meeting for the team to synchronize activities, identify blockers, and coordinate work. It promotes communication and transparency but is not dedicated to analyzing or improving processes systematically.

Option B, Sprint Retrospective, is correct because it is the ceremony where the team reflects on its processes, collaboration, and tools. The team discusses what went well, what didn’t, and identifies actionable improvements for the next sprint. Retrospectives encourage continuous learning, adaptation, and enhancement of team effectiveness, aligning closely with Agile principles of process improvement and iterative development.

Question 145: 

Which type of testing is best suited for discovering defects quickly in areas affected by recent changes?

A) Unit Testing
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer: B) Regression Testing

Explanation:

Option A, Unit Testing, focuses on verifying individual code components in isolation. While critical for catching defects early at a granular level, unit testing does not specifically address the verification of integrated functionality after changes. It is more concerned with correctness of single modules rather than ensuring existing features remain unaffected.

Option C, Exploratory Testing, is an unscripted approach where testers actively investigate the software to find defects. It can reveal unexpected issues and is useful in areas where requirements are unclear. However, it may not systematically verify that previous functionality continues to work after recent changes, making it less targeted for quick detection of regression issues.

Option D, Load Testing, evaluates system performance under stress, assessing how the application behaves under high user loads. It does not focus on functional correctness and is unrelated to discovering defects resulting from recent code changes.

Option B, Regression Testing, is correct because its primary purpose is to confirm that recent changes have not broken existing functionality. In Agile environments, where software evolves rapidly, regression testing ensures stability and confidence in incremental releases. Automated regression tests allow quick feedback, increase efficiency, and reduce the risk of defects propagating into production. By systematically verifying that previously working features still function as expected, regression testing supports Agile’s emphasis on iterative development, continuous delivery, and maintaining high quality in a fast-paced environment.

Question 146: 

Which Agile practice emphasizes testing early in the development lifecycle?

A) Shift-left Testing
B) Regression Testing
C) Load Testing
D) Smoke Testing

Answer:  A) Shift-left Testing

Explanation:

Shift-left Testing is an approach that encourages moving testing activities earlier in the development lifecycle, starting from the requirements and design phases rather than waiting until coding is complete. This practice is rooted in the understanding that the earlier defects are identified, the less costly they are to fix, and the smoother the development process becomes. By integrating testers into early discussions, such as requirement workshops and design reviews, teams can clarify ambiguities, identify risks proactively, and define acceptance criteria collaboratively. Shift-left Testing supports continuous feedback loops, aligning perfectly with Agile’s iterative approach, where increments of value are delivered frequently and validated regularly.

Regression Testing is an important testing practice but focuses on verifying that existing functionality continues to work after changes or enhancements. It is typically executed later in the development lifecycle, especially after code has been integrated or a feature has been completed. While regression testing ensures stability, it does not inherently promote early involvement of testers or risk mitigation during the planning and design phases. It serves a different purpose, emphasizing protection against unintended changes rather than early defect detection.

Load Testing evaluates how a system behaves under various levels of load, such as peak traffic or simultaneous users. This type of testing is performance-oriented and is almost always conducted once functional features are largely implemented. Load testing ensures that the application can handle anticipated operational stress but does not contribute to early defect identification in the design or code phases. It is more about validating system scalability and reliability rather than integrating testing into the development process from the start.

Smoke Testing is a preliminary testing activity conducted to ensure that the basic functionality of an application is working before deeper testing is performed. It is sometimes called a “sanity check” and usually occurs after code is compiled or a build is deployed. While smoke testing can provide rapid feedback on the overall health of a build, it is reactive rather than proactive. It does not inherently involve early collaboration, design reviews, or iterative feedback.

Shift-left Testing is the correct option because it fundamentally embodies Agile principles of early and continuous feedback, cross-functional collaboration, and iterative quality assurance. By moving testing to the earliest stages, teams reduce downstream defects, avoid costly rework, and maintain a high level of product quality throughout the development lifecycle. It complements automated testing, exploratory testing, and other quality assurance practices while embedding a mindset of “quality from the start” rather than “quality at the end.”

Question 147: 

Which artifact provides a visual representation of work remaining in a sprint over time?

A) Product Backlog
B) Burndown Chart
C) Sprint Backlog
D) Definition of Done

Answer: B) Burndown Chart

Explanation:

A Burndown Chart is a graphical tool that depicts the amount of work remaining versus time during a sprint. It provides teams and stakeholders with a clear and immediate understanding of progress, enabling early identification of bottlenecks, delays, or risks. By plotting completed work against remaining tasks daily, the team can adapt their efforts, make data-driven decisions, and maintain alignment with sprint goals. Burndown Charts are instrumental in fostering transparency, accountability, and team collaboration, making them an essential artifact in Agile project management.

The Product Backlog is a comprehensive list of all desired features, enhancements, and fixes for a product. While it is a prioritized collection of work items, it does not provide a time-based visual representation of sprint progress. The backlog guides long-term planning and scope management but is not designed to track day-to-day completion or remaining effort within a sprint.

The Sprint Backlog contains tasks selected from the Product Backlog for completion during the current sprint. It serves as a tactical plan to guide the team in achieving sprint goals and ensures that responsibilities are clearly allocated. However, it typically does not offer a visual metric of work completed versus work remaining over time. It is more of a static list of tasks rather than a dynamic progress-tracking tool.

Definition of Done is a set of criteria that determines when a backlog item or feature is considered complete. It ensures quality, consistency, and shared understanding within the team. While essential for validating work, it does not provide visualization of remaining work or track sprint progress; it focuses on completion standards rather than progress metrics.

The Burndown Chart is correct because it specifically visualizes the rate at which work is completed relative to the sprint timeline. By reviewing this chart regularly, teams can take corrective actions if they are falling behind, adjust task allocations, or reprioritize backlog items. This visibility enhances predictability, supports proactive risk management, and reinforces Agile’s iterative and transparent development practices.

Question 148: 

Which Agile technique uses tester creativity and simultaneous learning, test design, and execution?

A) Unit Testing
B) Exploratory Testing
C) Smoke Testing
D) Load Testing

Answer: B) Exploratory Testing

Explanation:

Exploratory Testing is a dynamic approach where test design, execution, and learning occur simultaneously. Testers rely on creativity, intuition, and domain knowledge to identify defects, often uncovering issues that scripted tests might miss. In Agile, where requirements are continuously evolving, exploratory testing provides rapid feedback, accommodates changing priorities, and enhances coverage. It complements automated tests by exploring edge cases, unexpected interactions, and complex scenarios that cannot always be anticipated in advance.

Unit Testing is focused on verifying individual code modules or functions. It is highly structured, repeatable, and often automated. While essential for ensuring that code works as expected at a granular level, unit testing is limited to predefined scenarios and does not involve creative problem-solving or adaptive exploration.

Smoke Testing is a shallow form of testing that checks whether the basic, critical functionalities of an application work. It acts as a sanity check for builds but is not designed to explore unknown or complex scenarios creatively. It ensures that the system is stable enough for further testing but does not offer insight into unexpected defects.

Load Testing evaluates system performance under various levels of usage. It is highly technical and scenario-based, focusing on throughput, response times, and scalability. While critical for performance validation, it is structured and does not involve simultaneous learning, design, or adaptive exploration in the way exploratory testing does.

Exploratory Testing is correct because it uniquely integrates learning, design, and execution. It thrives in Agile environments where rapid feedback, evolving requirements, and iterative development require flexible, adaptive testing approaches. By encouraging creativity and critical thinking, exploratory testing helps teams detect subtle defects early and improve overall product quality.

Question 149: 

Which Agile principle emphasizes collaboration with customers over contract negotiation?

A) Responding to change
B) Customer collaboration
C) Working software
D) Individuals and interactions

Answer: B) Customer collaboration

Explanation:

Customer collaboration is a core Agile principle that stresses active engagement with stakeholders throughout the development process. Rather than focusing solely on contractual obligations, Agile encourages continuous interaction with customers to understand their needs, gather feedback, and refine requirements iteratively. This approach ensures that the delivered product aligns with real business value and can adapt to evolving market or user expectations.

Responding to change is another Agile principle that values adaptability. While flexibility is important, this principle focuses on the team’s ability to adjust priorities and processes in response to emerging requirements rather than the nature of stakeholder engagement itself.

Working software over comprehensive documentation emphasizes delivering functional product increments frequently. While this principle aligns with Agile’s focus on tangible value, it is about the output of development rather than the collaborative process with customers.

Individuals and interactions prioritize effective team communication and collaboration within the development team. While it is essential for Agile success, it addresses internal dynamics rather than external stakeholder engagement and does not directly guide the interaction with customers.

Customer collaboration is correct because it directly captures the principle of engaging stakeholders actively to co-create solutions, ensuring that development decisions are informed by real-world requirements, feedback, and business priorities. It reinforces transparency, trust, and iterative improvement, which are cornerstones of Agile success.

Question 150: 

Which practice ensures that integration issues are detected early and frequently?

A) Continuous Integration
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer:  A) Continuous Integration

Explanation:

Continuous Integration (CI) is a development practice where code changes are merged frequently into a shared repository, followed by automated builds and tests. This process ensures that integration issues are identified as soon as possible, reducing risk and preventing defects from compounding. CI encourages teams to maintain a stable codebase, supports automated testing, and aligns with Agile’s iterative delivery by enabling frequent releases of potentially shippable increments.

Regression Testing focuses on verifying that existing functionality works correctly after changes. While it helps maintain stability, it is typically executed on completed code and does not inherently involve frequent integration of new changes. Regression testing is reactive rather than proactive regarding integration issues.

Exploratory Testing leverages creativity to discover defects in an adaptive manner. While it complements automated testing and supports early defect detection in functional areas, it is not specifically designed to ensure frequent code integration. Exploratory testing identifies unexpected behaviors but does not prevent integration conflicts by itself.

Load Testing evaluates system performance under varying levels of stress. Its primary focus is performance and scalability rather than frequent integration or detection of integration defects. It usually occurs after core functionality is implemented.

Continuous Integration is correct because it systematically addresses the challenge of early and frequent detection of integration issues. By merging changes often and running automated tests on each integration, CI reduces integration risk, accelerates feedback, and enables Agile teams to deliver high-quality software incrementally and predictably.

Question 151: 

Which Agile artifact is continuously refined to reflect changing priorities and value?

A) Sprint Backlog
B) Product Backlog
C) Burndown Chart
D) Definition of Done

Answer: B) Product Backlog

Explanation:

The Sprint Backlog is an Agile artifact that contains the work items selected for the current sprint. It represents a tactical plan for what the team intends to accomplish during the sprint. While it is highly useful for tracking immediate sprint tasks and guiding the team on a day-to-day basis, it is not continuously refined to reflect changing priorities. Its scope is limited to a single sprint and is typically fixed once the sprint begins. Therefore, while important, the Sprint Backlog does not serve the broader purpose of evolving priorities over the lifecycle of a project.

The Burndown Chart is a visual representation of work remaining versus time during a sprint or project. It is used primarily to monitor progress and predict whether the team is on track to meet sprint or release goals. Although the Burndown Chart is updated frequently and provides valuable insights into team performance, it does not contain a prioritized list of features or reflect changes in stakeholder value. It is a monitoring and reporting tool rather than an artifact that guides what work should be done next.

The Definition of Done is a set of agreed-upon criteria that specify when a backlog item or increment is considered complete. It ensures that completed work meets quality standards and is potentially shippable. While crucial for maintaining consistency and quality, the Definition of Done is static for a given project or team and does not prioritize or reflect changing business requirements. It functions as a quality benchmark rather than a dynamic planning tool.

The Product Backlog, on the other hand, is the correct answer because it captures all desired features, enhancements, bug fixes, and technical improvements in a single, prioritized list. This backlog is continuously refined through backlog grooming or refinement sessions, where items can be reprioritized, broken down, or redefined based on stakeholder feedback, evolving market conditions, or team capacity. Its dynamic nature allows Agile teams to adapt quickly, delivering the highest value features first while aligning with business priorities. By reflecting changing priorities and value continuously, the Product Backlog enables incremental delivery of software that meets stakeholder needs while maintaining flexibility in planning and execution.

Question 152: 

Which ceremony is held daily to synchronize team activities and identify impediments?

A) Sprint Planning
B) Daily Stand-up
C) Sprint Review
D) Sprint Retrospective

Answer: B) Daily Stand-up

Explanation:

Sprint Planning is a ceremony that occurs at the beginning of a sprint. Its primary purpose is to define the scope of work for the sprint, select backlog items to be worked on, and develop a plan for delivering them. While this meeting is essential for setting goals and aligning the team, it is not held daily and is not intended for ongoing synchronization of activities or rapid issue identification throughout the sprint.

The Sprint Review is conducted at the end of a sprint to inspect the completed increment and gather feedback from stakeholders. It focuses on demonstrating what has been built and discussing potential improvements for future work. While it promotes collaboration and transparency, it occurs only once per sprint and therefore does not provide the daily cadence necessary to address immediate obstacles or coordinate daily activities.

The Sprint Retrospective is another end-of-sprint meeting where the team reflects on processes, collaboration, and areas for improvement. Its focus is continuous process improvement rather than daily coordination or impediment resolution. Like the Sprint Review, it does not support daily tracking or synchronization of ongoing work.

The Daily Stand-up is correct because it is a short, focused meeting held every day, typically lasting 15 minutes. During this meeting, team members share what they accomplished yesterday, what they plan to do today, and any blockers they are facing. This practice promotes transparency, accountability, and rapid resolution of issues. By providing daily synchronization, the Daily Stand-up ensures that the team is aligned, obstacles are surfaced quickly, and work progresses smoothly, which is a cornerstone of Agile principles such as collaboration, adaptability, and continuous improvement.

Question 153: 

Which testing approach is most suitable for verifying functionality after changes in an Agile project?

A) Unit Testing
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer: B) Regression Testing

Explanation:

Unit Testing is focused on testing individual components or functions of the software in isolation. It ensures that each unit performs as intended and is often automated for efficiency. While unit testing is important for early defect detection and maintaining code quality, it does not provide coverage of the system as a whole. Unit testing cannot verify whether recent changes have unintentionally broken existing features in other parts of the system.

Exploratory Testing is an unscripted, simultaneous learning and testing approach where testers explore the system to identify defects based on intuition, experience, and creativity. While it is highly valuable for uncovering unexpected defects and gaining insights into the software, it is not structured to systematically verify that previously working functionality continues to work after changes. Exploratory testing is more suited to discovery and risk-based testing rather than repeatable verification of regressions.

Load Testing evaluates the system’s performance under anticipated user load or stress conditions. It focuses on measuring responsiveness, stability, and scalability rather than functional correctness. Load testing is useful for performance assurance but does not verify that new changes have not introduced functional defects or broken existing functionality.

Regression Testing is correct because it systematically verifies that recent code changes have not adversely affected existing functionality. In Agile projects, where changes are frequent and iterative, regression testing is crucial to maintain software stability and quality. It can be automated to ensure rapid feedback and to facilitate continuous integration practices, allowing teams to detect defects early and prevent the introduction of regressions. By consistently running regression tests after each change, teams can confidently deliver increments while preserving the reliability of existing features, aligning perfectly with Agile principles of continuous delivery and quality assurance.

Question 154: 

Which artifact defines the criteria that must be met for a backlog item to be considered complete?

A) Product Backlog
B) Sprint Backlog
C) Definition of Done
D) Burndown Chart

Answer: C) Definition of Done

Explanation:

The Product Backlog is a dynamic, prioritized list of desired features, enhancements, bug fixes, and technical improvements. While it helps plan and prioritize work, it does not define the specific criteria for when an item is considered complete. The backlog focuses on scope and value rather than completion standards.

The Sprint Backlog contains the tasks selected for the current sprint from the Product Backlog. It acts as a tactical guide for team activities during a sprint. While it may track progress and assignments, it does not specify the conditions or quality standards that must be satisfied for a task or backlog item to be regarded as done.

The Burndown Chart is a visual representation of work remaining versus time. It tracks the team’s progress but does not define completion criteria for backlog items. Its function is monitoring and reporting rather than establishing quality benchmarks or deliverable definitions.

The Definition of Done is correct because it provides explicit, agreed-upon criteria for considering a backlog item complete. These criteria often include functional requirements, non-functional requirements, testing coverage, code review, documentation, and integration readiness. By establishing a shared understanding of completion, the Definition of Done ensures that increments are potentially shippable, supports quality consistency, and aligns team expectations. It also facilitates transparency and accountability, helping Agile teams deliver reliable software in iterative cycles.

Question 155: 

Which Agile practice encourages early and continuous involvement of testers?

A) Shift-left Testing
B) Regression Testing
C) Load Testing
D) Smoke Testing

Answer:  A) Shift-left Testing

Explanation:

Regression Testing focuses on verifying that new changes have not adversely affected existing functionality. While critical in Agile for maintaining stability, it is typically performed after code changes are implemented. It does not inherently encourage early involvement of testers in the development lifecycle.

Load Testing evaluates system performance under anticipated user loads. It is generally conducted at later stages of development to ensure scalability and stability. Load testing is essential for performance assurance but does not promote early tester engagement or influence development from the outset.

Smoke Testing involves executing a basic set of tests to verify whether the critical functionalities of a build work. While smoke testing is quick and useful for early detection of major defects, it is reactive rather than proactive. It does not ensure that testers are continuously involved from the early stages of development.

Shift-left Testing is correct because it moves testing activities earlier in the development lifecycle, integrating testers into planning, design, and coding phases. This practice enables early defect detection, encourages collaboration between developers and testers, and provides rapid feedback to prevent costly errors downstream. By embedding quality assurance throughout the development process rather than waiting until the end, Shift-left Testing aligns closely with Agile principles, ensuring that teams can deliver high-quality increments efficiently and iteratively.

Question 156: 

Which technique leverages creativity to explore the system without predefined scripts?

A) Unit Testing
B) Exploratory Testing
C) Load Testing
D) Regression Testing

Answer: B) Exploratory Testing

Explanation:

Unit Testing is a software testing technique that targets individual units or components of code to ensure that each part functions as intended. Typically, unit tests are automated and executed repeatedly to verify that code changes do not introduce errors in a specific module. While unit testing is critical for verifying the correctness of individual parts of the application, it is highly structured and follows predefined test cases, leaving very little room for creative exploration. Its primary goal is to confirm that each unit works according to specifications, not to discover unexpected defects across the system as a whole.

Load Testing, on the other hand, focuses on assessing the performance of a system under specific conditions of stress, such as multiple concurrent users or heavy data processing. It helps identify performance bottlenecks, stability issues, and system capacity limits. While essential for ensuring that the application can handle expected usage patterns, load testing is not concerned with the creative exploration of functionality or uncovering logical or usability defects that may not have been anticipated. It is highly metric-driven rather than exploratory.

Regression Testing is aimed at verifying that existing functionality continues to work correctly after changes or enhancements are made to the software. This approach relies on a suite of predefined test cases that are rerun whenever modifications are introduced. Regression testing is essential for maintaining system stability and detecting defects that arise from new code changes, but it is inherently scripted and structured. It does not inherently encourage testers to explore the system creatively or adaptively beyond the defined scenarios.

Exploratory Testing is correct because it allows testers to interact with the application in an unscripted, adaptive manner. Testers leverage their knowledge, intuition, and creativity to design and execute tests on the fly, uncovering defects that may not be detected through predefined test cases. Exploratory testing is particularly effective in Agile environments where rapid changes occur and exhaustive scripting may not be feasible. It complements automated and scripted testing by providing coverage in areas that require human insight and critical thinking. By encouraging investigation and experimentation, exploratory testing can identify both obvious and subtle defects, improving overall software quality and enabling continuous learning within the team.

Question 157: 

Which principle emphasizes delivering value through working software over comprehensive documentation?

A) Working software over documentation
B) Responding to change
C) Customer collaboration
D) Individuals and interactions

Answer:  A) Working software over documentation

Explanation:

Responding to change is a core Agile principle that prioritizes adaptability over following rigid plans. While it emphasizes the importance of accommodating evolving requirements, it does not directly address the balance between documentation and software delivery. Responding to change focuses on flexibility rather than tangible outcomes that stakeholders can use.

Customer collaboration emphasizes close interaction with stakeholders to ensure that their needs are understood and met. While this principle promotes engagement and communication, it does not explicitly prioritize the delivery of functional software over maintaining detailed documentation. The collaboration can be effective whether the documentation is comprehensive or minimal; the focus remains on communication and alignment.

Individuals and interactions highlight the value of people and teamwork over processes and tools. While essential for effective Agile implementation, this principle concentrates on communication and collaboration rather than the trade-off between working software and documentation. It supports team cohesion and responsiveness but does not prescribe a tangible product outcome as the primary measure of value.

Working software over documentation is correct because Agile emphasizes delivering software that provides immediate value to stakeholders. This principle does not dismiss documentation entirely but prioritizes creating functional, usable software that can be iteratively improved based on feedback. The goal is to focus on outcomes rather than process artifacts. By ensuring that the software itself is the primary measure of progress, teams can receive early feedback, adapt to changes, and ensure that the delivered product meets real user needs. This approach aligns with Agile’s iterative and incremental development, ensuring stakeholders experience tangible value early and continuously.

Question 158: 

Which artifact visually shows work remaining versus time in a sprint?

A) Product Backlog
B) Burndown Chart
C) Sprint Backlog
D) Definition of Done

Answer: B) Burndown Chart

Explanation:

The Product Backlog is a prioritized list of features, enhancements, and bug fixes for the overall product. It serves as a roadmap for future work but does not provide real-time visualization of progress during a sprint. It is primarily used for planning and prioritization rather than tracking sprint completion over time.

The Sprint Backlog contains the tasks selected for a specific sprint and details what the team intends to complete. It is a tactical plan for the sprint but does not visually represent the work remaining against the sprint timeline. While it helps organize the team’s efforts, it is more of a task list than a progress-tracking tool.

Definition of Done is a set of criteria that determine whether a backlog item or increment is complete. It ensures consistent quality but does not provide any visual representation of progress or work remaining. Its purpose is to define completion standards, not track sprint velocity or remaining work.

Burndown Chart is correct because it visually tracks the amount of work left versus the time available in a sprint. It provides an at-a-glance view of team progress, helping identify potential risks, bottlenecks, or deviations from the plan. By continuously updating the chart, the team can make informed decisions about adjusting work or processes to ensure sprint goals are met. Burndown charts support Agile’s iterative approach by promoting transparency, enabling early intervention, and encouraging data-driven discussions in daily stand-ups and sprint reviews.

Question 159: 

Which Agile ceremony allows the team to reflect on process improvements and identify actionable steps?

A) Sprint Planning
B) Sprint Review
C) Daily Stand-up
D) Sprint Retrospective

Answer: D) Sprint Retrospective

Explanation:

Sprint Planning is focused on defining the scope and tasks for the upcoming sprint. While it involves collaboration and planning, it does not provide a dedicated forum for reflecting on past performance or identifying process improvements. It is forward-looking rather than reflective.

Sprint Review is intended to inspect the deliverables produced during the sprint and gather stakeholder feedback. While it includes some discussion of improvements, its primary focus is on product functionality and outcomes rather than team processes or workflow optimizations.

Daily Stand-up is a short, time-boxed meeting to synchronize activities, address impediments, and coordinate work for the day. It is tactical and operational in nature, focusing on immediate tasks and blockers, without allocating time for in-depth reflection or process improvement.

Sprint Retrospective is correct because it provides a structured opportunity for the team to analyze their processes, identify successes and failures, and define actionable steps for improvement in future sprints. This ceremony fosters a culture of continuous learning, collaboration, and incremental enhancement, contributing to improved productivity, higher-quality deliverables, and better team dynamics. By reflecting regularly, teams can experiment with new practices, refine workflows, and strengthen overall agility, ensuring that lessons learned are embedded in subsequent sprints.

Question 160: 

Which practice integrates code frequently with automated testing to identify defects early?

A) Continuous Integration
B) Regression Testing
C) Exploratory Testing
D) Load Testing

Answer:  A) Continuous Integration

Explanation:

Regression Testing verifies that existing functionality continues to work as expected after changes. While it identifies defects introduced by modifications, it does not inherently involve frequent integration of new code. Regression testing is generally performed after code merges rather than driving the integration process itself.

Exploratory Testing relies on human creativity and adaptive exploration to uncover defects. Although valuable for discovering unexpected issues, it is not a structured practice for integrating code or providing rapid automated feedback during development. It complements automated processes but does not replace them in Continuous Integration.

Load Testing measures system performance under heavy usage conditions. It helps identify bottlenecks and resource constraints but is focused on non-functional aspects rather than continuous integration or early defect detection.

Continuous Integration is correct because it involves frequently merging developers’ code changes into a shared repository and running automated builds and tests with each integration. This practice ensures that integration issues are detected early, reducing the cost and effort of fixing defects later in the development lifecycle. By combining frequent code integration with automated testing, teams receive immediate feedback on both functionality and compatibility, supporting Agile’s iterative delivery model, enhancing product quality, and minimizing risks associated with late defect discovery. Continuous Integration aligns closely with Agile principles, promoting rapid delivery, transparency, and continuous improvement.