COBIT 2019

quick overview of COBIT 19

Get Started. It's Free
or sign up with your email address
COBIT 2019 by Mind Map: COBIT 2019

1. 7. How to keep the momentum gooing

2. 1. Introduction

2.1. EGIT - Enterprise Governance for I&T

2.1.1. Outcomes of adoption of EGIT

2.1.1.1. Benefits Realization

2.1.1.2. Risk Optimization

2.1.1.3. Resource Optimization

2.1.2. Distinction between Governance & Mgmt

2.1.2.1. Gov

2.1.2.1.1. Stakeholder needs, conditions and options are evaluated to determine balanced, agreed on Enterprise objectives

2.1.2.1.2. Sets direction, prioritization and decision making

2.1.2.1.3. Monitors performance and compliance against agreed objectives

2.1.2.2. Mgmt

2.1.2.2.1. Plan, buiild, run, monitor activities in alignment with the direction set by governance body to achieve enterprise objectives

3. 2. COBIT Principles

3.1. Distinction between Governance System and Gov Framework

3.1.1. Gov System

3.1.1.1. Is the system that helps govern I&T

3.1.1.2. Value creation from the use of I&T

3.1.1.3. Components should work in a holistic way

3.1.1.4. Should be dynamic - allow for changes

3.1.1.5. Distinguish Governance and management activities

3.1.1.6. Tailored to the enterprise's needs

3.1.2. Gov Framework

3.1.2.1. Used to create a Governance system

3.1.2.2. Based on a conceptual model

3.1.2.3. Should cover the enterprise end to end

3.1.2.4. Should be open and flexible

4. 3. Governance and Management Objectives

4.1. Consists of Process and Componenets

4.1.1. 40 Processes and 7 Components

4.2. Always relate to 1 process and a series of related components

4.3. Goverenance Objj relates to a Gov process. Mgmt Obj relates to a Mgmt process

4.3.1. Read through the GMOs for each Gov and Mgmt objectives from the guide - specifically pay attention to the focus areas of each

4.4. Gov Objectives - 5 : EDM - Evaluate, Direct, Monitor

4.5. Management Objectives - 35

4.5.1. APO (14 process) - Align, Plan and Organize

4.5.2. BAI (11) - Build, Acquire, Implement

4.5.3. DSS (6) - Deliver, Service and Support

4.5.4. MEA (4) - Monitor, Evaluate, Assess

4.6. Components

4.6.1. They satisfy governance, management objectives enterprises need to build systems

4.6.2. Components Interact with each other

4.6.3. 7 Components in all

4.6.3.1. PPOCISP (Poor Paul Ott Came In Second Place)

4.6.3.1.1. Process,

4.6.3.1.2. Procedures and Policies

4.6.3.1.3. Organization

4.6.3.1.4. Culture and Ethics

4.6.3.1.5. Information

4.6.3.1.6. Services, Infra and application

4.6.3.1.7. People

4.6.3.2. Components are factors that individually and collectively contribute to the good operations of the enterprises' Gov System over I&T

5. 4. Design Factors

5.1. 11 Design factors in all

5.2. Enterprise Strategy

5.2.1. They are further classified in to 4 balance score card dimensions

5.2.1.1. Financial, Customer, Internal, Growth

5.3. Enterprise Goals

5.3.1. 13 EGs - Read through them from the manual

5.4. A couple of questions around the balance socre card will be asked

5.5. Risk Profile

5.5.1. Talks about the current risk profile of the enterprise - there are 19 different risk areas

5.6. I&T Related Issues

5.6.1. Talks about the possibility of any risk area that has turned in to an issue - 20 different issue profiles

5.7. Threat landscape

5.7.1. Normal, High

5.8. Compliance Requirements

5.8.1. high, Normal, Low - Talks about external compliance requirements that the enterprise has to adhere to

5.9. Role of IT

5.9.1. One question will be asked on this

5.9.2. Support - IT not critical for biz continuity

5.9.3. Factory - Immediate impact on biz cont when IT fails

5.9.4. Turnaround - IT seen as a driver for innovation but no impact on RUN

5.9.5. Strategic - Important for both Innovation and RUn

5.10. Sourcing model for IT

5.10.1. Outsourcing, Cloud, Insourced, Hybrid

5.11. IT Implementation methods

5.11.1. Agile, DevOps, Traditional, Hybrid

5.12. Technology adoption strategy

5.12.1. First Mover, Follwer, Slow adopter

5.13. Enterprise Size

5.13.1. Large, Small, Medium

6. 5. Goals Cascade

6.1. Is used to align Stakeholder Needs to Enterprise Goals to Alignment Goals to GMOs

6.2. Alignment Goals - Read about them from the manual

7. 6. Performance Management

7.1. Cobit has its own performance management system (Cobit Per Mgmet) based on CMMI5

7.2. Each GMO and Component has a capability score

7.2.1. score are from 0 -5

7.2.1.1. 0 - lack of basic capability

7.2.1.2. 1 - Process more or less achieves results but through incomplete applicaiton of process

7.2.1.3. Should align to major relevant standards

7.2.1.4. 2 - Process achieves but through basic set of activities

7.2.1.5. 3 - Process achieves results through well defined set of activities

7.2.1.6. 4 - Process achieves results and they are measurable

7.2.1.7. 5 - COntinuous Improvements are driven through measurements and learnings

7.3. Each focus area (collection of GMOs / Components ) have a maturity score

7.3.1. The maturity score is same as the capability score if all the GMOs and components of the focus area have the same capability score

7.3.1.1. Maturity scores are same as capabilty socres

7.4. Measuring Subjective components

7.4.1. Some components such as Information, People, Culture cannot be measured objectively - they are measured subjectively. COBIT provides guidance on how they can be measured

8. 7 - Designing a tailored governance system

8.1. 3 factors impact design

8.1.1. Management Obj and priority

8.1.2. Specific focus areas

8.1.3. Component variations

8.2. Follows a 4 step process

8.2.1. 1. Understand enterprise context and strategy

8.2.2. 2. Determine initial scope of the governance system

8.2.3. 3. Refine the scope of the governance system

8.2.4. 4. Conclude the Gov System design

9. 8. Implementing Governance

9.1. 1. What are the drivers

9.2. 7 Stages of implementation

9.2.1. 2. Where are we now

9.2.2. 3. Where do we want to be

9.2.3. 4. What needs to be done

9.2.4. 5. How do we get there

9.2.5. 6. Did we get there

9.3. 3 rings of the roadmap

9.3.1. Program Roadmap (outermost ring)

9.3.2. Change enablement (Middle ring)

9.3.3. COntinous improvement (inner ring)

9.3.4. The seven stages are mapped to activities under each of these 3 rings

9.4. All the stages of 7 - Designing are mapped to the first 3 stages of implementation

10. 9. Business Case for Implementation

10.1. Business cases have the following sections

10.1.1. Executive Summary

10.1.2. Background

10.1.3. Business Challenges

10.1.4. Gap Analysis and Goal

10.1.5. Alternatives considered

10.1.6. Proposed SOlution