APMG Agile Foundation Practice Exam

When should formal change control be implemented in a DSDM project?

1. When there is a change in depth of requirements

2. When the Business Sponsor requires it

3. When there is a change in breadth of requirements

4. When the Business Visionary wishes to get involved

The correct answer is: When there is a change in breadth of requirements

In a DSDM (Dynamic Systems Development Method) project, formal change control is primarily implemented when there is a change in the breadth of requirements. This practice is essential because it helps to manage the scope of the project effectively. When the breadth of requirements changes, it typically means that new requirements are being added to the project, which can significantly impact resources, timelines, and overall project objectives. Implementing formal change control at this stage ensures that these new requirements are properly evaluated, documented, and integrated into the project plan. This process allows for a systematic assessment of the impact of the changes, ensuring that the project remains aligned with its goals and delivers value to the stakeholders. In contrast, changes in the depth of requirements, the desire of the Business Sponsor for change control, or the involvement of the Business Visionary do not necessarily trigger the need for formal change control in DSDM. Changes in depth often relate to refining existing requirements, which may not require the same level of formal scrutiny as adding new ones. Additionally, decisions driven by individual stakeholders’ preferences can be managed through existing communication and review processes without necessitating formal change control.