ISTQB Updated ISTQB-CTFL Exam Questions and Answers by coen

Review leader

Facilitator.

Recorder.

Moderator

It helps avoid the risk of tasks associated with a user story not moving through the Agile task board at an acceptable rate during an iteration.

It helps team members understand the current status of an iteration by visualising the amount of work left to do compared to the time allotted for the iteration

It helps the whole team be more effective in test case design by requiring all team members to master all types of test techniques.

It helps team members develop better relationships with each other and make their collaboration more effective for the benefit of the project.

Only developers and testers should be involved in retrospectives, as involving people in other roles is very likely to prevent developers and testers from having open and constructive discussions that really help identify process improvements.

Retrospectives can be very effective in identifying process improvements and can also be very efficient and cost-effective especially since, unlike reviews, they do not require any follow-up activities

On Agile projects, well-conducted retrospectives at the end of each iteration can help the team reduce and sometimes even eliminate the need for dairy stand-up meetings.

During retrospectives, in addition to identifying relevant process improvements, participants should also consider how to implement these improvements and retain them based on the context of the project, such as the software development lifecycle.

The purpose of confirmation testing is to confirm that the defect giving rise to a failure has been successfully fixed. The regression test aims to ensure that no defects have been introduced or discovered in unmodified areas of the software as a result of the changes made.

Confirmation testing ensures the entire system functions as expected, whereas regression testing focuses only on modified components.

Confirmation testing verifies all system requirements, while regression testing ensures that no additional test cases are needed.

Regression testing and confirmation testing are interchangeable and serve the same purpose.