Phase G (Implementation Governance) ensures that what gets built actually conforms to the approved architecture. It is NOT about managing implementation projects — that is the PMO's job. Phase G is about architecture conformance: issuing Architecture Contracts and conducting Compliance Reviews.
Phase G runs DURING the implementation projects defined in Phase F. Architects perform a governance role — checking that implementation conforms to the Architecture Definition Document.
- ▸📝 Issues Architecture Contracts to implementation teams
- ▸🔍 Conducts Architecture Compliance Reviews at defined checkpoints
- ▸✅ Identifies conformance issues and escalates them
- ▸📋 Grants Dispensations for formally approved deviations
- ▸🔄 Handles Architecture Change Requests from implementation teams
- ▸📊 Produces Conformance Reports and updates Architecture Repository
- ▸🔗 Interfaces with Phase H if changes exceed scope of dispensation
Explore the Architecture Contracts CDIPD issued for each implementation project, and see the Architecture Compliance Review checklist:
- ▸ Managing implementation projects
- ▸ Writing code or building systems
- ▸ Project planning or scheduling
- ▸ Architecture conformance checks
- ▸ Architecture Contracts
- ▸ Handling change requests
The Architecture Contract is signed in Phase G (NOT Phase A or Phase F). Phase G governs CONFORMANCE — it does not manage the project itself. If an implementation team wants to deviate from architecture, they must request a Dispensation from the Architecture Board. Phase G issues Architecture Contracts and conducts Compliance Reviews — it does NOT manage the implementation project (that's the PMO's job).
The Architecture Contract is the formal agreement between the architecture team and the implementing teams. It specifies what the implementation must conform to.
- ▸📄 Defines: architecture standards, constraints, and conformance criteria the implementation must meet
- ▸✍️ Signed by: the Architecture Team (grantor) and the Implementation Team (implementer)
- ▸🔑 Signed in Phase G — NOT in Phase A or Phase F
- ▸⚠️ Exam trap: "When is the Architecture Contract signed?" = Phase G
- ▸📌 Contents: approved standards, allowed technologies, compliance review schedule, dispensation process
- ▸🔒 Once signed: any deviation requires a formal Dispensation request
A Dispensation is a formal, Architecture Board-approved departure from the agreed architecture. It is NOT a failure — it is a controlled change.
- ▸📝 When: an implementation team identifies they cannot meet an architecture constraint
- ▸🔄 Process: raise Architecture Change Request → Architecture Board reviews → Approve/Reject dispensation
- ▸📋 If approved: the dispensation is documented with rationale and impact assessment
- ▸🏛️ Authority: Architecture Board must approve all dispensations
- ▸⚠️ Exam distinction: Dispensation = APPROVED deviation. Unapproved deviation = architecture non-conformance.
- ▸📌 Example: PayFlask team requests dispensation to use Redis (not in approved list) for idempotency cache — Architecture Board approves with conditions