EA governance supports the optimal implementation of the national methodology, through the involvement of the governance committee and the application of governance procedures throughout the development cycle and digital initiative execution.
The governance committee responsible for enterprise architecture may need to be involved in executing stages of the development cycle in the following cases:
When there is a significant divergence in the entity's strategic directions or new requirements that require approval from top management.
When there are directions that significantly impact the entity's business model or the need to allocate budgets for IT investments.
Approving projects and the estimated costs for the enterprise architecture development roadmap.
| Review result | Action |
|---|---|
| Project outputs align with requirements | No corrective actions required; only the requirement status is updated. |
| Slight variance between outputs and requirements | The procedure for managing temporary exemptions for non-compliance is applied, and the requirement is updated with an exception statement. |
| Project outputs do not align with requirements | The EA team studies the reasons for non-compliance and takes appropriate action: either rejecting the modification or updating the requirement based on valid justification. |
The EA team must apply EA governance procedures when reviewing the list of current and scheduled initiatives/projects and decide whether to adjust their scope to maximise benefit for the entity.
Enterprise architecture requirements management is linked to the EA governance procedures in the entity, so it is important to consider them when implementing the requirements management steps. For more details on the governance model and committee structure, refer to the Guideline for EA Establishment for Government Entities.
