The predictive approach to delivery is a more formal approach and hence can cause a rework of tasks and activities already completed when a change is implemented as well as of the activities required to assess the proposed change on the whole.
A lot of requirements elicitation and analysis done in the early phases of a project follow the predictive approach. This means when a change is required during later phases of this type of project, there is often a higher impact on the time, cost, and effort required. An adaptive approach will try and minimize the impact of changes with iterative implementations from an early stage of the project. This approach typically lends itself to a less formal and more adaptable approach to manage the impact of change that is introduced during the life cycle of the project. Within the adaptive approach to delivery, the idea of an evolutionary delivery may also reduce the need for a formal impact assessment to be performed when a change is proposed to a requirement.

Explanation/Reference:
Requirements verification is the correct answer. This task verifies that requirements specifications and models are accurate so that the endeavor may continue to achieve the best solution for the organization.
A is incorrect. The task of defining assumptions and constraints identifies factors other than
requirements that may affect which solutions are viable.
C is incorrect. The task to specify and model requirements is used to analyze expressed
stakeholder desires and/or the current state of the organization using a combination of textual statements, matrices, diagrams, and formal models.
B is incorrect. The purpose of organizing requirements is to create a set of views of the
requirements for the new business solution that are comprehensive, complete, consistent, and understood from all stakeholder perspectives.

Explanation
Change-driven approaches typically do not use a formal change control process, as requirements are prioritized and selected for implementation at the beginning of each iteration and no changes to the requirements occur during the iteration process.
Answer A is incorrect. Change-driven approaches don't typically use a change control board.
Answer B is incorrect. This isn't a valid statement to describe the processes of change within a change-driven
approach to requirements management.
Answer D is incorrect. This isn't a valid statement to describe the processes of change within a change-driven
approach to requirements management.