DPMM® Principles: Steering by Results Within Fixed Decision Points
What this domain tests
This domain tests whether you understand the principles behind DPMM® rather than the mechanics alone: result-oriented management, controlled dynamism, transparency, integral decision-making and clear responsibility. Questions ask which principle justifies a behaviour, or which behaviour violates the method’s principles.
Core rules
- Result-oriented: management steers on agreed results and acceptance criteria, not on hours spent or activity volume.
- Dynamic: the plan is a living instrument. Content, sequence and allocation may change, but only through the agreed decision structure - the method is adaptive, not unstructured.
- Decision-driven: fixed decision points (go/no-go moments) structure the project. Between them the project manager has freedom; at them, the owner or steering group decides.
- Transparency: risks, issues and changes are recorded in logs and reported without surprises. A problem known to the project manager but invisible to the owner breaks the principle.
- Integral: time, money, quality, scope, risk and capacity are weighed together; no single dimension is optimised at the expense of the others.
- Clear responsibility: one point of accountability per result, with delegation matched by mandate.
Worked example
A marketing team wants to add a second language to a website project four weeks before the launch decision. The project manager refuses to simply accept the work. Reasoning: the request is legitimate but must pass the change route. She assesses the impact on time, budget, quality and risk, records it in the change log, and presents options at the next decision point - extend the deadline, drop another feature, or defer the language to a follow-up release. The principle at stake is dynamic planning within fixed decisions: the project adapts, but the owner decides the trade-off, not the project manager alone.
Traps that cost marks
- Reading “dynamic” as “no plan” or “change anything at any time”.
- Letting the project manager accept scope changes silently to keep the client happy.
- Reporting only progress on activities, never on results and risks.
- Optimising one dimension, for example cutting cost while quietly lowering quality standards.