Skip to main content

Enterprise Architecture Governance

Introduction

The Government of Rwanda under the leadership of RISA has undertaken to develop Enterprise Architecture Practice with the goal of establishing unified IT standards and practices across all public entities. The rationale behind this is the need for seamless and integrated IT solutions across government entities.

It is acknowledged that up until now, despite the close alignment of the services offered by different government entities, the respective IT functional units have applied different standards in developing and deploying solutions.

An assessment conducted in 2013 concluded that there is neither IT governance nor enterprise architecture in place within all public entities and by extension, there is practically no appropriate Enterprise Architecture Governance.

This scenario poses a challenge to the Government of Rwanda as it seeks to integrate IT solutions across all public entities.

In order to address this challenge, RISA has been tasked to drive the implementation of enterprise architecture practices that will ensure the application of unified IT standards across all entities.

To achieve this, there is a need to define an Enterprise Architecture Framework (EAF) as well as the governance model that will drive its implementation.

Rather than applying a leading framework in its entirety, the government of Rwanda has elected to adopt and modify The Open Group Architecture Framework (TOGAF) to suit the specific needs of Rwanda.

 

Depicted in Figure 20 below is the modified framework. The detailed description of the framework has been defined in the document titled ‘Government of Rwanda Enterprise.’

Architecture Framework (RGEA)’ which has also outlined the domains that enterprise architecture practice will cover.

image.png

The purpose of this document, therefore, is to outline the governance structures and roles that specific boards and committees will be entrusted with in ensuring adherence to set IT standards and practices.

Background

Management of an IT function is a complex undertaking. This is largely because IT encompasses a number of closely linked subdisciplines that need to be maintained in seamless alignment if the combined service offering is to deliver value to the target audience.

Success of the IT function therefore hinges on a number of interrelated activities, which are all coordinated through IT governance.

Within Government of Rwanda, IT governance should be taken both in the sense of provision of standards and policies for the entire ICT functional unit as well as governance around

Enterprise Architecture practice. This will be referred to as Enterprise Architecture Governance (EAG).

The primary purpose of Enterprise Architecture Governance is to ensure that an organization’s IT investments are closely aligned to business goals and processes, so that limited IT resources are allocated to areas of highest impact on organizational performance. While the overriding concern of EAG is the effectiveness of the IT investments, the EA program itself needs to be governed as well, since an incorrectly developed EA could adversely impact the IT investment decisions that are based on it. The EAG described in this document has three primary objectives:

  • Ensure that the EA program is properly managed and that it produces artifacts and plans that are truly representative of organizational goals and needs.
  • Ensure that the IT investment decisions are being continually aligned with the EA Office from the point they are initiated until implemented
  • Ensure that the IT decisions are made with consideration for integration goals of government Rwanda

To address these objectives, a well-defined Enterprise Architecture Governance Framework needs to be developed, agreed, communicated and implemented.

The following sections describe the proposed EA Governance Framework for each major component of the EA Program as well as the required governance bodies to ensure the implementation of the defined EAG framework.

EA Governance Implementation

The purpose of the EAG Framework is to provide policy guidance and advice and assistance in the definition, design, and implementation of Enterprise Architecture (EA) discipline and practice throughout the organization.

In addition, it serves as the core governance asset providing advocacy for EA integration of business and technology architectures across business units as well external boundaries.

The EAG establishes common terminology definitions and frameworks, including the Enterprise Architecture Framework and Technical Reference Models and Standards; and practical guidance to effectively implement and provide assurance for government of Rwanda technology solutions required to enable business requirements.

The Implementation of any EAG follows a number of steps. Typically, EAG requires formation of a number of governing bodies that share responsibility of overseeing operations of the IT functional unit.

These bodies are systematically arranged along the System Development Lifecycle (SDLC) to not only set and ensure adherence to set standards and principles but also to mitigate the risk of IT delivering a solution that may potentially be misaligned to the business requirements. Furthermore, the governance bodies vet and make recommendations on future IT investment plans.

The rationale behind having multiple governance bodies is to avoid a situation where a single body is entrusted with the responsibility of both making recommendation and approving the same. Best practice requires that there be multiple bodies that will validate each other’s decision.

Within the Government of Rwanda, however, it has been noted that the IT functional units are relatively small. In the majority of cases, the IT team is composed of less than ten (10) FTEs.

