Back to Guides

Building EA unit tasks

DGA guideline for building the tasks of the organisational unit that activates EA practice: description of tasks, why defining them matters, inputs, four steps, and expected outputs. Tasks are classified as core or supporting.

DGA guideline for building the tasks of the organisational unit that activates EA practice.

In brief

2
inputs
4
steps
1
main output

Unit tasks are the work assigned to the team to support the practice in line with strategic directions and stakeholder expectations.

Tasks are split into core (main activities linked to practice objectives) and supporting (activities that enable delivery of core tasks).

Inputs: EA strategic directions and the entity’s organisational structure and task manual. Output: list and details of EA practice tasks.

Description of EA unit tasks

EA unit tasks are the work assigned to the team in the entity to support EA practice in line with the defined strategic directions, stakeholder expectations, and business requirements from the practice as a whole. Tasks can be divided into core tasks and supporting tasks.

Why defining EA unit tasks matters

1

Define the role and scope of EA practice in the entity from an organisational perspective, so that all efforts by the team align with the tasks assigned to other organisational units.

2

Plan and allocate resources effectively to activate EA practice, which helps define job roles, services, and how the practice is applied in the entity.

Inputs / organisational data sources

EA strategic directions

Strategic objectives and focus areas for the next phase of activating EA practice, as set out in the EA strategy.

Entity organisational structure

The entity’s task manual to understand tasks assigned to other organisational units and to identify overlap and similar tasks so that duplication of tasks and responsibilities is avoided.

Steps to follow

1

Analyse the entity’s organisational structure

Understand current entity tasks and capabilities: the team reviews the entity’s current task manual and identifies tasks related to EA practice domains (business, beneficiary experience, applications, data, technology, and security architecture). For example, the entity’s IT unit may perform some EA-related tasks; such potential overlaps must be taken into account and addressed when defining and documenting practice tasks.
2

Align with strategic directions

Tasks must support the strategic directions defined in the EA strategy. EA strategic directions give a clear picture of objectives and act as guiding principles for defining tasks. For example, if one strategic objective of EA practice is to support innovation and adoption of emerging technologies, one task should focus on fostering a culture of innovation, continuous improvement, and research.
3

Classify tasks by nature

Core tasks: Core tasks: main work activities directly linked to the objectives defined for EA practice; they include the core responsibilities for activating the expected role of the practice in the entity in line with objectives and expectations.

Supporting tasks: Supporting tasks: work activities that enable the team to deliver the defined core tasks; they include responsibilities for managing the internal work of the practice and ensuring it runs effectively.

4

Develop EA practice tasks

The team prepares a list of specific tasks and their details to define the role of EA practice and the context for activating the practice as a whole, in line with defined strategic objectives and existing tasks that overlap with EA. The nature of each task (core or supporting) is also defined.

Developing EA unit tasks requires review and approval by the entity’s HR unit and related organisational units for the defined tasks.

Expected outputs

List and details of EA practice tasks in the entity

The guideline includes a sample of EA practice tasks (example classification and details). Entities may use it as reference to build their own list.

The Digital Government Authority (DGA) issues the guideline for building EA unit tasks (version 1.0, 2024) under NORA.