In the next two months some new features will be constantly added to new releases of a project you are working on as Test Manager. You have…

This option represents a proactive, pragmatic, and experience-based risk mitigation strategy. In projects with evolving requirements, waiting for complete specifications is often infeasible and leads to delays. By leveraging the team's experience from similar past projects, they can make reasonable assumptions to begin test design. Creating "lightweight" or high-level test cases that are easily adaptable allows the team to make tangible progress. This approach ensures that a testing framework is in place and can be quickly refined as requirements solidify, directly mitigating the risk of being unprepared for the test execution phase.

A. This is ineffective as it completely ignores the new features, which are the primary objective of the testing effort, focusing only on existing functionality.
C. This is a passive and counterproductive approach. A Test Manager's role is to proactively manage and mitigate risks, not to wait for them to become blocking issues.
D. While escalating risk is a valid activity, doing so without preparing any tests or proposing a mitigation plan constitutes inaction and is not an effective strategy.

1. ISTQB® Advanced Level Syllabus, Test Manager (Version 2012):

Section 5.2.4, Risk Mitigation: This section details that risk mitigation involves taking steps to reduce the probability and impact of risks. The strategy in option B is a clear example of a mitigation action, where the team acts to reduce the impact of incomplete requirements. In contrast, options A, C, and D represent inaction or incorrect action regarding the specific risk.

Section 2.3.4, Test Strategy and Test Approach: This section explains that the test strategy should be appropriate for the project's risks and objectives. For a project with unstable requirements, a flexible and adaptive strategy that leverages team experience to create preliminary, adaptable test assets is highly appropriate.

2. ISO/IEC/IEEE 29119-2:2021 Software and systems engineering — Software testing — Part 2: Test processes:

Section 5.3, Test Design and Implementation Process: This standard describes test design as the activity of deriving test cases from the test basis (e.g., requirements). The process is iterative. It supports creating initial test cases based on available information and refining them as the test basis becomes more complete, which aligns perfectly with the strategy described in option B.