ISTQB CTFL-AT Certified Tester Foundation Level Agile Tester Exam Dumps and Practice Test Questions Set 9 Q161-180

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

Question 161: 

Which Agile principle emphasizes delivering working software frequently, from a couple of weeks to a couple of months, with a preference for shorter timescales?

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

Answer: C) Deliver working software frequently

Explanation:

Responding to change is a core Agile principle that emphasizes the ability to adapt plans, requirements, and priorities as the project evolves. While it highlights the importance of flexibility and encourages teams to embrace modifications even late in development, it does not define a specific delivery cadence or prescribe the frequency of software releases. This principle is focused on ensuring that teams remain adaptable and responsive to the evolving needs of the business and stakeholders, rather than directly emphasizing the iterative delivery of working software increments.

Customer collaboration over contract negotiation emphasizes active engagement with customers throughout the development process. It prioritizes working closely with stakeholders to gather requirements, validate decisions, and ensure alignment with business needs. While collaboration ensures that teams are building the right product and responding to feedback, this principle does not inherently dictate the interval at which functional software should be delivered. It supports iterative delivery indirectly by promoting frequent communication, but it is not specifically about release cadence.

Working software over comprehensive documentation stresses the importance of delivering usable software that meets functional needs rather than focusing excessively on creating detailed documentation. This principle encourages teams to prioritize tangible outputs that stakeholders can interact with. Although it aligns with the idea of delivering value, it does not define how often these outputs should be produced. It is more about the relative priority between producing functional software and investing time in extensive documentation.

Delivering working software frequently is the principle that directly addresses the interval and cadence of releases. By emphasizing the delivery of functional increments every few weeks to a couple of months, it ensures that teams provide value early and continuously. Frequent delivery allows for early validation of features, enables stakeholders to give timely feedback, and reduces risk by identifying defects and misunderstandings sooner. Shorter delivery cycles facilitate iterative improvements, foster trust and transparency with customers, and allow teams to adapt the product incrementally based on real-world usage. In Agile projects, this principle underpins the iterative, incremental approach by creating predictable opportunities for feedback and learning, which in turn improves product quality and alignment with customer expectations.

Question 162: 

Which Agile artifact contains all desired features and is continuously prioritized and refined?

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

Answer: B) Product Backlog

Explanation:

The Sprint Backlog represents the set of items selected from the Product Backlog for a specific sprint. It contains tasks the team intends to complete within the sprint and serves as a tactical plan for immediate development work. While it reflects the team’s short-term focus and provides a detailed view of sprint tasks, it is limited in scope and time-bound to the sprint. It does not capture the comprehensive list of all desired product features or reflect ongoing prioritization across the project lifecycle, making it insufficient for representing the full set of product requirements.

The Burndown Chart is a visual tool used to track progress within a sprint or across releases. It displays the amount of work remaining versus time and helps teams monitor whether they are on track to meet sprint or project goals. Although it provides valuable insights into progress and velocity, it is not a repository for requirements or features. It serves primarily as a monitoring and reporting mechanism rather than a living artifact of prioritized work items.

The Definition of Done is a shared agreement that specifies the criteria that must be met for a product increment or backlog item to be considered complete. It ensures consistency in quality and provides clarity about what constitutes “done.” While this artifact supports quality assurance and alignment on completion standards, it does not capture or prioritize features, enhancements, or requirements. It functions as a guide for completing work rather than a list of what work should be undertaken.

The Product Backlog is the artifact that contains all desired features, user stories, enhancements, and defects to be addressed throughout the product lifecycle. It is continuously refined and reprioritized to reflect changing business priorities, risks, and stakeholder input. By maintaining a living backlog, teams can focus on delivering the highest value items first and adapt to evolving market conditions or user needs. Regular grooming sessions ensure clarity, breakdown of large items into smaller actionable tasks, and alignment with the overall product vision. This makes the Product Backlog the central tool for managing scope, prioritization, and iterative delivery in Agile, providing both a strategic overview and a detailed foundation for planning sprints.

Question 163: 

Which ceremony allows the team to inspect completed work and gather feedback from stakeholders?

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

