Dynamic Project Management Method - Project Manager
Domain: Dynamic Project Management Method - Project Manager
The exam tests whether you can apply DSDM's agile project-management mindset: fixed time and cost, variable scope, empowered teams, and control through principles, roles, products and timeboxes. For the Project Manager role, the focus is on project-level planning, governance, risk, stakeholder communication and protecting the timebox - not command-and-control task assignment.
Core rules and concepts
- Eight principles are mandatory: focus on the business need; deliver on time; collaborate; never compromise quality; build incrementally from firm foundations; develop iteratively; communicate continuously and clearly; demonstrate control.
- Lifecycle: Pre-Project, Feasibility, Foundations, Evolutionary Development, Deployment, Post-Project. Feasibility checks viability; Foundations establishes firm foundations (Vision, Prioritised Requirements List, Solution Architecture Definition, Delivery Plan).
- Roles: Business Sponsor (funding/decisions), Business Visionary (business direction), Technical Coordinator (technical coherence), Project Manager (delivery management), Team Leader (day-to-day team). The Project Manager manages the project, not the solution detail.
- MoSCoW: Must have, Should have, Could have, Won't have this time. Musts are the minimum usable subset; if Musts exceed capacity, the project is not viable.
- Timeboxing: fixed duration and effort; scope varies. A timebox is never extended; low-priority content is removed to protect the deadline.
Worked example
A regulatory project has a fixed six-month deadline. The Project Manager facilitates Foundations, ensuring a Vision, Prioritised Requirements List, Solution Architecture Definition and Delivery Plan exist before development. Evolutionary Development is planned as three timeboxes. In timebox 2, a Must-have integration is late. The Project Manager does not extend the timebox. They escalate to the Business Sponsor and Business Visionary with options: drop a Could-have, simplify a Should-have, or stop the project. The Business Sponsor removes a Could-have. The timebox closes on time and the Must-have is completed. Reasoning: DSDM fixes time and cost, so scope must flex; the Project Manager's control is demonstrated by transparent escalation and protected timeboxes.
Traps that cost marks
- Treating the Project Manager as the scope owner. Scope trade-offs belong to the Business Sponsor/Visionary.
- Calling every requirement a Must-have; this destroys prioritisation and makes timeboxing impossible.
- Skipping Foundations and starting build early; DSDM requires firm foundations, not detailed design.
- Confusing Project Manager with Team Leader: the Team Leader runs the Solution Development Team day to day.
- Assuming DSDM means no documentation or control; products and demonstrate control are explicit.
- Extending a timebox to finish work; DSDM protects the timebox and flexes scope.