Selecting an implementation method is the final action before completing the design of an IT governance system. An IT governance system is a set of components that provide direction, oversight, evaluation, monitoring, assurance, etc., for an enterprise’s information and technology. The design of an IT governance system involves several steps or actions that help to customize and tailor the system to the specific needs and context of the enterprise. These steps or actions include defining design factors, defining focus areas, defining current state, defining target state, identifying gaps and improvement opportunities, defining roadmap and priorities, etc. Selecting an implementation method is the final action before completing the design of an IT governance system because it helps to determine how the system will be put into practice, what resources and activities are needed, what challenges and risks are expected, etc.12 References: COBIT 2019 Framework:
Introduction and Methodology, COBIT 2019 Design Guide: Designing an Information and Technology Governance Solution

Communicating the results and benefits of an EGIT program plan in business impact terms is essential for an enterprise to be able to show and prove the benefits realized from the implementation. This includes providing clear evidence of how the program plan has created value, such as increased efficiency, cost savings, and improved customer satisfaction. Additionally, it is important to ensure that the results and benefits are communicated to all relevant stakeholders to ensure that they are aware of the value created.

Explanation
The IT governance implementation approach that should be utilized in order to achieve maximum enterprise benefits is treating implementation as a program. A program is a coordinated set of projects and activities that are designed to achieve a specific set of objectives within a defined scope, time frame, and budget. Treating implementation as a program helps to ensure that IT governance is planned, executed, monitored, controlled, and evaluated in a systematic and consistent manner, following best practices and standards. The approach is based on the COBIT 2019 Implementation Guide5, page 29. 5: COBIT 2019 Implementation Guide | Digital | English

The risk profile is a design factor that describes how an enterprise identifies, assesses, responds to, monitors, and reports on information and technology risks. The risk profile helps to determine the level of risk appetite and tolerance that an enterprise has for its information and technology activities, as well as the level of control and assurance that is required for its governance framework. When tailoring COBIT 2019 to enterprise requirements, the primary objective of preparing a risk profile is to identify areas of risk that exceed risk appetite. The risk appetite is the amount and type of risk that an enterprise is willing to accept in pursuit of its objectives. The risk appetite provides a basis for defining the risk criteria, thresholds, indicators, and responses that will be used in the risk profile process. By identifying areas of risk that exceed risk appetite, an enterprise can prioritize its governance objectives, processes, practices, roles, structures, and metrics according to the level of risk exposure and impact. This will also help to align the governance framework with the enterprise’s strategy and objectives.References: : COBIT 2019 Design Guide: page 41-43 : COBIT 2019 Framework: Introduction and Methodology: page 28-29

Explanation
COBIT guidance should be customized to meet specific enterprise needs, as different enterprises have different goals, objectives, risks, and requirements. COBIT provides a flexible and adaptable framework that can be tailored to suit the enterprise’s context and environment. COBIT also provides guidance on how to customize the framework using design factors and focus areas.12 References: COBIT 2019 Framework:
Introduction and Methodology, COBIT 2019 Design Guide: Designing an Information and Technology Governance Solution

According to the Official COBIT 2019 Study Manual from Isaca, the Program Management functional task area is responsible for assessing the potential return on investment (ROI) during future state planning. This includes creating a business case, assessing the economic benefits and costs associated with the project, and developing a roadmap for implementation. Program management also involves ensuring that the project is aligned with the organization’s strategic goals and objectives, as well as assessing risks and developing mitigation plans.

IT-related issues should be considered as part of the design factors for a governance system in order to manage risks that have a high impact. Design factors are the characteristics of the enterprise that influence the design and operation of a governance system, such as size, industry, culture, strategy, etc. IT-related issues are one of the 11 design factors defined in COBIT 2019, and they refer to the specific challenges or opportunities that arise from the use of information and technology in the enterprise, such as cybersecurity, digital transformation, innovation, etc. These issues may pose significant risks to the enterprise’s objectives, performance, or reputation, and therefore need to be addressed by the governance system. The answer is based on the COBIT 2019 Design Guide1, page 15. References: 1: COBIT 2019 Design Guide | Digital | English.