Answer: B) Sprint Review

Explanation:

Sprint Planning is the ceremony in which the team defines what work will be undertaken in the upcoming sprint. During this meeting, the team selects backlog items, estimates tasks, and defines sprint goals. It is forward-looking and focused on planning rather than inspecting work that has already been completed. While Sprint Planning is essential for organizing work and setting expectations, it does not provide a structured forum for gathering feedback from stakeholders about delivered increments.

The Daily Stand-up is a brief daily meeting intended to coordinate team members’ activities, identify impediments, and ensure alignment on sprint progress. Its primary purpose is internal team communication, with each member reporting on what they accomplished, plan to work on, and any blockers they face. It is not designed to involve stakeholders or provide a platform for reviewing completed functionality, so it does not fulfill the role of feedback collection and inspection of delivered work.

The Sprint Retrospective is a ceremony focused on process improvement. In this meeting, the team reflects on what went well, what could be improved, and defines actionable steps for enhancing team performance and processes. While it is critical for continuous improvement, it does not involve reviewing completed product features with stakeholders. Its scope is internal and process-oriented rather than product-oriented.

The Sprint Review is the correct ceremony because it provides a structured opportunity to inspect completed work and gather feedback from stakeholders. During this meeting, the team demonstrates the increment delivered in the sprint, allowing stakeholders to evaluate functionality, usability, and alignment with expectations. Feedback collected during the review informs adjustments to the Product Backlog, supports iterative development, and ensures the product evolves according to user needs. This practice promotes transparency, early validation of features, and a shared understanding between the team and stakeholders. By integrating feedback regularly, Agile teams enhance product quality, reduce risk, and maintain alignment with business priorities, making the Sprint Review a cornerstone of the inspect-and-adapt approach.

Question 164: 

Which Agile testing approach focuses on verifying previously working functionality after changes have been made?

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

Answer: B) Regression Testing

Explanation:

Unit Testing is a method of testing individual code modules or components in isolation to ensure they function as intended. While unit tests are valuable for catching defects at a granular level, they primarily focus on validating specific pieces of code and do not guarantee that changes elsewhere in the system have not introduced new defects. Unit testing is a preventive measure for individual modules rather than a comprehensive check on previously working system functionality.

Regression Testing is specifically designed to verify that existing functionality continues to work correctly after changes, such as enhancements, bug fixes, or configuration updates. It ensures that modifications do not introduce unintended side effects, making it essential in Agile environments characterized by frequent iterations. Regression testing can be automated for efficiency, providing rapid feedback to developers and reducing the risk of defects reaching production. It plays a crucial role in maintaining system stability, supporting continuous integration, and facilitating confidence in frequent delivery cycles.

Exploratory Testing is an unscripted approach where testers use creativity, experience, and intuition to uncover defects. While it is highly effective for identifying unexpected issues and edge cases, it does not focus on systematically validating previously working functionality. Exploratory testing is complementary to regression testing, as it can uncover defects not anticipated in automated or scripted tests, but it is not a primary approach for confirming that existing features remain intact after changes.

Load Testing evaluates the system’s performance under heavy or peak usage conditions. Its goal is to assess scalability, responsiveness, and resource utilization rather than verifying functional correctness of previously working features. Load testing ensures that the system can handle expected user loads but does not provide assurance that modifications have preserved the integrity of existing functionality. Regression testing is therefore the correct choice because it systematically targets verification of existing features, ensuring that incremental changes do not compromise previously working functionality, which is critical in Agile iterative development cycles.

Question 165: 

Which technique is best suited for uncovering unexpected defects in Agile projects?

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

Answer: C) Exploratory Testing

Explanation:

Unit Testing focuses on individual code components or modules. It ensures that specific functionality works as expected at a micro level, typically through automated or pre-scripted tests. While unit tests can detect defects within defined boundaries, they are limited to what is explicitly programmed and do not explore unanticipated interactions across the system. They are excellent for maintaining code quality but are insufficient for uncovering defects arising from unforeseen scenarios.

