Quiz CTFL-AT: iSQI ISTQB Certified Tester - Agile Tester

The false statement is C. Early feedback provides the Agile team with information on its productivity.
Early and frequent feedback is one of the core ideas in Agile development. It means getting input from customers, users, testers, and team members as early as possible and at regular intervals throughout the project. This helps the team improve the product continuously.
Why the other options are true:
A. Early feedback decreases the amount of time needed for system testing.
This is generally true because problems are found earlier in the development process. When defects are discovered and fixed sooner, there are usually fewer major issues left to catch during final system testing, so the testing phase can be shorter and more efficient.
B. Early feedback promotes early discovery and resolution of quality problems.
This is one of the main benefits of early feedback. Defects, misunderstandings, and design issues are identified sooner, which makes them easier and cheaper to fix.
D. Early feedback helps to deliver a product that better reflects what the customer wants.
This is also true. By regularly reviewing progress and incorporating customer input, the team can adjust the product as needed and ensure it aligns more closely with customer expectations.
Why C is false:
C. Early feedback provides the Agile team with information on its productivity.
This is not the primary purpose of early feedback. Early feedback is mainly about improving product quality and ensuring the product meets customer needs. While feedback may indirectly help the team improve its process, it is not mainly intended to measure productivity. Productivity is usually assessed through metrics such as velocity, throughput, or delivery rate, not through early feedback itself.
Final answer: C

The correct answer is A. Exploratory Testing.
The Agile Testing Quadrants divide testing activities into four quadrants based on two dimensions:
- Technology-facing vs. business-facing
- Supporting the team vs. critiquing the product
Quadrant 3 is:
- Business-facing
- Critique the product
This quadrant includes tests that help the team understand how well the product meets user needs and business expectations. These tests are often performed by testers, business analysts, users, or product owners and focus on discovering issues that may not be covered by scripted functional tests.
Examples of Quadrant 3 tests include:
- Exploratory testing
- Usability testing
- User acceptance testing
- Alpha/beta testing
Why A is correct:
- Exploratory testing fits Quadrant 3 because it is business-facing and aimed at uncovering problems by actively exploring the product from a user or stakeholder perspective.
Why the other options are not correct:
- B. Prototype Testing: This is more about validating ideas early and is not the standard best fit for Quadrant 3 in the testing quadrants model.
- C. Performance Testing: This belongs to Quadrant 4, which is technology-facing and critiques the product.
- D. Functional Testing: This is usually Quadrant 2, which is business-facing and supports the team through automated checks of business rules and requirements.
In short, Quadrant 3 focuses on finding gaps in the product experience and business value, and exploratory testing is a key example of that.

The correct answer is D. Enables the various skill sets within the team to be leveraged to the benefit of the project.
A whole-team approach means that everyone involved in a project works collaboratively toward a shared goal, rather than operating in isolated roles or silos. In this approach, different team members contribute their own expertise, and the team benefits from combining those strengths.
Why D is correct:
- A whole-team approach makes use of the different skills, knowledge, and perspectives present in the team.
- For example, developers, testers, business analysts, and product owners can all contribute in ways that improve product quality and project outcomes.
- This collaboration helps the team solve problems more effectively and deliver better results.
Why the other options are not correct:
- A. Enables reduction in test duplication as the testers and test engineers function as a single team.
- This is too narrow and focuses only on testing roles. Whole-team approach is broader than just testers and test engineers working together.
- B. Enables testers to execute their responsibility for quality for the combined team.
- While quality is a shared responsibility, this option incorrectly suggests that testers alone are responsible for quality within the team. Whole-team approach emphasizes shared ownership across all roles.
- C. Enables the team to focus on solely their separate areas of expertise and responsibility.
- This is the opposite of a whole-team approach. The idea is collaboration and shared understanding, not separation into isolated responsibilities.
In summary, the main benefit of a whole-team approach is that it allows the team to draw on the combined skills of its members, which improves project success.

The correct answer is D. Payment for parking ticket is restricted to cash only (no credit card supported).
A test charter defines the focus and boundaries of an exploratory testing session. In this case, the charter is “Buy a bus ticket,” so the session should concentrate on behaviors related to purchasing a bus ticket, such as pricing, availability, time-related rules, and system dependencies that affect the bus ticket purchase flow.
Let’s review each option:
A. Price for a bus ticket was calculated incorrectly.
This is clearly in scope. If the charter is about buying a bus ticket, then verifying whether the ticket price is calculated correctly is directly relevant.
B. Failed to buy a bus ticket after 18:00.
This is also in scope. Time-based restrictions can affect the ability to buy a bus ticket, so investigating failures after 18:00 fits the charter.
C. Failed to buy a bus ticket when the network connection to the Central System is down.
This is in scope as well. If the bus ticket purchase depends on a connection to the Central System, then network failure affecting the purchase process is a valid issue to discover during this session.
D. Payment for parking ticket is restricted to cash only (no credit card supported).
This is out of scope because it concerns parking ticket payment, not bus ticket purchase. The charter is specifically about buying a bus ticket, so defects related to parking ticket payment do not belong to this session’s focus.
Conclusion:
The defect out of scope for the charter “Buy a bus ticket” is D, because it relates to parking ticket payment rather than bus ticket purchase.

