Which one of the following statements is most true about changing requirements in a change-driven approach to business analysis and requirements management?

Change-driven (or adaptive/agile) approaches are fundamentally designed to embrace and accommodate change throughout the project lifecycle. They intentionally avoid the formal change control processes, such as a Change Control Board (CCB), that are characteristic of predictive (waterfall) methodologies. Instead, changes to requirements are managed by prioritizing and re-prioritizing work items in a backlog (e.g., a product backlog). The authority to accept changes typically rests with the product owner in collaboration with the team, allowing for flexibility and responsiveness to evolving needs.

A. Change-driven approaches must use a change control system with a change control board: This is false; this formal process is a hallmark of predictive, not change-driven, approaches.
B. Change-driven approaches only use a change control system for approved changes: This is misleading; they manage change through backlog prioritization, not a formal change system.
D. Change-driven approaches are driven by change control processes: This is the opposite of the truth; they are driven by delivering value and welcome change.

IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) Version 3

2015

Section 2.2.2 "Timing of Business Analysis Work"

p. 15.

IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) Version 3

2015

Section 5.4 "Approve Requirements"

pp. 92-94 (This section notes that formal approval may be different or non-existent in adaptive approaches).

IIBA

A Guide to the Business Analysis Body of Knowledge (BABOK® Guide) Version 3

2015

Section 11.2.3 "Change-Driven Perspective"

p. 424.