Frage 250ISTQB CTFL v4.0 Sample Exam A

Which of the arguments below would you use to convince your manager to organize retrospectives at the end of each release cycle?

Execution 1Execution 2Execution 3
TC1(1) Failed(4) Passed(7) Passed
TC2(2) Passed(5) Failed(8) Passed
TC3(3) Failed(6) Failed(9) Passed

Antwortmöglichkeiten

A.Retrospectives are very popular these days and clients would appreciate it if we added them to our processes
B.Organizing retrospectives will save the organization money because end user representatives do not provide immediate feedback about the product
C.Process weaknesses identified during the retrospective can be analyzed and serve as a to do list for the organization’s continuous process improvement program✓
D.Retrospectives embrace five values including courage and respect, which are crucial to maintain continuous improvement in the organization

Richtige Antwort

C: Process weaknesses identified during the retrospective can be analyzed and serve as a to do list for the organization’s continuous process improvement program

Dieses Prüfungsset übenAlle Fragen ansehen

Weitere Fragen aus dieser Prüfung

#239

Which of the following statements describe a valid test objective?

#240

Which of the following options shows an example of test activities that contribute to success?

#241

You have been assigned as a tester to a team producing a new system incrementally. You have noticed that no changes have been made to the existing regression test cases for several iterations and no new regression defects were identified. Your manager is happy, but you are not. Which testing principle explains your skepticism?

#242

You work in a team that develops a mobile application for food ordering. In the current iteration the team decided to implement the payment functionality. Which of the following activities is a part of test analysis?

#243

Which of the following factors (i-v) have SIGNIFICANT influence on the test process? i. The SDLC ii. The number of defects detected in previous projects iii. The identified product risks iv. New regulatory requirements forcing formal white-box testing v. The test environment setup