Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 10 of 155
Free Preview · 155 of 514 · questions 1–155 of 514 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
A change-driven approach (such as Agile) is designed to accommodate frequent and flexible requirement changes without relying on a formal change control process. According to the BABOK Guide (Chapter 5: Requirements Life Cycle Management - Assess Requirements Changes): Change-driven approaches embrace iterative development and allow requirements to evolve over time. Changes are managed through continuous collaboration with stakeholders rather than formal approval boards. Unlike predictive approaches (Waterfall), which require a structured Change Control Board (CCB), Agile teams adapt requirements dynamically.
C. Change-driven approaches don't use a formal change control process.
C. Change-driven approaches don't use a formal change control process.