The Dynamic Systems Development Method, usually shortened to DSDM, is an agile framework for delivering projects on a fixed deadline and budget. Instead of locking down every feature first and hoping the timeline holds, DSDM fixes time, cost and quality up front, then flexes the scope so the most important things always get finished. It dates back to 1994, which makes it older than the 2001 Agile Manifesto it now sits alongside.
Picture planning a wedding with a hard date and a set budget. You can’t move either, so you decide what truly matters (the venue and the food) and treat the chocolate fountain as a nice-to-have you’ll drop if money gets tight. DSDM works the same way through its MoSCoW priorities: Must, Should, Could and Won’t. It sits within the wider agile family and leans on short, repeated cycles to keep the business and the developers in step.
To keep that promise honest, DSDM caps the Must-haves at around 60 percent of the effort, leaving slack in the timebox so a surprise doesn’t blow the deadline. The Could-haves act as a buffer that quietly drops away when things run tight.
What sets DSDM apart is how seriously it takes the business side: it names clear roles, expects active user involvement, and never trades away quality to hit a date. The flip side is overhead, so for a tiny two-person build the full framework can feel heavier than the work itself.
At TopDevs we borrow the most useful parts of DSDM, fixed deadlines with prioritised scope, so a client always gets a working result on time rather than a half-finished wishlist.
