AgilePM Principles and Philosophy

The 8 AgilePM principles are the underlying beliefs that drive all DSDM practices. They are not prescriptive rules but guiding philosophies that explain why DSDM works as it does. Understanding these principles deeply is more important than memorising them — they explain the rationale behind all DSDM techniques and practices.

The most important principle distinction is that AgilePM fixes time and resources but varies scope. This is the inverse of traditional project management which typically fixes scope and allows time/cost to flex.

Key Points

• Time and cost are fixed; scope is the variable — opposite of traditional PM
• MoSCoW prioritisation determines what gets delivered within the timebox
• Must have features must be less than 60% of available effort (to give room for Should/Could)
• 'Never compromise quality' — quality requirements are agreed upfront and are not negotiable
• Firm foundations are built before evolutionary development begins
• Iterative development means revisiting and refining — not just adding features
• Demonstrate control to stakeholders — governance remains essential in agile
• Business involvement is not optional — collaboration is a principle

Key Terms & Definitions

MoSCoW

A prioritisation technique: Must have (M), Should have (S), Could have (C), Won't have this time (W). Used to decide what is delivered within a timebox.

Timebox

A fixed period of time within which work is carried out. At the end of a timebox, the team delivers what has been completed — the timebox does not move.

Minimum Usable SubseT (MUST)

The minimum set of features that must be delivered for the solution to be considered viable.

Evolutionary Development

The AgilePM lifecycle phase during which the solution is built iteratively in timeboxes.

Increment

A portion of the project deliverable produced during a timebox.