This scenario makes it impossible to create multiple IT governance bodies in such organizations.

It is, however, still imperative that EA governance be instituted in all public entities. It is noted that all public entities have and IT committee whose terms of reference include making decisions for IT investment and operational enhancements.

It is proposed that the terms of reference for such a committee should be extended to includenterprise architecture governance.e. In this regard, the IT committee should also have the responsibility of ensuring adherence to set standards and application of EA policies.

If, however, this IT Committee is to be the only body responsible for making decision affecting an entity, governance would be a failure in principle for the following reasons:

  1. The IT Committee’s decisions need to be vetted by another independent body
  2. The government of Rwanda’s goal of bringing integration between public entities will need to be driven by a common goal across all public entities and therefore needs another body outside each of the entities to validate the decisions that would impact the integration

Since all the entities are organized in Sectors, it is therefore recommended that the IT committees for each entity be aligned to their respective Sectors. At central level, three additional decision making bodies will serve as escalation points for institutions’ IT committees and Sector Working Groups. These are:

  • RISA Team
  •  GoR Digitization Advisory Committee
  • National ICT steering committee.

Described below is the proposed relationship:

  1. The IT Committee will be responsible for making IT decisions for the respective public entity. These decisions will include future investment plans, system enhancements, solution development, etc.
  2. Before the decisions are implemented, the IT Sector Working Group should be consulted. This is because the IT Sector Working Group would have a clear view of how each of the entities’ architecture fits in with the sector mandate. In order to ensure that there is no disruption to the integration plans, the IT Sector Working Group will be the custodian of the sector architecture models. As such, it would be in a better position to approve decisions that would not compromise the integrations across sector entities.
  3. In making its decision, the IT Sector Working Group will liaise with the RISA-EA Team. The RISA-EA Team is responsible for setting architecture standards and policies for all
  4. government entities. As such, it will vet decisions made by IT Sector Working Groups in line with the set standards,policies,s and architecture goals of the government.
  5. All major IT investment plans will be approved by the GoR Digitization Advisory Committee via the RISA-EA Team.
  6. All strategic orientations in connection to ICT cross-institutional projects fall under the responsibility of the National ICT steering committee, which is composed of GoR’s cabinet members.

The roles and compositions of each of the governance groups are depicted below.

image.png

GoR Digitization Advisory Committee

This is the top decision making body within Government of Rwanda regarding IT initiatives. The core of the Advisory Committee’s functional responsibility will rest on National ICT strategic projects approval, prioritization and monitoring in terms of cost and performance. It is therefore important to have the PS / Ministry of Finance as a permanent member of the GoR Digitization Advisory Committee to ensure alignment in terms of ICT projects financing.

The Advisory Committee receives recommendations from the RISA-EA Team on new projects and then advises on prioritization. It also reviews performances of projects as presented by the RISA-EA Team as well as provision of guidance for the Sector IT Working Group.

The ultimate role of the GoR Digitization Advisory Committee is to provide strategic direction to the IT function as well as ensuring that all ICT service delivery initiatives are aligned towards a common vision. In line with that and depending on matters being deliberated, the GoR’s Digitization Advisory committee might invite key ICT players from private sector to take part in the discussions on need basis. This would help capture views of the private sector and strengthen the Public and Private Partnership.

Described below is a summary of the GoR Digitization Advisory Committee roles and responsibilities:

 

Accountabilities

-       National ICT master plan approval

-       Strategic ICT projects approvals and prioritisation

-       National ICT project performance monitoring.

-       Guidance on major IT expenditures.

-       National ICT cost monitoring.

Suggested Composition

Permanent Secretary / MiTEC (Chair) Permanent Secretary/MINECOFIN CEO-RISA

GCINO  RISA GCIO – RISA COO - RDB DG – RURA DG-NIDA DG/ICT  OTP

Optional: Key Business Representatives to be invited on need basis.

Responsibilities

-      Advise on overall IT capital expenditure levels based upon merit of initiatives and overall financial constraints

Escalation

Escalation point for:

            RISA EA Team

            Sector IT Working Group

            IT Committee


 

 

 

-       Review IT performance metrics to track IT performance

-       Provide input into timing and scope of major IT initiatives.