Regression Testing is primarily concerned with verifying that previously working functionality remains intact after changes. It ensures stability in iterative development but is generally scripted and does not aim to detect unexpected or unknown defects. While it prevents the introduction of new bugs in existing features, it is not designed to explore areas where defects might be lurking outside of known requirements or expected behavior.

Load Testing evaluates system performance under simulated high-traffic or stress conditions. It helps identify bottlenecks, resource limits, or performance degradation. While critical for performance assurance, it is not intended for functional defect discovery, particularly for defects that occur in unexpected or complex usage scenarios. Load testing is complementary to defect detection but is not the primary method for discovering unknown issues.

Exploratory Testing is correct because it leverages tester intuition, domain knowledge, and creativity to explore the system without predefined scripts. It is particularly well-suited for Agile environments, where requirements evolve rapidly and developers may not anticipate all potential defect scenarios. Testers interact with the application dynamically, making observations, designing tests on the fly, and adjusting strategies as new insights emerge. This approach is highly effective at uncovering unexpected defects, edge cases, and usability issues. Exploratory testing complements automated tests and structured verification by addressing unknown risks, enhancing product quality, and providing rapid, actionable feedback to support iterative development cycles.

Question 166: 

Which ceremony provides the team an opportunity to reflect on processes and identify actionable improvements?

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

Answer: D) Sprint Retrospective

Explanation:

Sprint Planning is a key Agile ceremony that occurs at the beginning of each sprint. Its main purpose is to define the work that the team will commit to completing during the upcoming sprint. During this meeting, the team selects backlog items, breaks them into tasks, estimates effort, and aligns on the sprint goal. While Sprint Planning is essential for setting direction and clarity on priorities, it does not focus on reflecting on past performance or identifying ways to improve team processes. Its emphasis is more on planning and forecasting than on learning or process enhancement.

Sprint Review is held at the end of a sprint and primarily focuses on inspecting the increment of work that was completed. During this ceremony, the team demonstrates the features or product increments to stakeholders, gathers feedback, and ensures that the deliverables align with customer expectations. While the Sprint Review provides insight into product functionality and helps stakeholders validate the work, it is not specifically intended for analyzing team processes, collaboration challenges, or workflow improvements. Its lens is product-focused rather than process-focused.

The Daily Stand-up is a short, daily meeting where the team synchronizes activities, reports progress, and identifies any impediments. This ceremony supports coordination and communication within the team and helps ensure that work progresses smoothly. Although Daily Stand-ups help uncover short-term blockers and facilitate immediate problem-solving, they are not designed for in-depth reflection or systemic process improvement. The conversations are typically tactical, focusing on what was done yesterday, what will be done today, and any obstacles, rather than evaluating overarching team practices or long-term effectiveness.

Sprint Retrospective is the ceremony that directly addresses process reflection and continuous improvement. During this meeting, the team reviews the sprint to identify what went well, what did not go well, and what can be improved in future sprints. It encourages open dialogue, fosters trust, and allows team members to suggest actionable improvements to workflow, collaboration, and technical practices. The Retrospective is central to Agile’s philosophy of continuous improvement because it provides a dedicated forum for the team to adapt its processes, reduce inefficiencies, and enhance both productivity and quality. By reflecting regularly, the team builds stronger collaboration, reduces recurring issues, and incrementally optimizes practices to deliver higher-value increments in subsequent sprints.

Question 167: 

Which Agile principle emphasizes prioritizing customer collaboration over contract negotiation?

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

Answer: B) Customer collaboration

Explanation:

Responding to change is a core Agile principle that emphasizes the importance of adapting plans and solutions as requirements evolve. While responding to change ensures flexibility and helps the team stay aligned with shifting priorities, it does not explicitly focus on the interaction between the team and the customer. Its emphasis is on adaptability and adjusting work based on new insights rather than establishing strong engagement and collaboration practices with stakeholders.

Working software, as emphasized in Agile, prioritizes delivering functional software over extensive documentation. This principle ensures that tangible, valuable output is produced for users and stakeholders. While it is critical for validating product functionality, it does not inherently address the importance of engaging the customer throughout the process. Working software highlights results and deliverables rather than relationship and communication dynamics.