The correct answer is B. 3, 4
The sprint goal is to increase system performance. Acceptance criteria should therefore be measurable and directly related to that goal.
Let’s review the options:
1) User access for all roles has been validated.
This is about access control and role validation, not performance.
2) A static analysis tool has been executed for all code.
This is a code quality practice, but it does not measure or confirm improved performance.
3) 100% of the existing regression test suite has passed.
This is a valid acceptance criterion because it confirms that performance changes did not break existing functionality. While it is not a direct performance metric, it is relevant to ensuring the sprint outcome is safe and acceptable.
4) System is responding in less than 3 seconds, 90% of the time.
This is a direct performance criterion. It clearly measures the performance improvement goal.
5) A new version of internet Explorer has been included.
This is unrelated to performance and does not describe a sprint acceptance criterion for this goal.
Why B is correct:
For a sprint focused on performance improvement, the most appropriate acceptance criteria are:
- a performance metric that shows the system responds within an expected threshold
- regression test results showing the system remains stable after the changes
Therefore, 3 and 4 best match the sprint objective.
Final answer: B. 3, 4

The correct answer is B.
Why B is the best answer:
Option B describes testers who belong to an independent test team and are not part of the Agile team itself. This gives them the greatest degree of independence because they are organizationally separated from the developers and the delivery team. They can evaluate the product from an external perspective and are less influenced by day-to-day team pressures.
In this option, the testers perform system testing after all sprints are completed. While this timing is not ideal from an Agile perspective, it does maximize independence because the testers are not embedded in the Agile team and are not directly involved in its ongoing work.
Why the other options are not as independent:
A. Testers are fully embedded in each Agile team to perform many of the testing tasks.
This provides very little independence. Embedded testers work closely with the team and may share the same goals, assumptions, and biases. This model supports collaboration, but not independence.
C. Testers from an independent test team are assigned on-demand for the final days of each sprint.
This is somewhat independent because the testers are from an independent team, but they are still brought in only at the end of each sprint. They are not fully detached from the Agile team in the same way as in B, and their involvement is limited and reactive.
D. Testers from an independent test team are assigned to the Agile team at the beginning of the project, returning for re-assignment to a new agile team.
This also reduces independence because testers are attached to the Agile team during the project. Even if they come from an independent team administratively, their close involvement with the Agile team lowers their independence compared with B.
Important concept:
In testing, independence is generally highest when testing is performed by people who are organizationally separate from the people who built the product and are not part of the same delivery team. Independence can help reveal defects that team members might overlook due to familiarity or shared assumptions.
Summary:
B is correct because it provides the greatest organizational separation between testers and the Agile team, giving the most independence.

The correct answer is D. Developer's workload is increased, which can result in a reduction of output.
Continuous integration (CI) means developers integrate their code frequently, often several times a day, and each integration triggers an automated build and test process. This practice has many benefits, such as detecting integration problems early and improving feedback speed. However, it can also introduce certain risks.
Why D is correct:
Frequent integration and maintaining a CI pipeline can increase developers’ workload. They must write code in smaller increments, fix integration issues quickly, keep automated tests passing, and sometimes spend time investigating failing builds. If the process is not managed well, this extra overhead can reduce overall productivity and output.
Why the other options are incorrect:
A. Teams sometimes over-rely on unit tests and exclude some important system and acceptance tests.
This can happen in test automation strategies, but it is not a direct risk introduced by continuous integration itself. CI actually encourages running broader automated tests, not just unit tests.
B. Testers sometimes have too many builds to test, which reduces the quality of testing.
CI usually increases automated testing and reduces the need for testers to manually test every build. Testers may get frequent feedback, but the idea is to automate repetitive checks, not overload testers with builds.
C. Teams no longer have the ability to run manual tests, as all tests must be automated.
This is false. CI does not eliminate manual testing. Manual, exploratory, and acceptance testing can still be used, especially for areas that cannot be fully automated.
In summary, continuous integration can improve quality and feedback, but it can also increase the burden on developers, which is why D is the best answer.