-       Prioritisation of major initiatives

-       Provide approval of major IT initiatives

-       Review & approve National IT Strategy

-       Review and advise on expenditures for major initiatives or significant changes from plan

-       Review status of major initiatives and take action where appropriate

-       Review significant changes to IT standards, as recommended by the RISA EA team

 

Escalation to:

            National ICT steering committee

Frequency

Quarterly (and on need basis)

RISA EA Team

The RISA-EA Team is the custodian of architecture models and artefact for the entire Government of Rwanda. Its primary role is to set architecture principles and standards for all IT solutions. The EA Team should therefore, always be consulted when change is being considered in an environment. In this regard, when a business requirement is received for either developing, procuring a new solution or enhancements to an existing system, the requirements should be brought before this team for review.

In this role, the RISA-EA team is concerned with mapping the new business requirements to the current architecture landscape and ascertain on the impact that a new change would have across the government IT landscape. The role of the Team therefore transcends beyond setting standards for enterprise architecture. It also includes ensuring that the Government- wide architecture landscape is kept in line with the overall government initiatives.  Theseinitiatives include ensure application of common standards across all entities, maintaining the system alignment and integration among all Government entities, ensuring that investment plans are in line with overall government long term IT goals.

It is the RISA-EA Team that would approve the build’ or buy’ decisions. This is done after the business and functional requirements have been analyzed against the current IT solutions and investment planning. The assessment is done to ensure that the planned change is in alignment with the business requirement and IT capabilities.

As defined above, the RISA-EA Team should have powers assigned to a board i.e. powers to make decisions. This entails that it may reject or approve requests.

Furthermore, it will also play the role of an innovation board: thus, it should also fulfil an advisory role to IT and business on new innovations. In this regard, its actions should be proactive. Thus, the RISA –EA Team should always strive to bring innovative ways to enable business through provision of advice on trends in the technology field and also possible enhancements to current systems.

To ensure that the RISA-EA Team works well, it should be chaired by the Government Chief Innovation Officer (GCINO) or the Government Chief Information Officer (GCIO). The other members are the Enterprise Architecture Division Manager, the Digitization analyst, Information system security analyst, Business Process Re-Engineering Specialist, Data Architecture Specialist, Infrastructure Architecture Specialist, Systems integration senior engineer, Enterprise & application architecture specialist, Enterprise & application architecture analyst, Business intelligence and analysis specialist.

Summary of the composition and mandate is shown below:

Accountabilities

-       Enterprise Architecture direction across infrastructure, applications, processes and tools

-       Enterprise Architecture roadmaps across technologies

-       Identification of innovation in IT that can help the business and awareness of new technologies

Suggested Composition

-       Enterprise Architecture Division manager

-       Digitization analyst

-       Information system security analyst

-       Business Process Re- Engineering Specialist

-       Data Architecture Specialist

-       Infrastructure Architecture Specialist

-       Systems integration senior engineer

-       Enterprise & application architecture specialist

-       Enterprise & application architecture analyst

-       Business intelligence and analysis specialist.

Inputs

-       IT Strategy

-       IT Investment and operating plan(annual)

-       Project proposals

-       New technology developments in the marketplace

-       Learning / experiences

/ insights from other competitors/ industries/partners

Outputs

-       IT Strategy

-       IT Policy, Standards

-       EA framework and Architecture artefacts

-       IT Investment and operating plan(annual)

-       Project proposals

-       New technology developments in the marketplace

-       Learning / experiences / insights from other competitors/ industries/partners

Responsibilities

-       Review and recommend Enterprise Architecture vision & roadmap, to deliver corporate strategic objectives

-       Define Enterprise Architecture standards, policies, principles and guidelines

-       Assess new project proposals for

architectural compliance

Escalation

Escalation point for:

 

 

IT Sector Working Group

 

 

IT Committee

 

 

Escalation to:

 

 

GoR       Digitization             Advisory Committee

 

 

-       Facilitate collaboration across areas to exploit IT synergies and avoid duplication.

-       Bring learning / experiences / insights from other clients / industries to IT

-       Identify potential new business / IT opportunities and recommend new technologies and / or approaches

-       Work with business management / stakeholders to develop compelling business cases for new technologies

 

 

Frequency

Quarterly (and on need basis)