Dynamic Systems Development Method (DSDM) is an Agile framework that operates on the principle that " nothing is built perfectly the first time " and focuses on frequent delivery of business value. In DSDM, time and cost are fixed, while the scope is variable.

Why Choice D is correct: In DSDM, work is organized into Timeboxes (similar to Sprints in Scrum). One of the core principles of DSDM is " Never Compromise Quality. " When a new high-priority feature arrives, the practitioner follows the formal change process within the Agile framework:

MoSCoW Prioritization: New requirements are added to the prioritized requirements list (Backlog) and categorized using MoSCoW (Must have, Should have, Could have, Won ' t have this time).

Timeboxing: DSDM does not allow for " mid-timebox " disruptions that compromise the current commitments. Instead, the new feature is evaluated and prioritized for the next work period (Timebox). This maintains the team ' s focus and ensures that the current timebox ' s " Must Haves " are delivered as promised.

Analysis of other options:

A (Parallel work package): This creates multitasking and resource contention, which DSDM aims to avoid. It compromises the focus of the current timebox.

B (Shorten the current period): Timeboxes in DSDM are fixed. Shortening them disrupts the cadence and usually results in incomplete or low-quality deliverables for the current cycle.

C (Complete it immediately): This is " reactive " management. It bypasses the prioritization process and ignores the impact on existing work. In DSDM, the Business Visionary or Business Ambassador must first agree on the priority relative to other items.

Key Concept: DSDM relies on Empowered Teams and Iterative Development. By placing the request in the requirements list for the next period (Choice D), the practitioner respects the DSDM philosophy of " fixing " the time and quality while allowing the scope to be re-prioritized based on evolving business needs.