In Dynamic Systems Development Method (DSDM) — an agile framework — timeboxing and prioritization are core principles. New feature requests, even high-priority ones, should be:
Assessed and prioritized properly,
Added to the prioritized requirements list (often called the Prioritized Requirements List, or PRL),
Scheduled for the next appropriate timebox or iteration.
This ensures that planning discipline and team focus are maintained, rather than reacting ad hoc to new requests.
Why the other options are incorrect:
A. ❌ Side-stepping the prioritization process violates DSDM's timebox discipline.
B. ❌ Timeboxes are fixed; you can't unilaterally shorten them.
D. ❌ Ignoring prioritization and timeboxing leads to unmanaged scope creep.
*Prioritize it in the requirements list for the next work period.*
DSDM emphasizes the importance of prioritization and incremental delivery. When a new high-priority feature request is received, it should be added to the requirements list and prioritized according to its urgency and business value. Prioritization ensures that the most valuable features are addressed first and are delivered incrementally as part of the iterative development process. By prioritizing the new feature request, the practitioner aligns the development efforts with the project's overall objectives and ensures that the most critical requirements are addressed in a timely manner during the next work period.
upvoted 1 times
...
This section is not available anymore. Please use the main Exam Page.CAPM Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
JesseChou_123
2 weeks, 1 day agoJesseChou_123
1 month ago8a6d137
3 months ago