ISTQB-Agile-Public Exam Practice Test Instant Access

Question 1

Which two of the following statements are CORRECT with regards to test automation on agile projects?

i) Every test developed for past iterations is kept and executed as part of a regression suite for each new release of code.

ii) It would be very difficult to ensure high quality in an agile project without test automation.

iii) Automated acceptance tests are run regularly as part of the continuous integration full system build.

iv) Automated regression suites are only run for the final release of code.

v) In agile projects, the results from automated acceptance tests provide feedback on the overall product quality.

SELECT ONE OPTION

Aii, iii

Bii. v

Ci, iii

Diii, iv

Answer : A

In Agile projects, test automation plays a crucial role in maintaining high quality and accommodating the rapid pace of iterative development. Statement ii highlights the difficulty of ensuring high quality without test automation, given Agile's frequent changes and fast iterations. Test automation facilitates continuous testing, allowing teams to quickly identify and address issues. Statement iii, regarding automated acceptance tests being part of continuous integration, underscores the Agile practice of integrating and testing changes regularly to ensure that the product evolves correctly with each iteration. This practice aligns with the principles of Agile methodologies that advocate for sustainable development, continuous attention to technical excellence, and good design to enhance agility.

Question 2

Which of the following is a benefit of a whole-team approach?

SELECT ONE OPTION

AEnables testers to execute their responsibility for quality for the combined team

BEnables the team to focus on solely their separate areas of expertise and responsibility.

CEnables reduction in test duplication as the testers and test engineers function as a single team.

DEnables the various skill sets within the team to be leveraged to the benefit of the project.

Answer : D

The whole-team approach in agile methodologies is beneficial because it leverages the diverse skill sets within the team for the project's benefit. In this collaborative environment, team members, including developers, testers, and business analysts, work closely together from the project's outset. This close collaboration ensures a better understanding of the project goals, more innovative solutions to problems, and a higher quality product. The whole-team approach encourages knowledge sharing and collective problem-solving, leading to more efficient and effective project outcomes. This approach contrasts with traditional methodologies, where roles are more siloed, and collaboration between different roles occurs less frequently.

Question 3

Which of the following describes the main purpose of a task management tool in agile projects?

SELECT ONE OPTION

AA task management tool allows developers to continuously integrate their code.

BA task management tool is used by team members to share ideas and collaborate on assigned tasks.

CA task management tool is used to manage and track user stories, tests and other tasks.

DA task management tool is used to store source code and automated tests.

Answer : C

In agile projects, task management tools play a crucial role in facilitating project management and team collaboration. Specifically, option C accurately describes the primary function of a task management tool in agile contexts. These tools are designed to manage and track various elements of agile projects, including user stories, tests, tasks, and more, thereby enabling teams to maintain visibility and control over the project's progress.

Agile methodologies prioritize adaptability, customer collaboration, and the delivery of value through iterative development cycles. Task management tools support these principles by providing a platform for organizing work, prioritizing tasks, and ensuring that all team members are aligned on the project's objectives and progress. This alignment is essential for maintaining the agility and responsiveness characteristic of agile projects.

For example, the Scrum framework, a popular agile methodology, involves creating a product backlog that contains all the user stories and tasks needed for the project. The task management tool would be used to track these items through various stages of development, from the backlog to in-progress, testing, and completion. This tracking ensures that the team can adapt to changes, manage workloads effectively, and deliver increments of value to the customer consistently.

In summary, option C is the verified answer as it encapsulates the essential purpose of a task management tool in agile projects, which is to manage and track user stories, tests, and other tasks, thereby supporting the agile principles of adaptability, customer collaboration, and iterative delivery of value.

Question 4

Which of the following is NOT a typical task performed by the tester within an Agile team?

SELECT ONE OPTION

AEnsuring the appropriate testing tasks are scheduled during iteration planning.

BEnsuring all project status meetings are held according to the plan.

CSuggesting improvements in team retrospectives.

DWorking with business stakeholders to clarify requirements.

Answer : B

Question 5

