ATM Exam Dumps : Advanced Test Management Exam v 3.0 – ISTQB

Common Risk Identification Techniques:

A test manager often relies on experience with similar projects to foresee risks related to technical complexity, domain challenges, or previous defects.

Other options listed are less effective for comprehensive risk identification.

Evaluation of Options:

A(Lines of code) andB(Function points) are quantitative measures, not directly tied to risk identification.

Cis correct as past experience is crucial for identifying risks early.

D(Record/playback tools) is irrelevant to risk analysis.

References and Syllabus Alignment:

Risk identification techniques are discussed under "Risk Management" (TM-1.3.1)​​.

Context Analysis:

The developers claim many defect reports are invalid. Reviewing defects that are rejected or closed without fixes can highlight issues like incorrect environment setup or missed testing steps.

Evaluation of Options:

A. In the ones that are stuck in the In Progress state:

Incorrect. These defects are still being investigated, not confirmed as invalid.

B. In the ones that are Resolved but not Closed:

Incorrect. These defects have been fixed but not yet verified; they are not considered invalid.

C. In the ones that are in the status Rejected or Closed without a fix:

Correct. Rejected defects are marked invalid and are directly related to the problem described.

D. In the ones with the status of Re-Opened:

Incorrect. Re-opened defects indicate recurring or unresolved issues, not invalid reports.

Syllabus Alignment:

ISTQB highlights analyzing defect statuses to improve defect reporting and management processes (TM-2.3.5).

References:

ISTQB Advanced Level Test Management Syllabus (TM-2.3.5)​

Context Analysis:

The manager perceives conservative estimates as overly negative. The goal is to balance optimism with realism to satisfy both the team and the manager.

Three-point estimation provides a range of estimates: optimistic, pessimistic, and most likely, addressing the need for a positive yet realistic projection.

Evaluation of Options:

A. Wideband Delphi:

Involves group-based estimation using consensus techniques. While reliable, it does not explicitly offer optimistic vs. realistic estimates.

B. Planning Poker:

Often used in Agile projects, this technique involves relative estimation but does not inherently provide optimistic and pessimistic figures.

C. Three-point estimation:

Correct. Combines optimistic, pessimistic, and realistic estimates to calculate a weighted average. This allows presentation of both realistic and “positive” numbers to the manager.

D. Extrapolation:

Based on past data trends but does not offer a range of estimates or a way to address manager concerns directly.

Syllabus Alignment:The ISTQB syllabus mentions estimation methods like three-point estimation as effective techniques for providing balanced and transparent project timelines (TM-2.2.1).

References:

ISTQB Advanced Level Test Management Syllabus​