Q119. During what step of the Fundamental Test Process should you define the methods to be used to collect test metrics? [1]
The correct answer is B. Planning. This is because test metrics are quantitative measures that are used to monitor and control the test process, and to evaluate the test results and quality. Test metrics should be defined during the planning step of the Fundamental Test Process, which is the activity of establishing the test objectives, scope, approach, resources, schedule, and deliverables. By defining the methods to be used to collect test metrics during the planning step, the test team can ensure that the test metrics are aligned with the test plan and the project goals, and that the data collection process is consistent and efficient. Test Metrics – ISTQB not-for-profit association References: Certified Tester Advanced Level Test Manager (CTAL-TM) – ISTQB not-for-profit association, ISTQB Test Manager Certification – ISTQB Exams Worldwide – ISTQB Official Registration, Test Metrics – ISTQB not-for-profit association
Q125. What is the purpose of tracking efficiency metrics for a formal review? [1]
Efficiency metrics for a formal review are used to measure the cost-effectiveness of the review process, such as the time spent on the review, the number of defects found, and the return on investment1. These metrics can help to evaluate if the review was a good use of resources, such as human effort, money, and tools.
Therefore, option B is the correct answer. Option A is incorrect because efficiency metrics do not track who participated in the review, but rather how they performed. Option C is incorrect because efficiency metrics do not measure the quality of the reviewed object, but rather the quality of the review process. Option D is incorrect because efficiency metrics do not measure the speed with which defects were fixed, but rather the speed with which defects were detected. References: 1: How to manage formal reviews & management audits? Skills, metrics …
Q129. You are the Test Manager on a new project. The schedule is aggressive and will require the team to work at peak efficiency. The requirements are not well defined yet, but it is clear that the project will be using new technologies. To help the developers meet the development schedule, an offshore group will be added to the development team.
At this time there is not enough budget to add more testing resources. The project stakeholders are very concerned about the quality of delivered product and will be watching the project closely, particularly during the testing cycles. The exit criteria from the system test level require no open high priority/severity defects, 100% pass rate for all test cases covering risks that are classified as
“high” or “very high”, 90% pass rate for all “medium” risks and 50% pass rate for all “low” and “very low” risks.
Given this information, which lifecycle model should you recommend?[3]
An iterative/incremental lifecycle model is a type of software development lifecycle that divides the project into smaller iterations or increments, each delivering a part of the functionality and undergoing its own planning, analysis, design, implementation, and testing phases1. This model is suitable for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it allows for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement2. Therefore, option B is the correct answer. Option A is incorrect because a spiral model is a type of iterative/incremental model that adds risk analysis and prototyping activities to each iteration3. While this model can also handle unclear requirements, new technologies, and high quality expectations, it may not be the best choice for projects that have aggressive schedules and distributed teams, as it requires more time and communication for risk assessment and prototyping4. Option C is incorrect because a V-model is a type of sequential model that maps each development phase to a corresponding testing phase in a V-shaped diagram5. This model is suitable for projects that have clear and stable requirements, well-known technologies, co-located teams, and moderate quality expectations, as it allows for early verification, traceability, and defect prevention. However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement. Option D is incorrect because a waterfall model is a type of sequential model that follows a linear sequence of phases from requirements to deployment. This model is suitable for projects that have simple and fixed requirements, well-known technologies, co-located teams, and low quality expectations, as it allows for easy planning, management, and documentation. However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement. References: 1: ISTQB Glossary, Iterative/incremental lifecycle model 2: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 3:
ISTQB Glossary, Spiral model 4: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 5: ISTQB Glossary, V-model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Glossary, Waterfall model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1