Scope, requirements, quality and realising value
The Delivery Performance Domain addresses the activities and functions associated with delivering the scope and quality that the project was undertaken to achieve. It is where value is converted from plan to reality.
Three core concerns: requirements (what the deliverable must do), scope definition (what work will produce it), and quality (does it meet the acceptance criteria and fitness for purpose). Quality is built into the work — it is not an inspection step at the end. The cost of correcting defects increases exponentially the later they are found.
Requirements are elicited through interviews, workshops, observation, prototypes, surveys, and document analysis. They must be unambiguous, testable, traceable, and prioritised (e.g. MoSCoW). Scope statements, WBS (Work Breakdown Structure), and PBS (Product Breakdown Structure) make scope explicit.
Value is delivered through outputs (what you build), outcomes (the change they enable), and benefits (the measurable improvements). The Delivery domain is responsible for outputs; the wider organisation realises the benefits — but the project team should design for benefit realisation from day one.
Desired outcomes: the project delivers agreed scope and quality on time; deliverables enable intended outcomes and benefits.