Abstract
Deliverable review brings together contractual requirements, technical outputs, supporting records and approval. Completion tracking and authorisation to release need to be assessed separately.
Technical field. Delivery
Design considerations
- A deliverable register needs a defined relationship to scope requirements, revisions and responsible owners.
- Evidence completeness and technical acceptance require criteria appropriate to the deliverable.
- Release, recipient access and subsequent revisions require an explicit review and distribution process.
Questions for technical evaluation
- How are requirements, technical outputs and supporting records associated?
- Which checks and approvals are required before the proposed release action?
- How are released revisions, corrections and recipient access controlled?
Scope of this note
This note describes workflow design and evaluation considerations. Supported behaviour, interfaces, controls and limitations need to be demonstrated for the proposed product configuration and intended project.