Individuals and interactions stress the value of human communication and collaboration within the team. This principle ensures effective team coordination, knowledge sharing, and problem-solving. However, while it enhances team effectiveness, it primarily focuses on internal interactions rather than interactions with customers or stakeholders. It is about team dynamics, not about actively collaborating with external business representatives.

Customer collaboration is the correct choice because it underscores the Agile value of maintaining continuous engagement with stakeholders throughout the development process. Agile principles prioritize delivering value by understanding and addressing customer needs, ensuring that requirements are validated early and iteratively. By collaborating closely, teams can receive timely feedback, adjust priorities based on real user insights, and build trust with stakeholders. This ongoing dialogue minimizes misalignment, reduces risks of delivering irrelevant functionality, and maximizes value delivery. It emphasizes proactive partnership over rigid contract terms, allowing the team to respond to evolving business needs effectively.

Question 168: 

Which Agile practice integrates code frequently with automated builds and tests to detect defects early?

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

Answer:  A) Continuous Integration

Explanation:

Regression Testing is a practice used to verify that recent code changes do not adversely affect existing functionality. While regression testing is essential for maintaining software stability, it does not inherently involve frequent code integration or automated builds. It is primarily concerned with validating correctness after changes rather than detecting integration issues early in the development cycle.

Exploratory Testing relies on tester creativity and intuition to explore the system and identify defects. It is highly flexible and useful for uncovering unexpected issues, but it does not focus on continuous integration or automated testing. Its purpose is primarily investigative, providing coverage where predefined scripts may not exist, but it lacks the systematic, automated approach that ensures early detection of integration problems.

Load Testing evaluates how a system performs under high traffic or stress conditions. While it is important for understanding system scalability and responsiveness, it does not focus on continuous integration of code or automated testing. Load testing is typically conducted at specific points in the development lifecycle and is performance-oriented rather than focused on defect detection during integration.

Continuous Integration is the correct answer because it embodies the Agile practice of frequently merging code changes into a shared repository and automatically triggering builds and tests. This approach ensures that integration problems are detected early, reducing the cost and complexity of defect resolution. By automating builds and tests, teams gain immediate feedback on code quality, maintain system stability, and support iterative delivery of potentially shippable increments. Continuous Integration also encourages collaboration among team members, maintains high code quality, and aligns with Agile principles by facilitating fast, reliable delivery in short cycles.

Question 169: 

Which Agile artifact defines the work items to be delivered during a sprint?

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

Answer: B) Sprint Backlog

Explanation:

Product Backlog is the master list of all desired features, enhancements, and bug fixes for the entire product. It provides a prioritized roadmap but is not specific to any individual sprint. The Product Backlog is focused on long-term planning and scope management rather than detailing the tasks selected for immediate work within a sprint.

Burndown Chart is a visual tool used to track progress toward completing the work in a sprint or release. While it helps the team monitor remaining effort and predict completion rates, it does not define the work itself. It is purely an informational and tracking artifact, not a planning or commitment document.

Definition of Done is a set of criteria that determine whether a backlog item or increment is considered complete. It ensures quality standards and provides clarity on acceptance but does not list specific tasks or user stories for a sprint. It is a quality guideline rather than a task-planning artifact.

The Sprint Backlog is the correct answer because it specifies all work items selected from the Product Backlog for a given sprint. It provides a detailed, actionable plan that the team can follow, breaking stories into tasks, estimating effort, and tracking progress. The Sprint Backlog embodies Agile’s adaptive planning philosophy, as it can evolve during the sprint to reflect changing priorities or new insights. It ensures focus on the sprint goal, facilitates transparency, and helps teams organize and manage their work efficiently.

Question 170: 

Which technique uses system models or decision tables to generate test cases automatically?

A) Risk-Based Testing
B) Model-Based Testing
C) Exploratory Testing
D) Ad-hoc Testing

Answer: B) Model-Based Testing

Explanation:

