You tend to be conservative in your project estimations because you know how many things can go wrong and extend the schedule. You manager is not happy with your estimates and thinks you are being too negative with your numbers and not trying hard enough Which estimation method should you use to provide your manager with a positive' number while still also providing the number you think is more realistic?
Answer : C
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).
ISTQB Advanced Level Test Management Syllabus
You have been asked to make a recommendation on deployment readiness on the software your team has been testing. You have the following metrics:
Given this information what is a critical metric you are missing?
Answer : C
Context Analysis:
Deployment readiness depends on understanding the risk of releasing the software. The metrics provided include execution, design, defect counts, and coverage but do not quantify residual risk, which reflects remaining risks post-testing.
Evaluation of Options:
A . Number of tests passed:
Incorrect. While important, it doesn't directly provide insight into the remaining risk.
B . Number of defects outstanding:
Incorrect. Though critical, it's only one aspect of assessing readiness and doesn't provide the full picture of residual risk.
C . Residual risk:
Correct. Residual risk quantifies untested areas and unresolved issues, vital for decision-making.
D . Planned vs actual cost of testing:
Incorrect. While useful for process evaluation, it's not directly tied to deployment readiness.
Syllabus Alignment:
The syllabus emphasizes risk-based approaches, highlighting residual risk as a critical deployment readiness metric (TM-1.3.4).
ISTQB Advanced Level Test Management Syllabus (TM-1.3.4)
Your company has adopted an Agile methodology. Defect reports are not raised for all bugs found during the testing of individual stories, but continue to be raised in some circumstances, e.g., when the fix cannot be made immediately, or would involve another team. The teams would like better data to use for assessing the quality of their work. The list below shows five items that are currently not captured on defect reports.
Which TWO of these items will be MOST useful for assessing the quality of a product increment?
Answer : B, E
B (Quality characteristic): Tells whether the defect affected security, usability, performance, etc.---directly tied to non-functional quality.
E (User story): Enables tracking of defect-prone functionality and assessment of deliverable quality per increment.
''The information in defect reports supports test process improvement and quality trend analysis. Tracking defects by quality attribute and story link is a valuable input to Agile retrospectives.''
--- ISTQB CTFL Syllabus 2018, Section 3.2.4 and 5.6
These insights are essential for Agile teams focused on continuous improvement and product quality.
Your defect opened trend is converging to the closed trend but there is still a gap. What does that gap represent?
Answer : B
Understanding the Defect Trend Gap:
A gap between 'defects opened' and 'defects closed' usually indicates defects that have been resolved (fixed) but are pending formal closure, often awaiting retesting or approval.
The trend convergence suggests the defect management process is effective, but some defects are still in the verification stage.
Evaluation of Options:
A is incorrect: The gap does not indicate projected but unfound defects.
C is incorrect: Regression defects would cause a divergence, not convergence, in trends.
D is incorrect: Defects introduced to production are unrelated to the convergence.
B is correct as it aligns with the standard defect lifecycle.
Reference and Syllabus Alignment:
This aligns with 'Defect Management' in the ISTQB syllabus, emphasizing defect lifecycle tracking (TM-2.3.1).
Which technique will assist you in determining targeted improvement areas to reduce the number of defects? [1]
You have directed one of your testers to construct a "smoke test" to execute against new builds prior to starting formal testing. This is an example of which software development lifecycle activity?
[1]
It is now the last day of the second iteration and the team has been consistently underestimating the time needed. They estimate intuitively rather than using estimation techniques.
Which two estimation techniques would be BEST for the team in this scenario?
Answer : C, D
C (3-point estimation): Offers a structured approach to improve accuracy by accounting for uncertainty.
D (Planning poker): Commonly used in Agile; supports collaborative and experiential-based estimation.
''Planning poker is an example of the expert-based approach... team members are estimating the effort to deliver a feature based on their experience.''
-- ISTQB-CTFL_Syllabus_2018_V3.1, section 5.2.6