Which of the following statements is FALSE regarding early and frequent feedback?

SELECT ONE OPTION

AEarly feedback provides the Agile team with information on its productivity.

BEarly feedback promotes early discovery and resolution of quality problems.

CEarly feedback decreases the amount of time needed for system testing.

DEarly feedback helps to deliver a product that better reflects what the customer wants.

Answer : C

Early and frequent feedback is fundamental in Agile methodologies to ensure the product meets customer needs and to identify and resolve issues promptly. However, the statement that early feedback decreases the time needed for system testing (Option C) is misleading. While early feedback helps in identifying and resolving issues at an early stage, it does not necessarily reduce the overall time required for system testing. System testing is a comprehensive phase that assesses the system's compliance with the specified requirements. Agile practices, such as continuous integration and testing, aim to maintain a high quality throughout the development process, but they do not eliminate the need for thorough system testing to validate the product before release.

Question 6

You are developing the code that controls an industrial Espresso machine which will be operated by waiting staff in restaurants.

The machine is rather complicated and has lots of switches and buttons, so in the next iteration instructions will be provided to the operator on a small LCD screen.

A User Story for the Operator-Instructions module is as follows:

"As an operator of the Espresso machine, I would like to know how to steam milk, so I can add steamed milk to the coffee."

The following is a list of risks identified for this story, with assigned probability and impact.

Which of these is most correct in the context of the given User Story?

SELECT ONE OPTION

AAn untrained customer will attempt to use the coffee machine. Probability: High. Impact: High

BThe instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High

COperators will not read the instructions and will try various switches and buttons until something works. Probability: Low. Impact: Low

DA small child may try to steam milk. Probability: High. Impact: Low

Answer : B

In the context of the provided User Story for the Operator-Instructions module of an industrial Espresso machine, option B is the most pertinent risk. This option states, 'The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.' This risk directly affects the core functionality described in the User Story, which is to provide operators with accurate instructions for steaming milk.

Agile methodologies emphasize the importance of delivering value to the customer through functional and usable increments of the product. Incorrect or improperly ordered instructions would directly undermine the usability of the Espresso machine for its intended operators, potentially leading to operational errors, customer dissatisfaction, and a failure to deliver the intended value of the User Story.

While the other risks mentioned (A, C, and D) might have their relevance in broader project considerations, they do not directly impact the achievement of the User Story's goal as much as option B does. The risk of incorrect or out-of-order instructions is particularly significant because it could lead to improper operation of the machine, resulting in quality issues with the product (steamed milk in this case) or even damage to the machine, both of which have high impact on the project's success.

Therefore, option B is the verified answer as it most accurately reflects a risk that is directly related to the achievement of the User Story's objective, aligning with agile principles of focusing on delivering functional and valuable product increments to the customer.

Question 7

Which of the following is NOT a statement of value from the Agile Manifesto?

SELECT ONE OPTION

Asoftware over comprehensive documentation.

BResponding to change over following a plan.

CProcesses and tools over individuals and interactions.

DCustomer collaboration over contract negotiation.

Answer : C

The Agile Manifesto, a foundational document for Agile development, outlines four core values intended to guide Agile practices. Option C, 'Processes and tools over individuals and interactions,' is not a statement of value from the Agile Manifesto. In fact, the correct value stated in the Agile Manifesto is the opposite: 'Individuals and interactions over processes and tools.'

The Agile Manifesto values are as follows:

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 people, collaboration, adaptability, and the delivery of functional software in Agile development. The manifesto suggests that while processes, tools, documentation, contracts, and plans have their place, they should not overshadow the importance of human elements, effective collaboration, and responsiveness to change.

Option C is the verified answer because it misrepresents the Agile Manifesto's values by prioritizing processes and tools over individuals and interactions, which contradicts the manifesto's emphasis on the latter. This understanding is crucial for implementing Agile practices that align with the manifesto's intent to foster more adaptive, people-oriented, and customer-focused approaches to software development.

ISTQB Agile Public Sector ISTQB-Agile-Public Exam Practice Test