Explanation
The final step in governance system design is to define target capability levels for the most critical objectives.
The governance system design is the process of designing and implementing a governance system for an enterprise using COBIT 2019. The governance system design involves tailoring the COBIT 2019 components such as principles, enablers, goals, processes, practices, roles, structures, metrics, etc., according to the enterprise’s context and needs. The governance system design also involves considering various design factors such as enterprise strategy archetype; enterprise goals; IT-related goals; risk profile; IT deployment; threat landscape; compliance requirement; operating environment; size of enterprise; culture; stakeholders; etc., that influence how an enterprise designs and implements its governance system using COBIT 2019. The final step in governance system design is to define target capability levels for the most critical objectives. The capability levels are a measure of how well an enterprise performs its information and technology governance and management processes in terms of process attributes such as process performance, process definition, process deployment, process measurement, process control, process optimization, etc. The capability levels range from
0 (incomplete) to 5 (optimizing), indicating the degree of maturity and effectiveness of an enterprise’s information and technology governance and management processes. The critical objectives are the governance and management objectives that have been prioritized based on the design factors and the stakeholder needs.
The governance and management objectives are the statements of what an enterprise wants to achieve in terms of its information and technology governance. The governance and management objectives are derived from the enterprise goals, which are the high-level statements of what an enterprise wants to achieve in terms of its mission, vision, values, strategy, etc. By defining target capability levels for the most critical objectives as the final step in governance system design, an enterprise can ensure that it has set realistic and achievable goals for its information and technology governance and management processes that support its strategy and objectives. This will also help to identify the gaps or issues that need to be addressed to enhance the capability levels of the selected processes.References: : COBIT 2019 Design Guide: page 53-54 : COBIT 2019 Process Assessment Model: page 11-13

A business case outline is a key input to be considered when defining drivers for a COBIT implementation, as it outlines the business need for the initiative and provides a clear understanding of the benefits that the initiative is expected to deliver. The business case outline can then be used to help identify the drivers for the initiative and determine the urgency for change.

Explanation
According to the COBIT 2019 Framework: Governance and Management Objectives, one of the good practices with regard to performance management of organizational structures is to ensure that organizational meeting reports/minutes are available and meaningful to ensure transparency. This means that the outcomes and decisions of the meetings are documented and communicated to relevant stakeholders in a timely manner, and that they provide sufficient information to support accountability and learning. Transparency is one of the key principles of effective governance of enterprise I&T.4, p. 32-33 4: COBIT 2019 Framework:
Governance and Management Objectives

Explanation
Ensuring the program team knows and understands the enterprise goals is a part of the “Where do we want to be?” phase of the implementation. The implementation of a governance system is divided into seven phases, each with a set of activities and outputs. The “Where do we want to be?” phase involves defining the desired outcomes and target state of the governance system, based on the enterprise’s vision, mission, values, and goals. One of the activities in this phase is to ensure that the program team is aware of and aligned with the enterprise goals, as well as their roles and responsibilities in achieving them. The answer is based on the COBIT 2019 Implementation Guide2, page 34. References: 2: COBIT 2019 Implementation Guide | Digital | English

Explanation
Processes are key components of a governance system. Processes are the structured sets of activities that produce outputs or outcomes for achieving specific objectives. Processes define what needs to be done, by whom, when, how, and why. Processes are one of the seven enablers of a governance system, as defined by COBIT.12 References: COBIT 2019 Framework: Introduction and Methodology, COBIT 2019 Framework:
Governance System

Stakeholder drivers and needs must be defined before determining alignment goals. Stakeholder drivers and needs are the requirements or expectations of the internal or external stakeholders of the enterprise, such as customers, employees, shareholders, regulators, etc. Alignment goals are the intermediate goals that link the enterprise goals with the governance and management objectives. Alignment goals are derived from the stakeholder drivers and needs, and they reflect how information and technology can support the enterprise strategy and objectives. Therefore, stakeholder drivers and needs must be defined before alignment goals can be determined.12 References: COBIT 2019 Framework: Introduction and Methodology, COBIT 2019 Framework: Governance System