AGILEPM-PRACTITIONER · Question #63
Answer the following questions about the DSDM Lifecycle. Decide if each observation is an appropriate application of Agile Project Management for this project and select the option that supports…
The correct answer is A. Yes, because the later parts of the project should reflect the least valuable features. Option A is correct because DSDM uses MoSCoW prioritization (Must have, Should have, Could have, Won't have) to ensure the most valuable features are built first. By saving the least valuable features for last, the project protects its core deliverable - if time or budget runs…
Question
Answer the following questions about the DSDM Lifecycle. Decide if each observation is an appropriate application of Agile Project Management for this project and select the option that supports your decision. When the project was in the Feasibility phase it was initially proposed by the Finance Manager that it was a fixed price for a fixed specification' project. The Project Manager has decided that the best way to tackle it would be to leave the development of the least valuable features of the product until last. Is this an appropriate application of the DSDM lifecycle?
Options
- AYes, because the later parts of the project should reflect the least valuable features
- BYes, because in a DSDM project there is no detailed specification upfront.
- CNo, because the Solution Development Team should decide which features are left
- DNo, because the most valuable features of the project should be delivered last.
How the community answered
(43 responses)- A81% (35)
- B9% (4)
- C7% (3)
- D2% (1)
Explanation
Option A is correct because DSDM uses MoSCoW prioritization (Must have, Should have, Could have, Won't have) to ensure the most valuable features are built first. By saving the least valuable features for last, the project protects its core deliverable - if time or budget runs short, only low-priority features are at risk of being cut, which is exactly how DSDM manages scope under fixed time/cost constraints.
B is wrong because the absence of a detailed upfront specification is a true DSDM principle, but it is not the reason for sequencing features by value - that reasoning belongs to MoSCoW prioritization, not specification style.
C is wrong because feature prioritization in DSDM is driven by business value and is a business-level decision (led by the Business Sponsor/Visionary), not something delegated solely to the Solution Development Team.
D is wrong because it directly inverts DSDM practice - delivering the most valuable features last would mean that a late-running project has wasted time on low-priority work while failing to deliver core business value.
Memory tip: Think of DSDM as packing a lifeboat - load the most valuable items first. If the boat fills up early (time/budget runs out), you've still saved what matters most. Least valuable = loaded last, first to be left behind.
Topics
Community Discussion
No community discussion yet for this question.