Back to Guides

Change and exception governance

Governance procedures for managing changes to approved EA documents and outputs: accuracy, quality, and visibility of impact on the entity digital landscape. Manage development and updates to architectures, designs, and EA outputs in a controlled way.

Properly manage development and updates to architectures, designs, and EA outputs.

In brief

3
main objectives
4
inputs

Manage development and updates to architectures, designs, and EA outputs in a controlled way.

Reduce risk from change on the digital landscape and support flexible execution.

Inputs: EA tasks, services, organisational structure, interaction model.

Objectives of change and exception governance and DT roadmap

1

Proper management of development and updates to architectures, designs, and EA outputs.

2

Align impact of changes and reduce risk to the entity digital landscape.

3

Build and implement architectures in a flexible way that keeps pace with rapid change.

Steps to follow

1

Review required inputs
Review tasks, services, and the interaction model to define the nature of change in EA documents and outputs; review the organisational structure to identify roles and responsibilities needed to activate change and exception procedures.

2

Identify stakeholders
Identify stakeholders involved in executing change and exception requests and digital transformation roadmap governance, based on the input review.

3

Develop work procedures
Develop work procedures for change and exception requests and for digital transformation roadmap governance; build procedure flowcharts, activity descriptions, identification cards, and request forms for each procedure.

Inputs and outputs

Process inputs

  • EA tasks: tasks assigned to the team and context (internal or requested by a beneficiary).
  • EA services: approved services and practice scope.
  • EA organisational structure: roles, responsibilities, required experience, job descriptions, and reporting lines.
  • EA interaction model: the entity-approved model that describes how the practice interacts and collaborates with stakeholders inside and outside the entity.

Expected outputs

List of change and exception procedures and digital transformation roadmap governance procedures; procedure flowcharts; identification cards; activity descriptions; request forms per procedure.

Outputs in detail

1

List of change and exception procedures and digital transformation roadmap governance procedures

2

Procedure flowcharts for each procedure in the list

3

Identification cards for each procedure

4

Activity descriptions for each procedure

5

Request forms for each procedure

Sample list of work procedures (17 procedures)

Procedures are grouped by governance area: strategic alignment and change management, risk management, conflict and escalation, EA practice performance.

1

Strategic alignment management

2

Assess and analyse impact of strategic changes

3

Build and review DT roadmap initiatives and projects

4

Review digital strategies

5

Review terms and specifications for digital projects

6

Develop terms and specifications for EA initiatives and projects

7

Change request for EA documents and outputs

8

Review project design phase

9

Evaluate technical proposals from bidders

10

Verify proof-of-concept design for emerging technologies

11

Ensure alignment with target digital landscape

12

Review compliance with national architectural regulations

13

Verify compliance of architectures and designs

14

Manage temporary exemptions for non-compliance

15

Manage documentation and updates to EA components

16

Monitor EA team performance

17

Improve KPIs based on stakeholder feedback

Change and exception governance procedure models are issued under advisory support to raise EA practice maturity under NORA. Entities use them to control updates to approved EA documents and outputs.