Risk-Based Testing is a strategy that prioritizes testing activities based on the risk of failure or impact of defects. While it effectively allocates resources to high-risk areas, it does not inherently automate test case generation. Its focus is on planning and prioritization rather than systematic or model-driven test design.

Exploratory Testing relies on the tester’s knowledge, experience, and intuition to design and execute tests on the fly. It is highly adaptive and useful for discovering unexpected issues but does not use models or automated generation. Its strength lies in creativity and flexibility rather than structured test automation.

Ad-hoc Testing is an informal and unstructured approach where testers execute tests without formal planning or documentation. It relies heavily on the tester’s skill and understanding of the system. While it can uncover defects that formal scripts may miss, it does not involve models, systematic coverage, or automation.

Model-Based Testing is the correct choice because it systematically uses models of the system, workflows, or decision rules to automatically generate test cases. This approach ensures comprehensive coverage, reduces manual effort, and aligns with Agile’s iterative testing cycles. It is particularly effective for complex systems or highly regulated environments, where consistency and completeness in test design are critical. By leveraging automated test generation, teams can maintain quality while supporting rapid development and frequent releases.

Question 171: 

Which Agile principle emphasizes individuals and interactions over processes and tools?

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

Answer: D) Individuals and interactions

Explanation:

Working software is one of the core values of Agile, and it emphasizes delivering functional, usable software to the customer. This principle prioritizes outcomes and tangible results over exhaustive documentation or rigid procedures. While delivering working software is critical, it primarily focuses on the product itself rather than the collaborative processes that enable the team to produce it effectively. It ensures value is delivered early and continuously, but it does not explicitly address the human factors or team communication that drive the Agile process.

Responding to change is another foundational Agile principle that underlines the importance of flexibility and adaptability. Agile teams are encouraged to embrace evolving requirements, even late in the development lifecycle, to maximize customer satisfaction. This principle supports iterative development and prioritization but is more about external adaptation to changing business needs than internal team collaboration. It enables agility in planning and execution but does not directly focus on how individuals work together or share knowledge.

Customer collaboration emphasizes engaging stakeholders frequently to ensure that the delivered product aligns with business goals. It values active participation, frequent feedback, and cooperative decision-making with the customer. While this principle highlights interaction, its focus is primarily outward—toward stakeholders—rather than internal team dynamics. Effective customer collaboration supports building the right product but does not inherently address the mechanisms of team communication, problem-solving, or knowledge sharing among team members.

Individuals and interactions is the principle that directly addresses the human dimension of Agile teams. It prioritizes communication, collaboration, and knowledge sharing within the team, recognizing that even the best processes or tools cannot replace the problem-solving and creativity of motivated individuals working together. By emphasizing individuals over processes, Agile ensures that teams can quickly address issues, adapt to changes, and make informed decisions. It fosters a culture of collaboration, mutual support, and shared ownership, which is crucial for iterative development, continuous delivery, and high-quality outcomes. Therefore, individuals and interactions is the correct choice, as it reflects the Agile belief that human collaboration drives project success.

Question 172: 

Which testing approach in Agile is exploratory and adapts to findings during execution?

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

Answer: C) Exploratory Testing

Explanation:

Unit Testing is a testing approach that focuses on verifying individual code modules or components for correctness. These tests are often automated and executed frequently to ensure that the building blocks of the application function as intended. Unit testing is structured, predefined, and usually does not involve adapting tests based on real-time findings during execution. Its main purpose is defect prevention at the earliest stages of development rather than exploring unknown behaviors.

Regression Testing is primarily concerned with verifying that changes, updates, or new features do not break existing functionality. It ensures stability and continuity, typically using a fixed set of test cases. While regression testing is essential for quality assurance, it is not exploratory; it does not adapt or evolve based on what testers discover during execution. Instead, it follows a systematic, preplanned approach to validate previously established behaviors.

Load Testing evaluates how the system performs under specific workloads. It is concerned with performance, scalability, and reliability rather than correctness of functionality or adaptive exploration. Load testing is preplanned, usually involves simulation of high traffic or stress scenarios, and follows metrics-based outcomes. It is critical for understanding system limits but does not inherently support creative, adaptive testing techniques or the discovery of unexpected defects.