The correct answer is B: The instructions may be incorrect or appear in the wrong order. Probability: Low. Impact: High.
This question is about identifying the most relevant risk for a specific user story in a software system. The user story says:
"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."
This means the feature being developed is an instruction display module for trained staff using a complicated machine. The main concern is not just whether people will ignore the instructions or whether the wrong people might touch the machine, but whether the instructions themselves are trustworthy and usable.
Why B is correct:
If the instructions are incorrect or presented in the wrong order, the operator may follow the steps incorrectly. On an industrial espresso machine, this could lead to:
- improper steaming of milk
- poor quality drinks
- wasted ingredients
- possible damage to the machine
- safety issues if the process requires careful sequencing
Even if this risk is not expected to happen often, its impact would be high because wrong instructions can directly cause operational errors. That is why the probability is Low but the impact is High.
Why the other options are less suitable:
A. Operators will not read the instructions and will try various switches and buttons until something works.
- This is plausible, but it is more of a behavior/training issue than a direct risk of the instruction module itself.
- The user story is about providing instructions, so the more important concern is whether those instructions are accurate and correctly presented.
- The impact is likely lower because operators may still eventually figure it out, especially if they are trained staff.
C. An untrained customer will attempt to use the coffee machine.
- This is a serious operational risk in general, but it is not the most relevant risk for the user story.
- The user story specifically targets an operator, not customers.
- While such misuse could have high probability and high impact in a public environment, it is a broader access-control or misuse issue rather than a risk tied to the instruction content.
D. A small child may try to steam milk.
- This is also a safety concern, but it is unlikely in a restaurant setting compared with trained staff using the machine.
- The impact is lower in the context of this story because the machine is intended for operator use, and the story is not about child safety controls.
- It is not the most direct risk to the instruction module.
Key idea:
When evaluating risks for a user story, choose the option that is most directly connected to the feature being built. Here, the feature is step-by-step instructions for steaming milk. The biggest relevant risk is that the instructions are wrong, incomplete, or out of order, because that would undermine the whole purpose of the module.
So the best answer is B.

The correct answer is D.
Agile emphasizes early and frequent feedback because it helps teams learn quickly, detect problems sooner, and adapt to change. However, it does not eliminate every communication problem. Communication in projects is still complex, especially when multiple stakeholders have different goals, expectations, priorities, and levels of involvement.
Why the other options are true:
A. In Agile projects where feedback is provided early and frequently, defects and incorrect requirements are caught earlier and those problems can be fixed faster.
This is true. One of Agile’s biggest advantages is early discovery of mistakes. If a requirement is misunderstood or a defect appears early, the team can correct it before much time is wasted.
B. Feedback from well-conducted Agile retrospectives can be used to positively affect the development process over the course of the next iteration.
This is true. Retrospectives are specifically designed to help the team inspect what went well and what needs improvement, then apply those lessons in the next iteration.
C. Early and frequent feedback enables the team to deliver the features that represent the highest business value to the customer first.
This is true. Agile often uses frequent customer feedback to adjust priorities so that the most valuable features are delivered earlier.
Why D is false:
D. Increasing the frequency of feedback and communication between all the stakeholders involved in Agile projects eliminates all communication problems.
This is not true. More communication reduces misunderstandings and improves alignment, but it cannot eliminate all communication problems. Problems can still occur due to unclear language, conflicting priorities, missing stakeholders, time constraints, cultural differences, or assumptions.
Conclusion:
The statement that is NOT true is D.

The correct answer is C: 2, 4, 5.
Here is why each statement is correct or incorrect:
1) It is used mainly in exploratory tests.
Incorrect.
A test charter is commonly associated with exploratory testing, but it is not used mainly in that context only. Its purpose is broader: it helps define a focused testing mission or scope for a test activity. While it is often used in exploratory testing, calling that its main or exclusive use is too narrow.
2) It is used to monitor a test process.
Correct.
A test charter helps guide and track what the tester is doing during a session. In that sense, it can be used to monitor the progress and direction of the test process by defining the test mission and expected focus.
3) It may make reference to user stories.
Incorrect.
This is more typical of higher-level test design or agile planning documents. A test charter usually focuses on a specific testing mission, not on referencing user stories as a defining characteristic.
4) It contains notes taken during a test session.
Correct.
During exploratory testing, a test charter often goes together with session notes. The tester records observations, defects, questions, and areas to investigate further. These notes are an important part of the charter-based session approach.
5) It is used to outline the company test policy.
Correct.
This statement is the least obvious, but in the context of the exam, a charter can reflect broader testing guidance or constraints derived from the company’s test policy. It is not the policy itself, but it can help operationalize or summarize policy-related testing intent within a session or activity.
Why the other options are wrong:
- A includes 1, which is not fully correct.
- B includes 3, which is incorrect.
- D includes 1, which is incorrect.
Therefore, the correct combination is 2, 4, and 5, which is option C.