Van Grembergen PDF
Van Grembergen PDF
Van Grembergen PDF
www.uams.be/itag
Agenda
• Enterprise Governance of IT
2
Setting the scene
3
Setting the scene
4
IT governance definitions
5
Three layers
IT GOVERNANCE
strategic level
Board of
directors
Executive
management (CEO,
management level
CIO, …)
6
Moving to Enterprise Governance of IT
7
ISO 38.500 principles for Enterprise Governance of IT
• Principle 1: Responsibility
Individuals and groups within the organization understand and accept their
responsibilities in respect of both supply of, and demand for IT. Those with
responsibility for actions also have the authority to perform those actions.
• Principle 2: Strategy
The organization’s business strategy takes into account the current and future
capabilities of IT; the strategic plans for IT satisfy the current and ongoing needs of the
organization’s business strategy.
• Principle 3: Acquisition
IT acquisitions are made for valid reasons, on the basis of appropriate and ongoing
analysis, with clear and transparent decision making. There is appropriate balance
between benefits, opportunities, costs, and risks, in both the short term and the long
term.
• Principle 4: Performance
IT is fit for purpose in supporting the organization, providing the services, levels of
service and service quality required to meet current and future business requirements.
• Principle 5: Conformance
IT complies with all mandatory legislation and regulations. Policies and practices are
clearly defined, implemented and enforced.
• Principle 6: Human Behaviour
IT policies, practices and decisions demonstrate respect for Human Behaviour, including
8 the current and evolving needs of all the ‘people in the process’.
Key assets governance
Board
Executive committee
Key assets
Human Financial Physical IP Inform. & Relationsh
assets assets assets assets IT assets ip assets
9
IT Governance versus IT Management
(Peterson, 2003)
B us ine ss
O rie ntation
E xterna l
IT
G ov erna nce
overna nc e
Interna l
IT
M a na ge m ent
T im e
O rientation
P res ent Future
10
Structures, processes and relational mechanisms
Structures Processes
Roles and responsibilities, IT organisation Strategic Information Systems Planning, (IT)
structure, CIO on Board, IT strategy BSC, Information Economics, SLA, COBIT,
committee, IT steering committee(s) Val IT, ITIL, IT alignment / governance
maturity models
Enterprise governance of IT
Relational mechanisms
Active participation and collaboration between principle
stakeholders, Partnership rewards and incentives,
Business/IT co-location, Cross-functional business/IT
11 training and rotation
Structures: Roles & responsibilities
(Weill & Woodham)
B. monarchy
IT monarchy
Feodal
Federal
Duopoly
Anarchy
12
Structures: Principles for Enterprise
Governance of IT
13
Structures: IT strategy committee
(IT Governance Institute, 2002)
• a board may carry out its IT governance duties through an IT strategy committee
• the IT strategy committee needs to offer expertise and timely advice and direction
on topics such as:
• the alignment of IT with the business directions
• the achievement of strategic IT objectives
• the availability of suitable IT resources, skills and infrastructure
• optimization of IT costs
• the role and the value delivery of external IT sourcing
• risk, return and competitive aspects of IT investments
• progress on major IT projects
• measurement of IT performance
14
Structures: IT strategy committee
(IT Governance Institute, 2002)
•membership:
•chairman (board member)
•several board members
•IT experts as external advisors
15
Structures: IT strategy committee versus IT steering
committee (IT Governance Institute, 2002)
• an IT steering committee:
• assists the executive in the delivery of the IT strategy
• oversees day-to-day management of IT service delivery and IT projects
• focuses on implementation
16
Processes: Balanced Scorecard
(Van Grembergen et al., 2002; Van Der Zee and De Jong, 1999)
• the BSC, initially developed at enterprise level, can also be applied to IT and
through a cascade of business and IT scorecards integrated business and IT
management can be realized
• when using the BSC alignment method, business goals and the drivers
of business success are identified, including specific IT drivers (In this way,
IT can be integrated in the business).
• IT BSC is becoming a popular tool with its concepts widely supported and
and dispersed by consultant groups
17
Generic IT Balanced Scorecard
Corporate
Contribution
User Operational
Orientation Excellence
Future
Orientation
18
Corporate Contribution Scorecard
19
User Orientation Scorecard
20
Operational Excellence Scorecard
Employee Satisfaction Employee satisfaction survey scores in: North American technology
• compensation dependent companies
• work climate
• feedback
• personal growth
• vision and purpose
22
Cascade of scorecards
Business Objectives
23
IS Service Desk Unit Scorecard
THEN THEN
THEN IF
25
IT BSC maturity model
MATURITY LEVEL 1: There is evidence that the organization has recognized that there is a
need for a measurement system for its information technology division. There are ad hoc
approaches to measure IT with respect to the two main IT processes, i.e. operations and
systems development. This measurement process is often and individual effort in response
to specific issues.
MATURITY LEVEL 2: Management is aware of the concept of the IT balanced scorecard and
has communicated its intent to define appropriate measures. Measures are collected and
presented to management in a scorecard. Linkages between outcome measures and
performance drivers are generally defined but are not yet precise, documented or
integrated into strategic and operational planning processes. Processes for scorecard
training and review are informal and there is no compliance process in place.
MATURITY LEVEL 3: Management has standardized, documented and communicated the IT
BSC through formal training. The scorecard process has been structured and linked to
business planning cycle. The need for compliance has been communicated but compliance
is inconsistent. Management understands and accepts the need to integrate the IT BSC
within the alignment process of business and IT. Efforts are underway to change the
alignment process accordingly.
MATURITY LEVEL 4: The IT BSC is fully integrated into the strategic and operational planning
and review systems of the business and IT. Linkages between outcome measures and
performance drivers are systematically reviewed and revised based upon the analysis of
results. There is a full understanding of the issues at all levels of the organization that is
supported by formal training. Long term stretch targets and priorities for IT investment
projects are set and linked to the IT scorecard. A business scorecard and a cascade of IT
scorecards are in place and are communicated to all employees. Individual objectives of IT
employees are connected with the scorecards and incentive systems are linked to the IT
BSC measures. The compliance process is well established and levels of compliance are
high.
MATURITY LEVEL 5: The IT BSC is fully aligned with the business strategic management
framework and vision is frequently reviewed, updated and improved. Internal and external
experts are engaged to ensure industry best practices are developed and adopted. The
measurements and results are part of management reporting and are systematically acted
upon by senior and IT management. Monitoring self-assessment and communication are
pervasive within the organization and there is optimal use of technology to support
measurement, analysis, communication and training.
26
Processes: Information Economics
(Parker, M., 1996; Van Grembergen and Van Bruggen, 1997)
• this evaluation methods takes into account the ROI of a project and different
non-tangibles such as “strategic match of the project” (business evaluation)
and “match with the strategic IT architecture” (IT evaluation)
27
28
Processes: COBIT and VALIT as frameworks
for Enterprise Governance of IT
Enterprise Governance of IT
COBIT Val IT
Focus on IT processes - on IT related business processes
Foucs
Focus
29
PO1. define a strategic IT plan
Business and PO2. define the information architecture
Governance PO3. determine technological direction
COBIT Framework Objectives PO4. define the IT processes, organization and relationships
PO5. manage the IT investment
PO6.communicate management aims and direction
PO7. manage IT human resources
PO8. manage quality
PO9. assess and manage risk
INFORMATION PO10. manage projects
ME1. monitor and evaluate IT performance
ME2. monitor and evaluate internal control Criteria
ME3. ensure regulatory compliance •• effectiveness
effectiveness
•• efficiency
efficiency
ME4. provide IT governance •• confidentiality
confidentiality
•• integrity
integrity
•• availability
availability
•• compliance
compliance
•• reliability
reliability
31
COBIT Control
Objectives
Example: Detailed Control Objectives
for Manage Changes (AI6)
AI6.1 Change Standards and Procedures
Set up formal change management procedures to handle in a standardised manner all
requests (including maintenance and patches) for changes to applications, procedures,
processes, system and service parameters, and the underlying platforms.
33
COBIT - IT Control
Practices
DS8.1 Service Desk
Establish a service desk function, which is the user interface with IT, to register, communicate, dispatch
and analyse all calls, reported incidents, service requests and information demands. There should be
monitoring and escalation procedures based on agreed-upon service levels relative to the appropriate
SLA that allow classification and prioritisation of any reported issue as an incident, service request or
information request. Measure end users’ satisfaction with the quality of the service desk and IT services.
1. Establish a service desk as a single, initial point of contact for the reporting, monitoring, escalation
and resolution of customer requests and incidents. Develop business requirements for the service
desk, based on service definitions and SLAs, including hours of operation and expected response
time to a call. Ensure that service desk requirements include identifying staffing, tools and
integration with other processes, such as change management and problem management.
2. Ensure that there are clear instructions for service desk staff when a request cannot be immediately
resolved by service desk personnel. Establish time thresholds to determine when escalation should
occur based on the categorisation/prioritisation of the request or incident.
3. Implement the necessary support software and tools (e.g., incident management, knowledge
management, incident escalation systems, automated call monitoring) required for operation of the
service desk and configured in accordance with SLA requirements, to facilitate automated
prioritisation of incidents and rapid resolution.
4. Advise customers of the existence of the service desk and the standards of service they can expect.
Obtain user feedback on a regular basis to ensure customer satisfaction and confirm the
effectiveness of the service desk operation.
5. Using the service desk software, create service desk performance reports to enable performance
34
monitoring and continuous improvement of the service desk.
COBIT
Management Guidelines
Inputs –Outputs
35
Each process has primary inputs
and outputs with process linkages
Inputs
Outputs
Mission and Goals
Understanding of the Strategic Plan
business context,
capability and PO1 Tactical Plan
Project Portfolio
capacity
Business Strategy Service Portfolio
Risk Appetite
36
COBIT
Management Guideline
RACI Chart
37
RACI chart providing
roles and
CEO
responsibilities
CARS
Head of
Business Head of Chief Head of
IT Admin PMO
Sr Management Operations Architect or CTO Development
HR, Fin, etc
PO1
38
COBIT
Management Guideline
Goals and metrics
39
Example: Goals and metrics
for Manage Changes (AI6)
40
COBIT
Maturity models
41
Example: Maturity Model
for Manage Changes (AI6)
0 Non-existent when
There is no defined change management process and changes can be made with virtually no control. There is no awareness
that change can be disruptive for IT and business operations, and no awareness of the benefits of good change management.
1 Initial/ Ad Hoc when
It is recognised that changes should be managed and controlled. Practices vary and it is likely that unauthorised changes take
place. There is poor or non-existent documentation of change, and configuration documentation is incomplete and unreliable.
Errors are likely to occur together with interruptions to the production environment caused by poor change management.
2 Repeatable but Intuitive when
There is an informal change management process in place and most changes follow this approach; however, it is
unstructured, rudimentary and prone to error. Configuration documentation accuracy is inconsistent and only limited planning
and impact assessment takes place prior to a change.
3 Defined Process when
There is a defined formal change management process in place, including categorisation, prioritisation, emergency
procedures, change authorisation and release management, and compliance is emerging. Workarounds take place and
processes are often bypassed. Errors may still occur and unauthorised changes occasionally occur. The analysis of the impact
of IT changes on business operations is becoming formalised, to support planned rollouts of new applications and
technologies.
4 Managed and Measurable when
The change management process is well developed and consistently followed for all changes, and management is confident
that there are minimal exceptions. The process is efficient and effective, but relies on considerable manual procedures and
controls to ensure that quality is achieved. All changes are subject to thorough planning and impact assessment to minimise
the likelihood of post-production problems. An approval process for changes is in place. Change management documentation
is current and correct, with changes formally tracked. Configuration documentation is generally accurate. IT change
management planning and implementation are becoming more integrated with changes in the business processes, to ensure
that training, organisational changes and business continuity issues are addressed. There is increased co-ordination between
IT change management and business process redesign. There is a consistent process for monitoring the quality and
performance of the change management process.
5 Optimised when
The change management process is regularly reviewed and updated to stay in line with good practices. The review process
reflects the outcome of monitoring. Configuration information is computer-based and provides version control. Tracking of
changes is sophisticated and includes tools to detect unauthorised and unlicensed software. IT change management is
integrated with business change management to ensure that IT is an enabler in increasing productivity and creating new
business42opportunities for the organisation.
Val IT: Projects, Programmes, Portfolios
and Value
Value – the end business outcome expected from an IT-enabled business
investment where such outcomes may be financial, non-financial or a
combination of the two.
Portfolio – a suite of business
programmes managed to optimise
overall enterprise value
Portfolio
Management Programme – a structured grouping of
projects that are both necessary and
sufficient to achieve a business outcome
and deliver value, including business
Programme change management, business
Management processes, people, etc. (primary unit of
investment within VALIT)
Project
Management Project – a structured set of activities
concerned with delivering a defined
capability based on an agreed
schedule and budget (that is necessary
but not sufficient to achieve a required
business outcome)
43
Val IT - Relationship between
Processes & Practices
Establish strategic direction and target Determine availability and sources of Human Resource Management
investment mix funding
Manage the Investment
Portfolio (PM) Evaluate and select programmes to
fund
Monitor and report on portfolio
performance
Optimise portfolio performance
Develop and evaluate initial Understand candidate programme Develop the programme plan Develop full life cycle costs and
programme concept business case and implementation options benefits
Develop detailed candidate Launch and manage the programme Update operational IT portfolios
( I M) Update the business case Monitor and report on the programme Retire the programme
44
VG processes
Investment budget
VG03.2 Define categories (within portfolios) Major business enablement
+/- 33%
and infrastructure budget
eg. implementation SAP
Continuity budget
Upgrade or enhancement of
Increased control +/- 50%
Weill
Change The Rule
Win The Race
Stay In The Race
47
McKinsey
Example
Project class
Project class
MH 1 1 2 3 4 MH 1 1 2 3 4
PROJECT
PROJECT M 1 2 3 3 4 M 1 1 2 4 4
CLASS
BASIC CRITERIA
CLASS
ML 1 2 3 4 5 ML 1 1 3 4 5
PROFITA
NUMBER
BILITY: L 1 2 3 4 5 L 1 2 4 5 5
OF
PAY COMPETITIVE OPERATIONAL DECISION
PLANNED
BACK ADVANTAGE URGENCY SUPPORT L ML M MH H L ML M MH H
MAN
TIME
DAYS
(YEARS) Profitablity Competitive advantage
DIRECT
REACTION ON
IMPROVE
EXTREME H 1 1 1 2 5 H 1 1 1 1 1
PERFORMANCE
OPERATIONAL HIGH IMPACT
Project class
Project class
SIGNIFICANTLY
RISK, CHANGED SUPPORT MH 1 1 2 3 5 MH 1 1 1 1 2
ON CUSTOMER
HIGH > 2000 < 1.5 LEGAL OR FOR KEY
KEY BUYING
OPERATIONAL DECISION M 1 1 2 3 5 M 1 1 1 2 3
FACTORS FOR
ENVIRONMENT, MAKERS
STRATEGIC
SEGMENTS
EXTREME ML 1 1 3 4 5 ML 1 1 2 3 4
MAINTENANCE
RISK L 1 2 3 4 5 L 1 2 3 4 5
IMPROVE L ML M MH H L ML M MH H
PERFORMANCE OTHER
ELIMINATE
MEDI ON CUSTOMER SUPPORT Operational urgency Decision support
1000 – CRITICAL
UM 1.5 – 2.5 KEY BUYING FOR KEY
2000 OPERATIONAL
HIGH FACTORS FOR DECISION
HANDICAPS
OTHER MAKERS
SEGMENTS
A 5 points on at least one criterion
IMPROVE
PERFORMANCE REDUCE WEEK HIGH IMPACT Accept, high priority
MEDI SLIGHTLY ON POINTS IN FOR OTHER
500 – 1000 2.5 – 4
UM CUSTOMER KEY CURRENT MANAGEMEN
BUYING OPERATIONS T
B 4 points on profitability or 3 points on at least two criteria
FACTORS
IMPROVE ONGOING Accept
AVOID SMALL
MEDI PERFORMANCE SUPPORT
PROBLEMS IN
UM 200 – 500 4–6 ON OTHER FOR OTHER
LOW BUYING
OPERATIONAL
MANAGEMEN
C 3 points on profitability or total of 7 points
USAGE
FACTORS T
NO IMPACT Accept if resources available
ON
NO IMPACT ON
MANAGEMEN
LOW < 200 >6 COMPETITIVE NO URGENCY
T D 3 points on one criterion
POSITION
EFFECTIVEN
ESS
Accept only if subcontractable
48 Decline
Sidmar-Arcelor
VG processes
• VG04 Align and integrate Value Management with enterprise financial planning:
- VG04.1 Review current enterprise budgeting practices
- VG04.2 Determine Value Management financial planning practice
requirements
- VG04.3 Identify changes required
- VG04.4 Implement optimal financial planning practices for Value
Management
• VG05 Establish effective governance monitoring:
- VG05.1 Identify key metrics
- VG05.2 Define information capture processes and approaches
- VG05.3 Define reporting methods and techniques
- VG05.4 Identify and monitor performance improvement actions
• VG06 Continuously improve Value Management practices
- VG06.1 Implement lessons learnt
49
PM processes
Risk management
Reducing transaction cost
Reducing operational cost
Improving competitiveness through IT
P
S
P
P
D
ev
e
in lop
f o in
rm g
P
at in
io no IT
Fu n
lf i se vat Go
S
P
P
S
goals into IT strategy and goals
S
S
P
P
P
si w ic
In n g ith es
te IT b w
ith
gr d e
us
i a
de at n
PM 1.4 Translate business strategy and
pa ion pa es fo
rt m s cu
P
S
S
S
rtm a de s
e nd en
IT nt co t p a
on
di s ns e f rtm
fic
S
S
P
S
S
S
S
P
S
sa ol ie en
st id n ts
IT er at cy
re io
go n
P
ve co of
r v e di
IT na ry ffe
m nc a re
e
S
P
P
ea nd nt
Lo
su /I
T b us IT
re
w s st
r in
to
S
P
P
P
er at es
in eg s
M g sa
tis i c co
ak co
f a l nt
in st y ig in
S
P
S
S
S
g o B n m ui
IT f t as ty
O ra e en
pt m n lI t
im ea sa Ir
P
P
iz s c t
eq
R in ur io ui
ap g a bl n re
th e pr
id e
P
P
S
oc men
de IT es ts
R ve in si
ed lo f r n g
S
S
P
S
uc pm ast
in r u
St g en ct
ex to ur
an
te fn e
da
rd r na ew
Example
is ls IT
in ta
g f f se
IT rv
sy ic
st es
em
s
PM processes
52
Example
organisatorisch
Projectrisico &
Ondersteuning
Aansluiting op
ATS
Vermindering
management
operationele
onzekerheid
onzekerheid
architectuur
voordeel en
Functionele
Technische
Rendement
Competitief
Informatie
Noodzaak
noodzaak
strategie
risico's
risico
Investeringsdossiers
Doorlopende dossiers in 2004
RET MKT 0020 Intrest and liquidity risk (ALM_TDI) 1 5 4 5 5 5 5 2 5 5
OND OND 0021 Quantitative Credit Risk Management (QCR) 4 5 5 5 5 5 1 4 5 5
RET RET 0119 KBD : Multikanalen krediettoep. aan particulieren 4 5 4 3 3 5 5 2 1 1
RET RET 0202 KIT 4 5 4 4 3 3 5 3 1 3
RET RET 0232 Oleander (totaaloplossing Leven Ondernemingen) 1 5 5 1 3 5 3 3 1 2
NAV NAV 0245 Collateral Management Fase 2 5 3 3 1 3 5 5 3 3 4
BED BED 0292 Bankwijd Web-enablen van ICMtoepassingen 4 5 5 1 3 1 1 4 1 3
NAV NAV 0397 IPE / EBOBA 1 5 4 1 3 5 3 4 5 4
NAV NAV 0399 Verwerking OTC Derivaten 4 5 4 4 3 5 4 1
RET RET 0403 VA Front-end Leven
RET RET 0406 Product fabriek Schadeverzekeringen 2 5 4 1 1 5 3 4 1 3
OND OND 0442 Operationeel Risicobeheer 5 5 5 5 5 3 5 3 3 3
RET RET 0449 Herwerken cliënten output 5 5 4 5 1 5 5 3 5 2
OND OND 0456 IAS Verzekeringen 4 5 4 5 5 3 3 4 5 3
OND OND 0479 Beperking van de volatiliteit onder IAS 1 5 3 5 5 3 1 4 5 2
OND OND 0501 ERP voor ondersteunende diensten B+V
RET RET 0518 OFS (Ontwikkeling Financiele Services) 4 5 4 1 3 5 5 3 1 3
Nieuwe
RET RET 0308 Migratie Centea 1 5 3 1 5 5 3 3 1 3
OND OND 0480 Reconciliatietool 1 5 1 3 3 5 1 3 3
RET RET 0884 Pleander Voorstudie Particulieren leven anders 1 5 5 2 3 5 3 2 5 2
OND OND 0887 Europese Spaarfiscaliteit 1 5 4 3 3 5 4 5 1
10
Proceed Program 21
Program 13
9
Program 03
8
Program 24
Program 19
Program 02
Program 17
Financial Worth
7 Program 09
6
Hold Program 01
vs.
Program 06
5
Program 23 Program 08 Risk
Program 11
4
Legend
3 Program
Stop
Financial Worth
Program 16
1 Right Way Done Well
Program 12 Program 07
Program 15
Green = “Are” Risk score between 1 & 3.9
0
10 9 8 7 6 5 4 3 2 1 0 Yellow = “Are” Risk score between 4 & 6.9
54
Source: Fujitsu
IM processes
55
IM04.1
Identify full
life-cycle
costs and
benefits
56
Example
(example of a web2.0
programme)
7. Appendices
Detailed analytic model
Detailed project plan
Detailed risk management plan
59 benefits realisation plan
Detailed
Full benefits register
IM processes
60
VALIT Management Guidelines
From Inputs Outputs To
*
PM1
High-level business requirements
Appropriate investment mix
Initial business case
Initial business case approval
IM2
IM3
COBIT PO1COBIT PO5 COBIT AI1
IM4 IM6 COBIT PO1 COBIT PO10
Inputs /
IM1 Initial business case COBIT AI1
COBIT PO1 IT services portfolio
COBIT PO5 IT cost-benefit estimates
outputs
COBIT PO9 Risk assesment
urit isk,
r
Functions
ns o
es
R
y
Spo
t
nt
nt
ent
nt
dit nce,
and tmen
Boa ervic
e
Off geme
Off geme
Off geme
Ma amm
Ma amm
em
Sec
ess
Ma ess
er
plia
Ma ct
rd
rd
nag
nag
es
S
ice
ice
ice
e
sin
sin
gr
gr
na
na
na
je
Activities
CE O
alu
Com
Bo a
CFO
Inv
CIO
Pro
Pro
Pro
Ma
Au
Bu
Bu
V
Create an environment that fosters and welcomes new ideas and
R A/R R R
acknowledges their champions.
Suggest new opportunities. R A/R R R R R R R
Capture opportunities for investment programmes to create value
in support of the business strategy or to address operational or C C C R C R A/R
compliance issues.
Categorise the opportunity. Clarify expected business outcome(s)
and identify, at a high level, business, process, people,
C R C C A/R
technology and organisational initiatives required to achieve the
expected outcomes.
Determine which opportunities to pursue further or examine in
more depth, and identify and assign a business sponsor for each C C C C C C A/R C
opportunity to be pursued.
Describe the business outcome(s) to which the potential
programme will contribute, the nature of the programme’s C C C A R R
contribution, and how the contribution would be measured.
Identify high-level initiatives that might be required to achieve
these outcomes.
C C
C
C
A
A
R
R
R
R
RACI
and the costs for the full economic life cycle of the programme.
State any key assumptions and identify key risks, along with their
potential impact on current and future business operations, and C C R A R R
mitigation strategies.
Document the initial programme concept business case with
C A R
information obtained.
Review and evaluate the initial programme concept business
C C C A R R R
case.
Determine whether the programme should proceed to full
C C C A R R R
programme definition and evaluation.
Obtain CIO approval and sign-off on the technical aspects of the
I R A R
initial programme concept business case.
Obtain business sponsor approval and sign-off on overall initial
programme concept business case. I A R
ACTIVITIES PROCESS IM
• An environment that fosters and • Individuals throughout the enterprise • Ensure that the enterprise’s
captures new ideas exists. suggest new investment opportunities. individual IT-enabled investments
• A process and responsibilities for • Ideas are collected, understood and contribute to optimal value.
submission and categorisation of new categorised correctly for the
ideas exist and are used. investment portfolio.
• Champions of new ideas that are • Good ideas are selected efficiently
GOALS
Business sponsor The individual accountable for delivering benefits and value to the enterprise from
(incl. service an IT-enabled business investment programme
owner)
Business unit Business individuals with roles with respect to a programme
executives /
managers
Compliance, audit, The function(s) in the enterprise responsible for compliance, audit, risk and security
risk and security
(CARS)
Chief Executive The highest ranking officer, who is in charge of the total management of the
Officer (CE0) enterprise
Chief Financial The most senior official of the enterprise, who is accountable for financial planning,
Officer (CF0 record keeping, investor relations and financial risks
Chief Information The most senior official of the enterprise, who is accountable for IT advocacy;
Officer (CIO) aligning IT and business strategies; and planning, resourcing and managing the
delivery of IT services and information, and the deployment of associated human
resources
Investment and A management structure primarily accountable for managing the enterprise’s
services board portfolio of investment programmes and existing/current services and, thus,
(ISB) managing the level of overall funding to provide the necessary balance between
enterprise-wide and specific line-of-business needs
Head of Human The most senior official of an enterprise who is accountable for planning and
Resources policies with respect to all human resources in that enterprise
Programme The individual responsible for the achievement of the programme’s objectives
Manager
Programme The function responsible for supporting programme managers and gathering,
Management assessing and reporting information about the conduct of their programmes and
Office (PgMO) constituent projects
Project The function for supporting project managers; defining and propagating
Management standardised methodologies; and gathering, assessing and reporting information
Office (PMO) about the conduct of their projects
Value The function that acts as the secretariat for the ISB in managing investment and
Management service portfolios, including assessing and advising on investment opportunities and
Office (VMO) business cases, value governance/management methods and controls, and
reporting on progress in sustaining and creating value from investments and
62 services
Relational mechanisms
(Peterson, 2003)
• Business/IT collocation
• IT leadership
•…
63
IT governance international benchmarking
• Enterprise Governance of IT
66
Implementation of EGIT in practice
Requires:
• Governance Processes
Enterprise governance of IT
• Structures
• Relational Mechanisms
Relational mechanisms
67
12 structures
“a list of 33 EGIT
practices based on
delphi research”
11 processes
10 relational mechanisms
68
EGIT: Practices identified & defined structures: 12 practices
69
EGIT: Practices identified & defined structures: 12 practices
70
EGIT: Practices identified & defined processes: 11 practices
Portfolio management (incl. business cases, Prioritisation process for IT investments and projects in
x x
information economics, ROI, payback) which business and IT is involved (incl. business cases)
Charge back arrangements - total cost of ownership Methodology to charge back IT costs to business units, to
x
(e.g. activity based costing) enable an understanding of the total cost of ownership
71
EGIT: Practices identified & defined processes: 11 practices
72
EGIT: Practices identified & defined relational mechanisms:
10 practices
73
EGIT: Practices identified & defined relational mechanisms:
10 practices
74
Perceived effectiveness of EGIT practices
0,0 0,5 1,0 1,5 2,0 2,5 3,0 3,5 4,0 4,5 5,0
75
0 = not effective, 5 = very effective
Perceived ease of implementation of EGIT practices
CIO reporting to CEO and/or COO
Security / compliance / risk officer
IT project steering committee
IT budget control and reporting
Informal meetings betw een business and IT executive/senior management
Corporate internal communication addressing IT on a regular basis
IT security steering committee
CIO on executive committee
(IT) audit committee at level of board of directors
IT strategy committee at level of board of directors
IT steering committee (IT investment evaluation / prioritisation)
Business/IT account management
IT governance aw areness campaigns
Service level agreements
Architecture steering committee
IT governance function / officer
Co-location
Project governance / management methodologies
IT leadership
Cross-training
Strategic information systems planning
Executive / senior management giving the good example
IT performance measurement (e.g. IT balanced scorecard)
Know ledge management (on IT governance)
Portfolio management (incl. business cases, information economics, ROI, payback)
Integration of governance/alignment tasks in roles&responsibilities
IT governance assurance and self-assessment
IT governance framew ork COBIT
Job-rotation
Charge back arrangements - total cost of ow nership (e.g. activity based costing)
Benefits management and reporting
IT expertise at level of board of directors
COSO / ERM
0,0 0,5 1,0 1,5 2,0 2,5 3,0 3,5 4,0 4,5
committee
3,6
3,5
S8 Security / compliance / risk officer P5
S9 IT project steering committee
3,4 R9
3,3 S10 IT security steering committee P6/P4 S8
3,2
3,1
S11
S12 •Having the CIO
Architecture steering committee
Integration of governance/alignment tasks in roles&responsibilities
Strategic information systems planning
S2
S12 R4
S11
S3
3 P1
2,9
2,8
P2
reporting to the CEO
IT performance measurement (e.g. IT balanced scorecard)
Portfolio management (incl. business cases, information economics,
P10
P7
S7
R3 R2 R10 S10
Effectiveness
0,2
0,1
0,1 0,2 0,3 0,4 0,5 0,6 0,7 0,8 0,9 1,0 1,1 1,2 1,3 1,4 1,5 1,6 1,7 1,8 1,9 2,0 2,1 2,2 2,3 2,4 2,5 2,6 2,7 2,8 2,9 3,0 3,1 3,2 3,3 3,4 3,5 3,6 3,7 3,8 3,9 4,0 4,1 4,2 4,3 4,4 4,5 4,6 4,7 4
77
Difficult to implement
Ease of implementation Easy to implement
Assignment
78
Organisation
Maturity Rationale
IT strategy committee at level of board of directors 0 1 2 3 4 5
IT expertise at level of board of directors 0 1 2 3 4 5
(IT) audit committee at level of board of directors 0 1 2 3 4 5
CIO on executive committee 0 1 2 3 4 5
CIO reporting to CEO and/or COO 0 1 2 3 4 5
IT steering committee (IT investment evaluation / prioritisation at executive / senior management level) 0 1 2 3 4 5
IT governance function / officer 0 1 2 3 4 5
Security / compliance / risk officer 0 1 2 3 4 5
IT project steering committee 0 1 2 3 4 5
IT security steering committee 0 1 2 3 4 5
Architecture steering committee 0 1 2 3 4 5
Integration of governance/alignment tasks in roles&responsibilities 0 1 2 3 4 5
Strategic information systems planning 0 1 2 3 4 5
IT performance measurement (e.g. IT balanced scorecard) 0 1 2 3 4 5
Portfolio management (incl. business cases, information economics, ROI, payback) 0 1 2 3 4 5
Charge back arrangements - total cost of ownership (e.g. activity based costing) 0 1 2 3 4 5
Service level agreements 0 1 2 3 4 5
IT governance framework COBIT 0 1 2 3 4 5
IT governance assurance and self-assessment 0 1 2 3 4 5
Project governance / management methodologies 0 1 2 3 4 5
IT budget control and reporting 0 1 2 3 4 5
Benefits management and reporting 0 1 2 3 4 5
COSO / ERM 0 1 2 3 4 5
Job-rotation 0 1 2 3 4 5
Co-location 0 1 2 3 4 5
Cross-training 0 1 2 3 4 5
Knowledge management (on IT governance) 0 1 2 3 4 5
Business/IT account management 0 1 2 3 4 5
Executive / senior management giving the good example 0 1 2 3 4 5
Informal meetings between business and IT executive/senior management 0 1 2 3 4 5
IT leadership 0 1 2 3 4 5
Corporate internal communication addressing IT on a regular basis 0 1 2 3 4 5
IT governance awareness campaigns 0 1 2 3 4 5
79
Other practices
General remarks
Assignment
0 Non-existent
There is a complete lack of any recognisable IT Governance process.
1 Initial/ad hoc
The organisation has recognised that IT Governance issues exist and need
to be addressed.
2 Repeatable but intuitive
There is awareness of IT Governance objectives, and practices are
developed and applied by individual managers.
3 Defined process
The need to act with respect to IT Governance is understood and
accepted. Procedures have been standardised, documented and
implemented.
4 Managed and measurable
IT Governance evolves into an enterprise-wide process and IT
Governance activities are becoming integrated with the enterprise
governance process.
5 Optimised
Enterprise governance and IT Governance are strategically linked,
leveraging technology and human and financial resources to increase the
competitive advantage of the enterprise.
80
Agenda
• Enterprise Governance of IT
81
Business/IT Alignment
82
Business/IT Alignment
External
Business
Business
Strategy IT Strategy
Strategy
Strategic fit
Internal
Organizational
Infrastructure and IS infrastructure
IS infrastructure
and processesand
processes processes
83
Strategic Alignment
(Henderson and Venkatraman, 1993)
Business IT
External
strategy strategy
Strategic fit
Operational IT
Internal infrastructure infrastructure
and processes and processes
Functional integration
84
Strategic Alignment model
Business IT
External
strategy strategy
Strategic fit
Operational IT
Internal infrastructure infrastructure
and processes and processes
Functional integration
85
Strategic Alignment model
Business IT
External
strategy strategy
Strategic fit
Operational IT
Internal infrastructure infrastructure
and processes and processes
Functional integration
86
Strategic Alignment model
Business IT
External
strategy strategy
Strategic fit
Operational IT
Internal infrastructure infrastructure
and processes and processes
Functional integration
87
Business/IT Alignment
strategy
structure
operations
88
Assignment
89
Assignment: linking business goals to IT goals
90
91
Business Goals
Risk management
Reducing transaction cost
Reducing operational cost
Improving competitiveness through IT
P
S
P
P
D
ev
e
in lop
f o in
rm g
P
at in
io no IT
Fu n
lf i se vat Go
S
P
P
S
llin cu ive als
g rit IT
In SL y se
cr
ea A 's rv
S
S
P
P
P
si w ic
In n g ith es
te IT b w
ith
gr d e
us
i a
de at
pa n es fo
pa ion
rt m s cu
P
S
S
S
rtm a de s
e nd en
IT nt co t p a
on
di s ns e f rtm
fic
S
S
P
S
S
S
S
P
S
sa ol ie en
st id n ts
IT er at cy
re io
go n
P
ve co of
r v e di
IT na ry ffe
m nc a re
e
S
P
P
ea nd nt
Lo
su /I
T b us IT
re
w s st
r in
to
S
P
P
P
er at es
in eg s
M g sa
tis i c co
ak co
f a l nt
in st y ig in
S
P
S
S
S
g o B n m ui
IT f t as ty
O ra e en
pt m n lI t
im ea sa Ir
P
P
iz s c t
eq
R in ur io ui
ap g a bl n re
th e pr
id e
P
P
S
oc men
de IT es ts
R ve in si
ed lo f r n g
S
S
P
S
uc pm ast
in r u
St g en ct
ex to ur
an
te fn e
da
rd r na ew
Linking business goals – IT goals
is ls IT
in ta
g f f se
IT rv
sy ic
st es
em
s
Aligning business goals and IT goals
• UAMS-ITAG/ITGI research:
- Previous research
• 20 business goals and 28 IT goals
• Across multiple sectors
- This study
• Validate business and IT goals
• Gain insight in priorities for different sectors
• Examine relationship between IT goals and business goals
92
Aligning business goals and IT goals
• Delphi methodology:
- Structured process for collecting and distilling knowledge
from a group of experts by means of several research
rounds.
• 5 sectors
- Manufacturing and pharmaceuticals, IT professional services,
telecommunications and media, government, utilities and
healtcare, and retail and transportation.
93
Aligning business goals and IT goals
94
Aligning business goals and IT goals
95
ts
en
m
g
st
in
ve
ak
in
m
t
s
n
es
on
e
m
pl
va usin
si
ire
o
ity
ci
pe
de
ns
iv
b
eq
en ity
ct
d
tio
d)
ic
e
du
(IT nal
le
g
la
n
e
s
ab
ro
gu
si
io
ne
t
i
ra
ot
fp
y
bu
ct
re
si
r
st
m
en f u n
ve
af
bu
ity
d
nd
r
d
es
st
e
fo
an
i
el
an
l
ic
ss
ta
i
g
es
b
i
nd
ge
d
of
ic
n
rv
n
s
la
ce
io
uc
d
ic
l
e
w
se
ng
la
po
an
t
ai
le
c
rv
at
a
ro
od
s
vi
av
na
ha
ch
l
rm
se
d
al
k
sk
tm
p
er
st
l
pr
an
ris
cy
io
rn
us t o c
d
co
ss
fo
n
ss
d
es
in
n
at
r
te
e
n
s
of
in
n
te
ne
e
a
re
ag
v
es
s
a
r
io
an h i n
n
g
e
nt
in
ex
es
tim ful
n
si
pa
s
at
si
n
op
an
t
in
tio
ai
i
ct
i
u
on
oc
bu
e
nt
nd
th
it
us
ns
m
in
b
u
m
w
a
in
ie
pr
i
od
is
t
w
po
n
n
b
tra
ge
on
ta
d
y
or
ur
ai
nd
n
d)
an e s s
nc
an e pr
y
n
s
na
nt
c
a
et
nc
l
re
er
ai
te
de ncia
v e le a
a
op
e
op
ai
e
r
m
in
i
ia
om
v
ic
pl
in
bl
M
d
m
l
iti
s
s
pl
el
re
rv
st
b
o
om
d
na
bu
ov oal
ty
et
st
ia
d
go
m
ev
an
in
co
se
IT
i
cu
,e
l
co
c
f
re
. O agi
,d
. E ise
Im s G
om
a
(
e
h
ify
le
ov
ov
e
e
lis
n
e
re
im
ov
ag
ie
rc
ai
vi
1. es
nt
pr
pr
b
at
na
i
qu
ch
bt
pt
ro
ov
ov
pr
pr
ta
an
de
ffe
in
m
re
.O
;A
.P
Es
Ac
Im
Pr
Pr
.I
.I
.I
M
us
C
IT Goals
10
11
12
13
14
15
16
17
2.
3.
4.
5.
6.
7.
8.
9.
B
1. Align the IT strategy to the business strategy P S S P P P S S P P S S P S S S P
2. Maintain the security (confidentiality, integrity and avaliability) of information and processing infrastructure P P P P S S P
3. Make sure that IT services are reliable and secure P P P P S S S S S S S S
4. Provide service offerings and service levels in line with business requirements P P S P P S S S S S S S S S
5. Provide IT compliancy with laws and regulations S P P S S S P
6. Translate business functional and control requirements in effective and efficient automated solutions S S S S P S S S S S S S S S
7. Deliver projects on time and on budget meeting quality standards S S S S S S S S S S
8. Drive commitment and support of executive management S S S S S S S S S S
9. Improve IT’s cost-efficiency S P P P S
10. Account for and protect all IT assets S S S S S S
11. Acquire, develop and maintain IT skills that respond to the IT strategy S S P S S S S S
12. Provide IT agility (in responding to changing business needs) S S S S P P S
13. Offer transparency and understanding of IT cost, benefits and risks S S S S P
14. Optimise the IT infrastructure, resources and capabilities S S P S P S S
15. Accomplish proper use of applications, information and technology solutions S S S S S S S S S S S S S
16. Seamlessly integrate applications and technology solutions into business processes S S P S S S S S S S S
17. Ensure that IT demonstrates continuous improvement and readiness for future change S S S P S P
18. Acquire knowledge and expertise in emerging technologies for business innovation and optimisation S S P S S S S P
96
Luftman assessment of business/IT alignment maturity
• Validated instrument
• Used in many studies to assess business/IT alignment
• 6 attributes
- Communications maturity
- Competency/value measurements maturity
- Governance maturity
- Partnership maturity
- Scope & architecture maturity
- Skills maturity
97
attribute characteristics level 1 characteristic level 5
•communications maturity
• understanding of business by IT minimum pervasive
• understanding of IT by business minimum pervasive
• inter/intra-organizational learning casual, ad hoc strong and structured
• protocol rigidity command and control informal
• knowledge sharing ad hoc extra-enterprise
• liaison(s) breath/effectiveness none or ad hoc extra-enterprise
• governance maturity
• business strategic planning ad hoc integrated across & external
• IT strategic planning ad hoc integrated across & external
• reporting/organization structure CIO reports to CFO CIO reports to CEO
central/decentral federated
• budgetary/control cost center, erratic investment center, profit center
• IT investment management cost based, erratic business value
• steering committee(s) not formal, regular partnership
• prioritization process reactive value added partner
98
attribute characteristics level 1 characteristic level 5
•partnership maturity
• business perception of IT value IT perceived as a cost IT co-adapts with business
• role of IT in strategic business planning no seat at business table co-adaptive with business
• shared goals, risk, rewards/penalties IT takes risk risks and rewards shared
• IT program management ad hoc continuous improvement
• relationship/trust style conflict/minimum valued partnership
• business sponsor/champion none at the CEO level
• scope & architecture maturity
• traditional, enabler/driver traditional systems business strategy driver/enabler
• standards articulation none or ad hoc inter-enterprise standards
• architectural integration: no formal integration evolve with partners
• functional organization integrated
• enterprise standard enterprise architecture
• inter-enterprise with all partners
• architectural transparency, flexibility none across the infrastructure
• skills maturity
• innovation, entrepreneurship discouraged the norm
• locus of power in the business all executives, including CIO
• management style command and control relationship based
• change readiness resistant to change high, focused
• career crossover none across the enterprise
• education, cross-training none across the enterprise
• attract & retain best talent no program effective program for
99
Example questions
(partnership maturity)
ov
er l
O n m
il/ en
G t
as
/M
in
in
g
Ph U
til
ar iti
m es
ac
eu
ti c
Ed al
uc
at
io
na
l
O
ve
ra
ll
Av
er
ag
e
Business / IT alignment international benchmark
Business / IT alignment Belgian benchmark
102
Business / IT alignment Belgian benchmark
103
The relationship between EGIT practices and business / IT
alignment
B CEO
Change Manager
Head IT Governance
I
Head IT Development
Head Project Management Office
J CIO
Head Accounting
104
Defining maturity of 33 EGIT practices
0 Non-existent
There is a complete lack of any recognisable IT Governance process.
1 Initial/ad hoc
The organisation has recognised that IT Governance issues exist and need
to be addressed.
2 Repeatable but intuitive
There is awareness of IT Governance objectives, and practices are
developed and applied by individual managers.
3 Defined process
The need to act with respect to IT Governance is understood and
accepted. Procedures have been standardised, documented and
implemented.
4 Managed and measurable
IT Governance evolves into an enterprise-wide process and IT
Governance activities are becoming integrated with the enterprise
governance process.
5 Optimised
Enterprise governance and IT Governance are strategically linked,
leveraging technology and human and financial resources to increase the
competitive advantage of the enterprise.
105
A B I J P5 0 0 2 4
S1 0 0 0 0 P6 0 0 1 4
S2 4 1 0 1 P7 1 0 1 1
S3 3 3 3 3 P8 2 3 3 4
S4 2 5 2 0 P9 1 2 4 5
S5 2 5 4 5 P10 0 1 1 3
S6 2 2 4 4 P11 0 0 0 0
S7 2 0 4 4 R1 1 0 1 2
S8 2 3 4 5 R2 5 2 3 3
S9 2 2 4 4 R3 2 0 2 1
S10 0 0 0 4 R4 3 3 4 4
S11 0 0 1 3 R5 2 0 0 4
S12 2 1 2 5 R6 2 2 5 5
P1 1 2 1 4 R7 2 0 0 0
P2 1 2 4 4 R8 1 4 4 4
P3 1 2 4 4 R9 2 0 2 3
P4 0 0 2 5 R10 1 1 1 1
1,48 1,39 2,21 3,12
106
The relationship between EGIT and business/IT alignment
G
F
Business/IT << A B C D E H I J >>
alignment maturity 1,8 1,9 2,0 2,1 2,2 2,3 2,4 2,5 2,6 2,7 2,8 2,9 3,0 3,1 3,2 3,3 3,4 3,5 3,6
4,00
3,50
3,00
J
Maturity of IT I
2,50
governance B
2,00
1,50
practices A
1,00
0,50
0,00
Structures Processes Relational
mechanisms
107
The relationship between EGIT and business / IT alignment
• Maturity averages
• Clear gap between A-B and I-J
3,5
3
2,5
2
1,5
1
0,5
0
A B I J
108
6
Extreme cases analysis
5 EGIT practices versus
business / IT alignment
4
3,5
J
3 3
A
2,5
2
2 Average IT goverance
practices maturity
1 1,5
1
0 6
0,5
S1 S4 S5 S6 S9 P1 P3 P80 P9 R8
A B I J
5
4,00
3,50 4
3,00
J
2,50 J
I
2,00 3
B A
1,50
A
1,00
0,50 2
0,00
Structures Processes Relational
1 mechanisms
0
109
P11
P10
R10
S10
S11
S12
R5
R6
R7
R9
R2
R3
R4
R8
R1
P9
P3
P4
P5
P6
P7
P8
P1
P2
S9
S2
S3
S7
S8
S1
S4
S5
S6
Agenda
• Enterprise Governance of IT
110
From enterprise governance of IT to
business value
111
Business/IT alignment and
Business Value from IT
- Productivity paradox
(Brynjolfson)
112
What is the relationship between organizational performance
and IT governance practices based on COBIT 4.1 and Val IT
2.0?
• Research model and metrics use the available concepts from COBIT and
Val IT.
• Three research constructs
- COBIT and Val IT processes
measured by the implementation status of 34 COBIT processes
and 22 Val IT processes
- Technical, operational and business capabilities
measured by the achievement status of 18 IT goals
- Business Outcome
measured by the achievement status of 17 business goals and 3
Val IT goals
113
Questionnaire - Sample question
114
IT and Business Governance Practices Reserach Model
COBIT Processes Val IT processes
measured by measured by
Processes implementation Processes implementation
status status
Business/IT Alignment
IT Goals
Business Outcome
Measured by
Business Goals achievement status
Business Goals
115
Research questions
116
Research questions
117
Key findings
1
IT Goals
Technical Capability Operational Capability
IT related Business capability
measured by measured by
measured by
IT Goals achievement IT Goals achievement
IT goals achievement status
status status
2
Business Goals
Business Outcome
Measured by
Business Goals achievement status
119
Implementation status IT processes
3,50
3,40
3,30
3,20
3,10
3,00
2,90
2,80
2,70
2,60
2,50
COBIT COBIT COBIT COBIT COBIT Val IT Val IT Val IT VAL IT
PO AI DS ME Total VG PM IM Total
120
Knowing-doing gap
121
Summary - High impact
implemented processes / achieved
IT goals relation
122
Summary - High impact
achieved IT goals / achieved
Business Goals relation
• 8 high impact IT Goals
• 6 high impacted Business Goals
123
Input COBIT 4.1 development
Mapping COBIT 4.1 / correlation
matrix business goals – IT Goals
124
Input COBIT 4.1 development
Mapping COBIT 4.1 / correlation
matrix IT goals – COBIT processes
125
• Questions and discussion
• More information
- Email
• [email protected]
• [email protected]
- Books
• Van Grembergen W., De Haes S., Implementing
Information Technology Governance: models,
practices and cases, 255p., IGI Publishing, 2008
• Van Grembergen W., De Haes S., Enterprise
Governance of IT: achieving strategic alignment and
value, 360p., Springer, 2009
126