Exploratory Testing is correct because it is an adaptive and simultaneous approach to test design and execution. Testers leverage creativity, intuition, and experience to explore the system, uncover hidden defects, and investigate areas that may not be fully documented. It is particularly valuable in Agile environments where requirements can evolve rapidly and documentation may be limited. Exploratory testing enhances coverage, provides immediate feedback, and encourages collaborative problem-solving, aligning closely with Agile principles of flexibility, learning, and iterative improvement.

Question 173: 

Which artifact captures all desired product features prioritized by value and risk?

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

Answer: B) Product Backlog

Explanation:

The Sprint Backlog is a subset of the Product Backlog that contains tasks selected for a specific sprint. It is tactical in nature and guides the team during the sprint to deliver the sprint goal. While it provides a plan for short-term execution, it does not reflect all desired features or the full prioritization of value and risk across the product. It is focused on immediate work rather than strategic planning.

Burndown Chart is a visual tool that tracks progress against a sprint or project. It shows the remaining work over time and helps teams monitor completion rates. While it supports transparency and planning, it is a reporting mechanism rather than a repository of requirements or features. It cannot capture or prioritize product functionality or business value, making it unsuitable as the artifact in question.

Definition of Done defines the criteria that determine when a backlog item is considered complete. It ensures quality standards and shared understanding but does not list or prioritize features. Its focus is on validating completion rather than organizing work based on value or risk.

The Product Backlog is correct because it is a comprehensive list of all desired features, enhancements, and bug fixes for a product. It is continuously refined and prioritized based on business value, risk, dependencies, and stakeholder needs. The Product Backlog enables the team to focus on delivering high-value items first and provides flexibility to adapt to changing priorities. By capturing all work and organizing it according to impact and urgency, it supports Agile’s iterative and incremental approach, ensuring that each increment delivers meaningful value to the customer.

Question 174: 

Which ceremony focuses on daily synchronization and reporting 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 to define the sprint goal and identify backlog items to be worked on. While it is critical for setting direction and expectations, it is not a daily synchronization event and does not focus on reporting day-to-day impediments. Its scope is planning rather than ongoing coordination.

Sprint Review occurs at the end of a sprint to inspect the increment and gather feedback from stakeholders. It evaluates what has been completed and identifies potential improvements, but it is periodic and not intended for daily updates. The review emphasizes product assessment, not the continuous, immediate communication needed for team synchronization.

Sprint Retrospective is focused on reflecting on processes, team interactions, and workflow improvements. Its purpose is to identify lessons learned and implement changes for future sprints. While it contributes to team efficiency, it is not a mechanism for daily reporting of progress or immediate impediments.

Daily Stand-up is correct because it is a short, time-boxed meeting where team members synchronize on progress, plan tasks for the day, and communicate blockers. It fosters transparency, collaboration, and accountability, ensuring that issues are addressed promptly and that team efforts remain coordinated. By enabling quick problem-solving and iterative adjustments, the Daily Stand-up embodies the Agile principles of adaptive planning, teamwork, and rapid feedback.

Question 175: 

Which principle emphasizes early involvement of testers in the development lifecycle?

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

Answer:  A) Shift-left Testing

Explanation: 

Regression Testing is intended to validate that new changes do not negatively impact existing functionality. It is usually conducted after features are developed and does not inherently involve early participation of testers in planning or design phases. While important for quality assurance, it addresses late-stage validation rather than early defect prevention.

Exploratory Testing is an adaptive approach to discovering defects through simultaneous learning, test design, and execution. It is valuable for uncovering unexpected issues, but it is not inherently about integrating testers early in the lifecycle. It can be applied at any stage, often after functional areas are available for exploration.

Load Testing evaluates system performance under stress or high demand. It is typically conducted after development to ensure reliability and scalability, not as an early engagement strategy for testers. Its focus is technical performance rather than collaboration or early defect identification.

