A tester on an Agile project typically performs the following tasks 1 2 :

Implementing test strategy: A tester helps to define and implement the test strategy for the Agile project, which includes the test approach, test levels, test types, test techniques, test tools, test environment, test data, test metrics, and test documentation.

Measuring and reporting test coverage: A tester measures and reports the test coverage of the product features and quality attributes, such as functionality, usability, performance, security, etc. Test coverage can be expressed in terms of test cases, test scenarios, test sessions, test conditions, test data, code, etc.

Coaching development team in relevant aspects of testing: A tester coaches the development team in relevant aspects of testing, such as test design, test execution, test automation, test-driven development, behavior-driven development, exploratory testing, etc. A tester also helps the development team to improve their testing skills and practices.

The following tasks are not typically performed by a tester on an Agile project:

Documenting business requirements: Business requirements are usually documented by the product owner or the business analyst, not by the tester. The tester may review and provide feedback on the business requirements, but the tester is not responsible for documenting them.

Executing test-driven development tests: Test-driven development tests are usually executed by the developers, not by the tester. The tester may assist the developers in creating and reviewing the test-driven development tests, but the tester is not responsible for executing them.

Therefore, the correct answer is C, as it contains the tasks that are typically performed by a tester on an Agile project.  References : ISTQB Foundation Level Agile Tester Extension Syllabus 1 , pages 14-15, 18-19, 22-23; ISTQB Agile Tester Sample Exam 2 , question 17.

Comprehensive and Detailed Explanation From Exact Extract:

From CTFL-AT Syllabus v4.0 , Section 3.1 Testing Techniques and Agile , it states:

"Decision table testing is useful when the outcome depends on combinations of inputs or rules."

In this case, different reimbursement percentages are determined based on types of visits and subtypes , making Option A (Decision Table Testing) the ideal technique.

Option B focuses on single input ranges , less suitable here.

Option C suits end-to-end scenarios but not logic-driven calculations.

Option D applies to state-based systems , which this is not.

Comprehensive and Detailed Explanation From Exact Extract:

From the CTFL-AT Syllabus v4.0 , Section 5.1, it states:

"The team uses the retrospective to review how they worked during the iteration, including planning accuracy and team collaboration, and to identify actionable improvements."

Thus, Option D is correct — retrospectives help reflect on iteration planning accuracy, team dynamics , and efficiency to improve future iterations.

Option A is incorrect — retrospectives aim to focus on what the team can improve , not just on external hindrances.

Option B is false — Agile retrospectives require follow-up , often in the form of action items tracked in the next iteration.

Option C is incorrect — Product Owner and possibly others may contribute, depending on team context.

Risk-based testing is a technique that prioritizes testing activities based on the level of risk associated with each feature or requirement. The level of risk is usually calculated by multiplying the probability and impact of each risk. The higher the risk level, the more testing effort should be allocated to mitigate the risk. In this case, the risk level for each option is as follows: A. Risk level = Low x Low = Low B. Risk level = Low x High = Medium C. Risk level = High x High = High D. Risk level = High x Low = Medium Therefore, the highest risk level is C, followed by B and D, and then A. The User Story for the Operator-Instructions module should be tested according to this risk order, starting with C, then B, then D, and finally A.  Hence, the answer is B, as it is the second highest risk level and should be tested after C.  References : ISTQB Foundation Level Agile Tester Extension Syllabus 1 , page 16; ISTQB Agile Tester Sample Exam 2 , question 18.