Discuss ISTQB ATM Exam Topic 2 Question 30

The main objectives the senior management team wants to achieve are:

- to reduce the costs associated with dynamic testing

- to use reviews to ensure that the project is on course for success and following the plan

- to use reviews as a well-documented and effective bug-removal activity following a formal process with well-defined roles

- to determine the effectiveness of reviews in terms of phase containment

- to improve phase containment effectiveness

Which of the following answers would you expect to describe the best way to achieve these objectives?

K4 3 credits

AYou should plan for lightweight exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects

BYou should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects

CYou should plan for formal exit-phase reviews at the end of each development phase and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the people responsible for those bugs

DYou should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the phase in which they have been introduced

Suggested Answer: A

Get Premium ATM Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

36 comments · newest first

Dominque 11 months ago

Wait, are we really analyzing bugs to find out who caused them? That seems intense!

Flo 11 months ago

Definitely agree with focusing on phase containment!

Art 11 months ago

Isn't it risky to rely too much on formal processes?

Thersa 11 months ago

I think lightweight reviews could save time and still be effective.

Glenna 12 months ago

Formal exit-phase reviews sound like a solid plan!

German 12 months ago

I practiced a similar question where we had to choose between lightweight and formal reviews, and I think formal reviews are generally more effective for ensuring thoroughness.

Pamela 12 months ago

I'm a bit confused about whether we should focus more on the process of gathering information or the type of reviews. I feel like both are important.

Marge 1 year ago

I think option D sounds familiar because it emphasizes analyzing bugs to find out which phase they were introduced in, which could help with phase containment.

Daron 1 year ago

I remember we discussed the importance of formal exit-phase reviews in class, but I'm not sure if they should be lightweight or formal for this scenario.

Wynell 1 year ago

This is a good one. I reckon the key benefit is the ability to trigger product-specific scoring and program status changes. That would give Bhaskar a lot more control and flexibility in managing their products.

Jaime 1 year ago

Hmm, I'm a little unsure about this one. I know piece rate is based on production, but I can't remember if that's the same as an individual's rate of production. Let me think this through carefully.

Sheron 1 year ago

I can't shake the feeling that option C involves a manual approach that might not be the standard method, but it seems like a valid step nonetheless.

Renay 1 year ago

I considered using NFS for this, but it might not be the best choice for temporary storage. The /tmp directory seems more straightforward and designed for cases like this.

Earleen 1 year ago

Wait, I'm confused. I thought "Feasible" might be the right answer since a requirement has to be achievable to be considered fulfilled. But now I'm second-guessing myself. I need to re-read the question and options more closely.

Tarra 1 year ago

I'm going with Option B. Anything that can help 'reduce the costs associated with dynamic testing' is a winner in my book!

Anika 1 year ago

↳ replying to Tarra

Option B does sound like a practical approach to meet the objectives. It's important to have a well-defined process in place for reviews.

Alise 1 year ago

↳ replying to Tarra

I think Option B is a good choice too. It seems like a solid plan for achieving the objectives set by the senior management team.

Caprice 1 year ago

↳ replying to Tarra

I'm going with Option B. Anything that can help 'reduce the costs associated with dynamic testing' is a winner in my book!

Darrin 1 year ago

Option B is the way to go, no doubt. Formal reviews and a robust defect analysis process? Sign me up!

Irving 1 year ago

Option B is the clear winner here. Formal reviews and a data-driven approach to defect analysis - that's the secret sauce to success!

Lillian 1 year ago

Hmm, I'm not so sure. Option D also seems reasonable, as identifying the phase where bugs were introduced could be useful for improving phase containment effectiveness.

Rosalind 1 year ago

↳ replying to Lillian

Planning for formal exit-phase reviews at the end of each development and testing phase seems like a thorough approach to achieving the objectives.

Ira 1 year ago

↳ replying to Lillian

It's important to have a clear process for analyzing bugs found during testing to determine their origin.

Wai 1 year ago

↳ replying to Lillian

I agree, knowing when the bugs were introduced can definitely help in preventing similar issues in the future.

Lamar 1 year ago

↳ replying to Lillian

Option D seems like a good choice. Identifying the phase where bugs were introduced can help improve phase containment effectiveness.

Lorean 1 year ago

I agree, Option B is the way to go. It focuses on the right activities like reviews and defect analysis, which align with the management team's objectives.

Justine 1 year ago

Option B seems to cover all the key objectives mentioned in the question. Formal exit-phase reviews at the end of each phase, combined with a defect analysis process, would be the best approach to achieve the stated goals.

Carole 1 year ago

↳ replying to Justine

C) You should plan for formal exit-phase reviews at the end of each development phase and testing phase, and plan for a process of gathering information from testing to perform an analysis of the bugs found during testing to determine the people responsible for those bugs

Tayna 1 year ago

↳ replying to Justine

B) You should plan for formal exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects

Jacinta 1 year ago

↳ replying to Justine

A) You should plan for lightweight exit-phase reviews at the end of each development and testing phase, and plan for a process of gathering information from testing to perform an analysis aimed at identifying the larger cluster of defects

Polly 1 year ago

I'm not sure, but I think option C could also work well in ensuring bug-removal activities are effective.

Bernadine 1 year ago

I agree with Georgiann, option D seems to be the most effective in improving phase containment.

Georgiann 1 year ago

I think option D would be the best way to achieve the objectives.

Ronnie 1 year ago

I'm not sure, but I think option C could also be a good choice. It mentions analyzing bugs found during testing to determine the people responsible for those bugs.

Izetta 1 year ago

I agree with Shawnna. Option D seems to focus on identifying when bugs were introduced, which can help improve phase containment effectiveness.

Shawnna 1 year ago

I think option D would be the best way to achieve the objectives.

ISTQB ATM Exam - Topic 2 Question 30 Discussion