Shift-left Testing is correct because it advocates involving testers from the earliest stages of development, including requirements gathering, design discussions, and early coding. This proactive involvement improves requirement clarity, helps identify potential defects before implementation, and ensures continuous feedback. Early engagement aligns with Agile’s iterative cycles and incremental delivery by preventing costly rework, enhancing quality, and fostering collaboration between testers, developers, and stakeholders. By shifting testing left in the lifecycle, teams reduce risk and ensure that deliverables meet user expectations from the outset.

Question 176: 

Which ceremony allows the team to inspect the increment and adapt the backlog based on feedback?

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

Answer: B) Sprint Review

Explanation:

Sprint Planning is a ceremony that occurs at the beginning of a sprint. During this session, the team collaborates to select items from the Product Backlog to be completed in the upcoming sprint. The primary focus of Sprint Planning is on defining the scope of work for the sprint, estimating tasks, and breaking down backlog items into actionable work items. While important for guiding development activities, Sprint Planning is forward-looking and does not involve evaluating the completed increment or incorporating stakeholder feedback on what has already been delivered. It is essentially about planning rather than inspection or adaptation.

The Daily Stand-up, often held as a brief meeting each day, serves a different purpose. Its main objective is for team members to coordinate work, share progress, and identify any blockers or impediments that might hinder the completion of sprint tasks. While this ceremony supports transparency and immediate issue resolution, it does not formally involve stakeholders, review completed deliverables, or influence backlog priorities. The Daily Stand-up is tactical and operational, focused on daily synchronization rather than strategic evaluation of the increment.

Sprint Retrospective is a ceremony aimed at process improvement. It occurs at the end of a sprint and is focused on reflecting on team performance, identifying challenges in collaboration, communication, or workflow, and planning improvements for future sprints. The emphasis here is on “how” the team works rather than the product itself. While this meeting is crucial for continuous improvement, it is not intended for inspecting the work completed in the sprint or for receiving feedback that would change the backlog content.

Sprint Review is correct because it specifically addresses both product evaluation and stakeholder engagement. During this ceremony, the team demonstrates the completed increment to stakeholders, such as product owners, customers, and other interested parties. Feedback is gathered regarding functionality, usability, and alignment with business needs. Based on this feedback, the Product Backlog is updated and reprioritized to ensure that future work maximizes value. The Sprint Review ensures that the product evolves iteratively and adaptively, aligning closely with Agile principles. It combines product inspection with adaptive planning, making it the most suitable ceremony for responding to change in a structured and collaborative way.

Question 177:
Which artifact provides a visual representation of remaining work 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 desired features, enhancements, and bug fixes for the product. It serves as a dynamic repository of work items, but it does not provide a visual measure of the progress within a sprint. It is focused on scope and priority rather than quantitative tracking of completed or remaining tasks. Therefore, while essential for planning, it cannot serve the purpose of visualizing work remaining in a sprint.

The Sprint Backlog, on the other hand, contains the subset of Product Backlog items that the team has committed to delivering during the sprint. It provides detailed task-level breakdowns and ownership assignments. While this artifact is operational and allows the team to manage daily work, it is not inherently visual, nor does it track progress over time in a way that makes it easy to see remaining effort at a glance.

The Definition of Done establishes the criteria required for a backlog item or increment to be considered complete. It ensures consistency and quality but does not provide any visualization of remaining work. Its role is primarily evaluative, enabling the team to verify that items meet agreed-upon standards rather than to monitor progress against a timeline.

The Burndown Chart is correct because it is specifically designed to visually track the remaining effort against time in a sprint. It represents the total work planned versus work completed in a clear graphical format, enabling the team and stakeholders to monitor progress, detect potential risks, and make adjustments to ensure sprint goals are met. This transparency supports inspection and adaptation, key principles of Agile, allowing the team to respond quickly if progress deviates from expectations and to continuously communicate progress to all involved parties.

Question 178: 

Which Agile principle encourages adapting to changing requirements even late in development?

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

Answer: B) Responding to change

Explanation:

Working software over documentation is a principle that emphasizes the delivery of functional software rather than extensive documentation. While it guides the team to focus on tangible outcomes, it does not explicitly address how to respond to changes in requirements once development is underway. Its primary intent is to prioritize results over process artifacts.

