Why DSDM

In most projects, time and budget are set — the scope is not. DSDM therefore turns the usual equation around: date and cost stay fixed, requirements are delivered by priority. Whatever fits into a timebox is built; whatever does not is moved visibly — never silently.

I work within the AgilePM framework, in client projects as well as in my own products. My project cockpit Krelora grew out of exactly this work.

The phases

From pre-project to post-project — every phase with a clear result.

  1. Pre-project

    Goal and scope

    Record the goal, scope and contacts — one page, not a binder.

  2. Feasibility

    Checkpoints instead of gut feeling

    Settle the risky questions first: technology, data, operations, cost.

  3. Foundations

    Requirements by MoSCoW

    Prioritised requirements, architecture, wireframes and a plan made of timeboxes.

  4. Development in timeboxes

    2 to 4 weeks per timebox

    Every timebox ends with working software and a report. Must requirements make up at most 60 per cent — the rest is buffer.

  5. Deployment

    Testing first, then production

    First to a test environment, after your approval to production — with a backup and a way back.

  6. Post-project

    Check the benefit

    After a few weeks we check together whether the expected benefit has materialised.

What you get

  1. Living documentation

    Requirements, decisions and reports in the repository — updated with every commit, as PDF for your records.

  2. Decisions with reasons

    Every decision is recorded with date, options and reason. Two years from now, you still know why.

  3. Wireframes before every timebox

    You see every screen before it is built and can still change it cheaply.

  4. Honest priorities

    MoSCoW with at most 60 per cent Must. When time gets tight, a Could goes — not the quality.

Frequent questions

Does my team need to know DSDM?

No. I explain the few rules at the start; after that, two meetings per timebox matter most: planning and acceptance.

Do you also lead projects without developing them?

Yes — for software projects where I can judge the technology and the effort.

How do I see the progress?

At the end of every timebox in the browser and in the report; in between in the repository and — if you like — in the Krelora project cockpit.

A project that needs to be predictable?

Let us find out which scope fits your deadline.

Discuss a project