Enterprise Architecture Governance backs the correct implementation of the national methodology. The committee responsible for EA governance takes part in specific situations during the development cycle, and governance procedures are applied when digital initiatives and projects are delivered, so their outputs stay aligned with the EA requirements.
Role of governance in the methodology
In brief
The National Enterprise Architecture Methodology rests on Enterprise Architecture Governance, which keeps its application correct and consistent.
The committee responsible for EA governance is brought in for specific situations during the development cycle.
EA governance procedures are applied when digital initiatives and projects are delivered, so their outputs stay aligned with the target EA components.
The full governance model and committee structure are set out in the Guideline for Establishing the EA Practice in Government Entities.
National Enterprise Architecture Methodology
The framework EA practice rests on inside the entity, run through seven integrated stages.
Enterprise Architecture Governance
Runs across the methodology stages, controlling decisions and when the responsible committee gets involved.
Organisational unit responsible
The organisational unit responsible for enterprise architecture inside the entity, within the approved governance model.
When the EA governance committee gets involved
The committee responsible for EA governance takes part in the EA component development cycle in the following cases:
01
Approving the scope of the EA component development cycle
When there is a significant shift in the entity's strategic directions, or new requirements that need top management approval.
02
Approving the future strategic directions for EA components
When directions clearly affect the entity's business model, or budgets need to be allocated for IT investment.
03
Approving roadmap projects and estimated costs
Approving the projects of the EA development roadmap together with their estimated costs.
Governance procedures during the implementation of digital initiatives and projects
EA governance procedures in the "digital project implementation" domain confirm that initiatives and projects stay aligned with EA principles and with the target EA components. A review ends with one of the following outcomes:
Outcomes of applying governance procedures to project outputs
Review outcome
Action
Project outputs align with the requirements
No corrective action is needed for EA requirements management. Only the requirement status is updated.
Slight variance between project outputs and the requirements
The procedure for "Managing Temporary Exemptions for Non-Compliance with Defined Standards" is applied to grant an exception or exemption. The requirement and its status are updated with a note that records the exception or exemption.
Project outputs do not align with the requirements
The EA team studies the reasons for non-compliance. The outcome is either to reject the modification when no valid justification exists, or to update the requirement and its status on the basis of a valid justification (for example, a specific technology cannot be used because of national laws or standards).
The EA team applies EA governance procedures when reviewing the list of current and scheduled projects, and makes the scope adjustments that deliver the most value to the entity.
Key takeaway
Key takeaway
EA requirements management is directly linked to the EA governance procedures inside the entity, and those procedures must be taken into account when running the requirements management steps. For the full governance model and the structure of the committee responsible for EA governance, refer to the Guideline for Establishing the EA Practice in Government Entities.