Customer collaboration over contract negotiation emphasizes engaging customers continuously to understand their needs and ensure alignment with the delivered product. This principle is about fostering active partnership rather than explicitly managing changes to requirements. It creates opportunities to receive feedback, but the focus is more on interaction than on the mechanics of accommodating late changes.

Individuals and interactions over processes and tools underscores the importance of effective communication and teamwork. It highlights that collaboration among team members is more valuable than strict adherence to processes or reliance on tools. This principle is foundational for Agile teamwork, but it does not explicitly emphasize adapting requirements or product features in response to evolving conditions.

Responding to change is correct because it explicitly encourages teams to remain flexible and adaptive, even late in development. Agile recognizes that business needs and customer priorities can evolve, and this principle allows teams to adjust scope, features, or implementation strategies to maximize value. By embracing change, teams reduce the risk of delivering outdated or irrelevant solutions and ensure that the product continues to align with stakeholder expectations and market realities. This principle reinforces the iterative and incremental approach, allowing continuous adaptation based on feedback and emerging requirements.

Question 179: 

Which testing technique is most effective for identifying defects not anticipated by scripted tests?

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

Answer: C) Exploratory Testing

Explanation:

Unit Testing focuses on verifying individual components or modules of the code in isolation. It ensures that each unit behaves as expected according to predefined conditions. While highly effective at catching defects within specific modules, Unit Testing relies on predefined tests and does not inherently explore unanticipated behavior or interactions beyond the expected scenarios.

Regression Testing is performed to ensure that existing functionality continues to work as expected after changes, enhancements, or bug fixes. While essential for maintaining stability, regression tests follow scripted procedures and predetermined expectations. They are not primarily designed to uncover new, unexpected defects outside the scope of the existing test suite.

Load Testing evaluates the system’s performance under expected or peak load conditions. It measures how the system behaves under stress, identifying bottlenecks or performance issues. Although valuable for performance assessment, Load Testing does not focus on functional defects, user interface issues, or unanticipated behavior. Its scope is limited to performance rather than functional exploration.

Exploratory Testing is correct because it relies on tester insight, intuition, and creativity rather than pre-scripted steps. Testers explore the system in an unscripted manner, investigating areas where defects are likely but not explicitly predicted. This approach is highly effective in Agile contexts because it supports rapid feedback, adaptive learning, and immediate defect detection. Exploratory Testing complements automated and scripted tests, providing coverage in areas where formal tests may overlook unexpected issues. By leveraging human observation and analysis, it uncovers subtle, complex, or emergent problems that scripted tests are likely to miss.

Question 180: 

Which Agile artifact defines completion criteria for a backlog item or increment?

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

Answer: C) Definition of Done

Explanation:

The Product Backlog is a list of all desired features, enhancements, bug fixes, and requirements for the product. It is a planning and prioritization tool but does not define criteria for when work is considered complete. Its purpose is scope management rather than quality control or completion verification.

The Sprint Backlog contains tasks and work items that the team commits to completing during a sprint. It is a tactical artifact used to organize and track sprint activities. Although it includes work items and their associated tasks, it does not define the standards or criteria that determine whether an item meets completion requirements. Its focus is on execution rather than definition of quality or readiness.

The Burndown Chart visually represents remaining work over time in a sprint. While it helps monitor progress and ensures transparency, it does not specify completion criteria for individual backlog items or increments. Its role is quantitative tracking, not qualitative assessment of completeness or readiness.

The Definition of Done is correct because it establishes explicit criteria that must be met for a backlog item or increment to be considered complete. This artifact ensures that work is consistently evaluated against agreed-upon standards, promoting quality, transparency, and shared understanding among team members and stakeholders. It guides testing, documentation, and acceptance processes, making increments potentially shippable. By providing a clear benchmark for completion, the Definition of Done supports iterative delivery, reduces ambiguity, and ensures alignment with Agile principles. It helps teams avoid partially completed work, improves predictability, and fosters confidence that each increment adds tangible value to the product.