Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

ISTQB Exam ISTQB-Agile-Public Topic 1 Question 5 Discussion

Actual exam question for ISTQB's ISTQB-Agile-Public exam
Question #: 5
Topic #: 1
[All ISTQB-Agile-Public Questions]

Why is regression of software a high risk in agile projects?

SELECT ONE OPTION

Show Suggested Answer Hide Answer
Suggested Answer: A

In agile projects, the high risk of regression is primarily due to the code churn that occurs as business needs change over the course of several sprints. This is inherent in the agile process, where requirements and solutions evolve through collaborative effort. The iterative nature of agile projects means that as new features are added or existing features are modified to meet evolving business needs, previously tested and stable parts of the software might be affected, leading to potential regression issues. This phenomenon is well-recognized in agile methodologies and necessitates rigorous regression testing practices to ensure that new changes do not adversely affect existing functionalities.


Contribute your Thoughts:

Major
6 months ago
C) Regression is built into software as a safeguard against unexpected failures.
upvoted 0 times
...
Gerry
6 months ago
I disagree with option B, as test automation helps catch regressions early.
upvoted 0 times
...
Howard
6 months ago
B) Test automation can cause regression of software in the test environment.
upvoted 0 times
...
Bev
7 months ago
I think option A is correct because agile projects often have changing requirements.
upvoted 0 times
...
Olga
7 months ago
A) There is code churn due to change in business needs over several sprints.
upvoted 0 times
...
Gaynell
7 months ago
Why is regression of software a high risk in agile projects?
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77