root / chapter3.tex @ 28:be66d105f0cb
History | View | Annotate | Download (29.9 kB)
1 |
\chapter{Overview of Literature in IT Governance} |
---|---|
2 |
\label{chapter:3} |
3 |
|
4 |
The importance of \ac{it} governance has been widely acknowledged in the |
5 |
academic and professional literature, especially with regards to the |
6 |
private sector. The corporate scandals of Enron and other US-based |
7 |
companies raised the level of regulation and tightened corporate |
8 |
governance in order to protect investors and ensure fiscal |
9 |
accountability. Increased significance was similarly attributed to \ac{it} |
10 |
governance, which is the focus of this chapter. Research has found |
11 |
that effective \ac{it} governance enhances competitiveness and business |
12 |
value \cite{WeillRoss2004b}. There is debate, however, as to how this |
13 |
can be best operationalised. The following sections will provide an |
14 |
overview of the literature on the nature, forms and mechanisms of \ac{it} |
15 |
governance. Current research in the main areas will be discussed, |
16 |
together with the latest empirical findings. |
17 |
|
18 |
\section{Defining IT Governance} |
19 |
|
20 |
As a result of research developing in different areas, scholars and |
21 |
professional bodies have suggested many useful definitions. There |
22 |
seems to be general consensus as to how \ac{it} governance has come to |
23 |
be interpreted, although the focus is slightly different between |
24 |
studies. |
25 |
|
26 |
Sambamurthy and Zmud \cite{SambamurthyZmud2000} define \ac{it} |
27 |
governance as ``an organisation's \ac{it}-related authority pattern''. |
28 |
The authors suggest research should understand the ``organising logic |
29 |
for the \ac{it} function'' which they define as ``the managerial |
30 |
rationale for designing and evolving specific organisational |
31 |
arrangements in response to an enterprise's environmental and |
32 |
strategic imperatives''. Building on this work, Schwarz and Hirschheim |
33 |
\cite{Schwarz2003} refer to \ac{it} governance as ``the \ac{it} |
34 |
related structures or architectures (and associated authority pattern) |
35 |
implemented to successfully accomplish (\ac{it} imperative) activities |
36 |
in response to an enterprise's environmental and strategic |
37 |
imperatives''. |
38 |
|
39 |
In another strand of research, Weill and Ross \cite{WeillRoss2004b} |
40 |
define \ac{it} governance as representing ``the framework for decision |
41 |
rights and accountabilities to encourage desirable behavior in the use |
42 |
of \ac{it}''. This definition captures the high level at which \ac{it} |
43 |
governance operates, but at the same time emphasises the unique |
44 |
character it can attain since desirable behaviors differ between |
45 |
organisations. It also encompasses both the behavioural and normative |
46 |
aspects of governance in line with \ac{oecd} principles \cite{OECD}. |
47 |
|
48 |
Relating \ac{it} governance with other aspects of the organisation, |
49 |
Van Grembergen \cite{Grembergen2003} proposes the following |
50 |
definition: ``\ac{it} governance is the organisational capacity |
51 |
exercised by the board, executive management and \ac{it} management to |
52 |
control the formulation and implementation of \ac{it} strategy and in |
53 |
this way ensure the fusion of business and \ac{it}''. Along other |
54 |
material operationally focused on implementation, the \ac{it} |
55 |
Governance Institute suggests that ``\ac{it} Governance is the |
56 |
responsibility of the Board of Directors and executive management. It |
57 |
is an integral part of enterprise governance and consists of the |
58 |
leadership and organisational structures and processes that ensure |
59 |
that the organisation's \ac{it} sustains and extends the |
60 |
organisation?s strategy and objectives''~\cite{ITGI2003} . |
61 |
|
62 |
The last two definitions emphasise the relevance to corporate |
63 |
governance, a recurring theme in the literature. Weill |
64 |
\cite{Weill2004} suggests that ``good \ac{it} governance draws on |
65 |
corporate governance principles to manage and use \ac{it} to achieve |
66 |
corporate performance goals''. Other work states that due to the |
67 |
growing reliance of organisations on \ac{it}, it is very difficult to |
68 |
distinguish between \ac{it} and corporate governance, since they are |
69 |
interrelated and constantly feeding into each other |
70 |
\cite{Grembergen2003}. In addition to this synergy, the literature on |
71 |
Strategic Information Systems Planning also provides useful guidance |
72 |
to \ac{it} governance\cite{Webb2006}, as it contributes to work on its |
73 |
supporting mechanisms such as critical success factors, the value |
74 |
chain model and business process reengineering \cite{Grembergen2003}. |
75 |
|
76 |
There is, however, a clear demarcation between \ac{it} governance and |
77 |
\ac{it} management. The former is usually referred to as a broader |
78 |
term that covers \ac{it} performance and transformation towards |
79 |
business and customer demands, while the latter is restricted to |
80 |
denoting effective supply of \ac{it} services and products, as well as |
81 |
management of \ac{it} operations \cite{Peterson2003}. Although |
82 |
scholars and practitioners insist on the value of involving \ac{it} |
83 |
management in \ac{it} governance processes, they are quick to dismiss |
84 |
the assumption of \ac{it} governance as an enhanced mode of \ac{it} |
85 |
management and draw a definite line between the two concepts and the |
86 |
distinct purposes they serve \cite{HaesGrembergen2004,Peterson2003}. |
87 |
As Weill and Ross\cite{WeillRoss2004b} clearly explain, governance |
88 |
establishes who has the right to make decisions, while management |
89 |
involves the actual decision-making and implementation processes. |
90 |
|
91 |
A large part of the literature discusses an extended view of \ac{it} |
92 |
governance, departing from decision rights to include governance |
93 |
mechanisms, informal arrangements and other means to support |
94 |
organisational objectives, as will be discussed in the following |
95 |
sections. |
96 |
|
97 |
\section{Key IT Governance Decisions} |
98 |
\label{sec:key-it-governance-decisions} |
99 |
|
100 |
Weill and Ross \cite{WeillRoss2004b} depart from traditional research |
101 |
on \ac{it} governance with their contemporary framework for the |
102 |
customisation of \ac{it} governance systems \cite{BrownGrant2005}. |
103 |
Drawing on research in 250 companies worldwide, they argue that the |
104 |
starting point for effective \ac{it} governance lies in articulating |
105 |
\ac{it} governance decisions and positioning the appropriate people to |
106 |
engage in decision-making in the following five interrelated areas: |
107 |
|
108 |
\begin{itemize} |
109 |
|
110 |
\item \ac{it} Principles |
111 |
|
112 |
These are high-level statements regarding the use of \ac{it} and |
113 |
should be derived naturally to match and support an organisation's |
114 |
business and operational objectives. Weill and Ross |
115 |
\cite{WeillRoss2004b} suggest that these principles should identify |
116 |
the organisational operating model, concrete ways in which \ac{it} |
117 |
can support it, and the funding model required. \ac{it} principles |
118 |
guide decisions in the other domains listed below and may be used to |
119 |
raise a shared understanding among organisational members. |
120 |
|
121 |
\item \ac{it} Architecture |
122 |
|
123 |
Architecture design relies on \ac{it} principles to capture |
124 |
requirements for process, data and technical standardisation and |
125 |
integration, according to the organisation's objectives. For |
126 |
example, the extent to which an organisation decides between stable |
127 |
infrastructure and local flexible applications reflects a |
128 |
translation of relevant strategic choices such as the degree of |
129 |
business flexibility. |
130 |
|
131 |
\item \ac{it} Infrastructure Strategies |
132 |
|
133 |
\ac{it} infrastructure is defined as ``the foundation of planned |
134 |
\ac{it} capability (both technical and human) available throughout |
135 |
the business as shared and reliable services and used by multiple |
136 |
applications''~\cite{WeillRoss2004b}. Examples of crucial governance |
137 |
decisions around infrastructure include the location of |
138 |
infrastructure services, pricing, updating and outsourcing. |
139 |
|
140 |
\item Business Applications Needs |
141 |
|
142 |
Decisions in this area seek to achieve a balance between, on the one |
143 |
hand, finding creative ways to increase business value through |
144 |
applications that support organisational objectives and, on the |
145 |
other, complying with architectural integrity. |
146 |
|
147 |
\item \ac{it} Investment and Prioritisation |
148 |
|
149 |
Investment levels should correspond to the strategic role attached |
150 |
to \ac{it}. An \ac{it} investment portfolio---an analogy to |
151 |
financial investment portfolios---provides a useful way to approach |
152 |
decisions on funding allocation, based on strategic alignment, |
153 |
return and risk considerations. Prioritising and reconciling \ac{it} |
154 |
needs between organisational departments, as well as distinguishing |
155 |
absolutely necessary from merely desirable \ac{it} capabilities, are |
156 |
both included in this area of decision-making. |
157 |
|
158 |
\end{itemize} |
159 |
|
160 |
\section{IT Governance Forms and Archetypes} |
161 |
|
162 |
A large part of the literature discusses appropriate \ac{it} |
163 |
governance decision-making structures for different areas in order to |
164 |
maximise efficiency and return on investment. |
165 |
|
166 |
One of the most common approaches distinguishes ``\ac{it}-related |
167 |
authority patterns'' as centralised, decentralised, or federal |
168 |
\cite{SambamurthyZmud1999}. \emph{Centralised} \ac{it} governance |
169 |
grants decision rights to corporate stakeholders only. The |
170 |
\emph{decentralised} mode assigns authority to either divisional |
171 |
units, a mix of divisional units and line management actors, or in |
172 |
very rare cases, just to line managers. The advantages of the first |
173 |
include control over \ac{it} and a greater opportunity to realise |
174 |
economies of scale, while the second model allows for greater |
175 |
customisation and responsiveness \cite{BrownGrant2005}. |
176 |
|
177 |
A \emph{federal} model would involve a corporate unit and divisional |
178 |
units or line management in different variations \cite{Peterson2004, |
179 |
SambamurthyZmud1999, Weill2004}, combining the advantages of both |
180 |
centralised and decentralised models. Peterson suggests a distinction |
181 |
between \ac{it}-centric and business-centric approaches, according to |
182 |
the participation of \ac{it} and business executives in |
183 |
decision-making \cite{Peterson2004}. Typically, there is central |
184 |
control on decisions around \ac{it} infrastructure supply and |
185 |
decentralised patterns regarding \ac{it} applications and use |
186 |
\cite{BrownMagill1998}. Similar types of \ac{it} governance have been |
187 |
described as hybrid, distributed, centrally-decentralised and |
188 |
equilibrium models or structures \cite{BrownGrant2005}. |
189 |
|
190 |
Sambamurthy and Zmud \cite{SambamurthyZmud1999} note that \ac{it} |
191 |
governance arrangements are not stable but frequently change from more |
192 |
centralised to more decentralised forms and vice versa. At the same |
193 |
time, it is acknowledged that there are no strict boundaries |
194 |
between centralised, decentralised and federal models, since they are |
195 |
all situated on a continuum and reflecting more complicated |
196 |
arrangements encountered in organisations \cite{BrownGrant2005}. |
197 |
|
198 |
In essence, governance structures are put in place to balance the |
199 |
tensions between local units and central parts of an enterprise |
200 |
\cite{Huang2010}. To achieve this task, more flexible \ac{it} |
201 |
governance models have been developed, in vertically and horizontally |
202 |
expanded variations \cite{BrownGrant2005, WeillRoss2004b}. Six \ac{it} |
203 |
governance archetypes have been identified to illustrate which sets of |
204 |
stakeholders have input and/or decision rights regarding the five key |
205 |
decisions areas described in~\ref{sec:key-it-governance-decisions}. |
206 |
|
207 |
\paragraph{Business Monarchy} |
208 |
In business monarchies, business executives at the most senior levels |
209 |
of organisations (CxOs) make decisions on \ac{it} governance. This |
210 |
style is common with respect to \ac{it} principles, in this way |
211 |
enhancing the chances for \ac{it} alignment with business objectives. |
212 |
\ac{it} investment is another area of regular application, where such |
213 |
high-level budgeting decisions establish funding priorities across |
214 |
competing parts of the organisation, rather than being solely focused |
215 |
on \ac{it}. |
216 |
|
217 |
\paragraph{IT Monarchy} |
218 |
Senior \ac{it} executives make decisions in groups or individually, |
219 |
usually with input from both corporate teams and business units. This |
220 |
governance model is more frequently adopted in \ac{it} architecture |
221 |
and \ac{it} infrastructure strategies decisions. In other areas the |
222 |
involvement of business executives is required to ensure strategically |
223 |
important goals, responsibility and commitment. |
224 |
|
225 |
\paragraph{Feudal} |
226 |
Feudal arrangements delegate decision-making to the leaders of |
227 |
business units, regions or business functions who own \ac{it} |
228 |
processes. However, this is a less widespread model, as it does not |
229 |
take advantage of synergies across the organisation. Only little |
230 |
application has been observed. |
231 |
|
232 |
\paragraph{Federal} |
233 |
This model of \ac{it} governance involves coordination between the |
234 |
senior business executives and business unit leaders. There is often |
235 |
participation of senior \ac{it} executives or business unit \ac{it} |
236 |
leaders. The federal archetype is regularly used, but only to provide |
237 |
input to all five decision areas |
238 |
of Section~\ref{sec:key-it-governance-decisions} by a large percentage of the |
239 |
organisations studied. Actual decision-making is organised around this |
240 |
type of arrangement mainly with regard to business applications needs |
241 |
across different units, as well as for \ac{it} investment, in order to |
242 |
ensure a balance between different business units' priorities. It can |
243 |
be argued that this model favours large and powerful business units, |
244 |
leading the rest to adopt local \ac{it} solutions. |
245 |
|
246 |
\paragraph{IT Duopoly} |
247 |
Duopolies refer to bilateral decision-making processes between \ac{it} |
248 |
executives (only central or together with those from business units) |
249 |
and either senior level business executives, or business unit leaders, |
250 |
the same group involved in feudal arrangements. The simple management |
251 |
structure and the ability to customise decisions for different units |
252 |
efficiently make duopolies popular in the five key \ac{it} governance |
253 |
decision areas. Regarding \ac{it} principles, coordination between |
254 |
senior business and \ac{it} management ensures alignment and |
255 |
commitment to business objectives. Duopolies allow rapid consideration |
256 |
of both business and technological issues around shared infrastructure |
257 |
services, transferring expertise from one party to the other. |
258 |
Moreover, \ac{it} duopolies increase the involvement of \ac{it} in |
259 |
business applications decisions, resulting to greater exploitation of |
260 |
current technical infrastructures. Along these lines, \ac{it} |
261 |
investment and prioritisation often relies on \ac{it} duopolies to |
262 |
identify risks and opportunities, especially around long-term and more |
263 |
efficient sharing of infrastructures. |
264 |
|
265 |
\paragraph{Anarchy} |
266 |
Here, there is no coordination across the organisation, as local needs |
267 |
guide decisions made by individuals or small groups independently. |
268 |
This model is very rare and only appropriate when it is necessary to |
269 |
react quickly to change. |
270 |
|
271 |
As organisations expand geographically and diversify their activities, |
272 |
organisational structures are not adequate to reconcile conflicting |
273 |
needs and objectives and \ac{it} governance becomes indispensable. A |
274 |
certain amount of heterogeneity in governance forms archetypes is |
275 |
identified across studies, while it is now widely acknowledged that |
276 |
``there is no single `best' \ac{it} organisational structure or |
277 |
governance arrangement because \ac{it} needs to respond to the unique |
278 |
environment within which it exists'' \cite{Agarwal2002, |
279 |
BrownGrant2005}. Willson and Pollard stress the significance of the |
280 |
unique characteristics of the organisational and historical |
281 |
environment \cite{WillsonPollard2009}. Other research shows that more |
282 |
successful organisations are adopting specific governance models |
283 |
\cite{WeillRoss2004b}. A significant amount of work has been devoted |
284 |
to understanding how specific variables affect \ac{it} governance |
285 |
structures. This topic will be discussed in the following section. |
286 |
|
287 |
|
288 |
\section{Drivers of IT Governance Forms: Multiple Contigencies} |
289 |
|
290 |
It is important to understand the reasons for adopting specific |
291 |
\ac{it} governance arrangements \cite{SambamurthyZmud1999}. Early |
292 |
research considered single contingencies or a set of individual |
293 |
contingencies without paying attention to possible interactions. |
294 |
Strategic and performance goals, organisational and decision-making |
295 |
structures, governance experience, size and diversity have been found |
296 |
to influence the choice of \ac{it} governance structural forms |
297 |
\cite{BrownGrant2005, WeillRoss2004b}. At the same time, differences |
298 |
according to industries and regions determine appropriate governance |
299 |
arrangements. For instance, not-for-profit and government |
300 |
organisations are characterised by different performance measures, |
301 |
accountability patterns and cultures; as a result, governance |
302 |
archetypes suitable to successful for-profit companies may not apply |
303 |
directly to these organisations. |
304 |
|
305 |
In any case, single contingency factors are not adequate to explain |
306 |
how \ac{it} governance forms are shaped, since there is significant |
307 |
interaction between multiple influences \cite{BrownMagill1998, |
308 |
SambamurthyZmud1999}. A theory of multiple contingencies has been |
309 |
introduced~\cite{SambamurthyZmud1999}, looking at how a consideration |
310 |
of reinforcing, conflicting and dominating forces generates a better |
311 |
understanding of the evolutionary nature of \ac{it} governance in |
312 |
organisations. Through empirical work it was found that reinforcing |
313 |
and dominating contingencies would contribute towards centralised or |
314 |
decentralised models of \ac{it} governance, while conflicting |
315 |
contingencies were more likely to create federal modes. Contingencies |
316 |
have been grouped in three categories. These explain the establishment |
317 |
of specific \ac{it} governance types against others. |
318 |
|
319 |
\paragraph{Corporate Governance} |
320 |
\ac{it} governance models frequently reflect similar arrangements |
321 |
adopted in the corporate governance of the same organisations. In |
322 |
addition, the size of the firm plays a significant role, as larger |
323 |
organisations usually have more divisions and tend to decentralise |
324 |
corporate and \ac{it} governance to be able to respond to the needs of |
325 |
the business units. |
326 |
|
327 |
\paragraph{Economies of Scope} |
328 |
Economies of scope are defined as ``the benefits arising from the |
329 |
sharing of appropriate \ac{it}-related expertise, know-how and |
330 |
investments across the enterprise''~\cite{SambamurthyZmud1999}. |
331 |
Drawing on strategic management literature, it is suggested that |
332 |
diversification mode, diversification breadth, and exploitation |
333 |
strategy are three additional factors influencing \ac{it} governance. |
334 |
\begin{itemize} |
335 |
|
336 |
\item \emph{Diversification mode} refers to whether, on the one hand, |
337 |
strategic goals towards growth assume an internal outlook, |
338 |
leveraging existing technological capabilities and infrastructures. |
339 |
A centralised mode would facilitate coordination of such objectives. |
340 |
On the other hand, the diversification mode can be directed towards |
341 |
external expansion through acquisitions, a strategy that may require |
342 |
a decentralised form of \ac{it} governance in order to accommodate |
343 |
differences between the \ac{it} infrastructures and units. |
344 |
|
345 |
\item \emph{Diversification breadth} refers to the similarity between |
346 |
the products of different business units in the same firm or the |
347 |
relevance of the markets they compete in. Assuming that greater |
348 |
similarity in products and markets means less differentiation in |
349 |
\ac{it}, a centralised mode would be more likely to achieve |
350 |
economies of scope. Conversely, little similarity in products and |
351 |
markets would make a decentralised model more appropriate. |
352 |
|
353 |
\item Under the condition that diversification mode or breadth allow |
354 |
the leveraging of economies of scope, \emph{exploitation strategies} |
355 |
provide an avenue to take further advantage of the situation. One |
356 |
way to achieve this would be either by building internal |
357 |
partnerships to integrate \ac{it} knowledge and authority, and |
358 |
thereby adopting decentralised \ac{it} governance at the divisional |
359 |
level, or by merging \ac{it} assets, supported by centralised |
360 |
decision rights. \end{itemize} |
361 |
|
362 |
\paragraph{Absorptive Capacity} |
363 |
This term is used to denote employee experience and capabilities in |
364 |
evaluating information and constructing knowledge bases, as well as |
365 |
engaging in effective decision-making and implementation. Lack of |
366 |
\ac{it}-related absorptive capacity in line management favours |
367 |
centralised \ac{it} governance models, while greater \ac{it} |
368 |
experience supports decentralised forms. |
369 |
|
370 |
\section{Governance Mechanisms} |
371 |
|
372 |
\ac{it} governance is not solely determined by governance |
373 |
forms~\cite{Ribbers2002, Schwarz2003}, as these work within a dynamic |
374 |
and competitive environment. In addition to decision rights and |
375 |
authority structures, the \ac{it} governance literature extends to |
376 |
examine horizontal integration capabilities, as ``the ability to |
377 |
coordinate and integrate formal and informal \ac{it} decision-making |
378 |
authority across business and \ac{it} stakeholder communities'' |
379 |
\cite{Peterson2004}. This section will discuss the cross-functional |
380 |
implementation of \ac{it} governance in terms of formal and informal |
381 |
coordination mechanisms, structural layers and processes |
382 |
\cite{Brown2004}. |
383 |
|
384 |
\paragraph{Structures and Committees} |
385 |
|
386 |
Structures and committees are referred to as structural \ac{it} |
387 |
governance capabilities \cite{Peterson2004}. Unrelated to \ac{it} |
388 |
governance forms, these mechanisms involve formal roles and |
389 |
relationships contributing to horizontal contact between \ac{it} and |
390 |
business management. \acsp{cio} and liaison roles such as \ac{it} |
391 |
relationship managers, \ac{it} account managers, as well as \ac{it} |
392 |
executive councils and project committees, advisory boards and centres |
393 |
of excellence, are all elements of structural capabilities. |
394 |
|
395 |
Weill and Ross \cite{WeillRoss2004b} emphasise the decision-making |
396 |
responsibilities accompanying this type of mechanisms, discuss how |
397 |
they can generate commitment and relate these with the \ac{it} |
398 |
governance archetypes. As it would be anticipated, business monarchies |
399 |
employ executive committees or part of these, sometimes together with |
400 |
the {\sc ceo}. In \ac{it} monarchies one encounters \ac{it} |
401 |
leadership teams and \ac{it} architecture committees, with some |
402 |
members participating in both the \ac{it} and business realms in order |
403 |
to ensure alignment. The drive for shared \ac{it} infrastructures and |
404 |
data makes federal archetypes necessary, but to balance local and |
405 |
enterprise priorities, senior executive committees in this case draw |
406 |
members from all business units. Duopolies are supported by three |
407 |
mechanisms: \ac{it} councils with joint business/\ac{it} memberships, |
408 |
process teams comprising cross-functional process owners and |
409 |
\ac{it} executives, as well as business/\ac{it} relationship managers. |
410 |
|
411 |
\paragraph{Processes and Control Frameworks} |
412 |
|
413 |
This type of mechanism reflects the degree to which decision-making |
414 |
and monitoring follow formalised standard procedures and rules |
415 |
\cite{Peterson2004}. Apart from \ac{it} governance frameworks |
416 |
developed by organisations themselves, there is a range of \ac{it} |
417 |
standards provided by external bodies that consolidate best practices |
418 |
in a structured manner, but at the same time allow organisations to |
419 |
adapt them to their needs. |
420 |
|
421 |
One of the most widely accepted frameworks is the \ac{cobit}, |
422 |
published free online by the \ac{isaca}. This set of guidance |
423 |
documentation includes the framework, high-level and detailed control |
424 |
objectives, audit guidelines, management guidelines and an |
425 |
implementation guide together with a toolkit, to support executives |
426 |
with \ac{it} governance \cite{COBIT, Guldentops2003}. De Haes and Van |
427 |
Grembergen \cite{HaesGrembergen2004} suggest complementing \ac{cobit} |
428 |
with the \ac{itil}, a framework maintained by the \ac{ogc} in the |
429 |
United Kingdom. It is significantly oriented towards service |
430 |
management, such as payroll infrastructures, and comprises of best |
431 |
practice documentation material on strategy, design, transition, |
432 |
operation and continual service improvement |
433 |
(\url{http://www.itil-officialsite.com}). |
434 |
|
435 |
Maturity models are also useful to benchmark performance and alignment |
436 |
against other standards. Some maturity models are included in, for |
437 |
instance the management guidelines of \ac{cobit}, or are developed |
438 |
separately by researchers or institutions such as the \ac{it} |
439 |
Governance Institute \cite{HaesGrembergen2004, Luftman2003}. Simonsson |
440 |
et al \cite{Simonsson2010} carried out 35 case studies to examine the |
441 |
correlation between \ac{it} governance maturity and \ac{it} governance |
442 |
performance. The strongest positive correlation to \ac{it} governance |
443 |
performance was exhibited by the internal \ac{it} structure, clear |
444 |
organizational structures and relationships, mature quality management |
445 |
and cost allocation. Minimal correlation was found with the maturity |
446 |
of project management, service level management, performance and |
447 |
capacity management. |
448 |
|
449 |
Taking the view of \ac{it} as a service provider to the rest of the |
450 |
organisation, the Balanced Scorecard can be used to control \ac{it} |
451 |
performance in areas such as user satisfaction, business contribution, |
452 |
operational excellence and future orientation |
453 |
\cite{HaesGrembergen2004, Grembergen2000}. In addition, by linking the |
454 |
objectives of the business Scorecard to the \ac{it} Scorecard, there |
455 |
is greater strategic alignment and capability exploitation |
456 |
\cite{HaesGrembergen2004, Grembergen2000}. |
457 |
|
458 |
Other related measurement and control tools include Service Level |
459 |
Agreements, strategic alignment frameworks and information economics |
460 |
models \cite{HaesGrembergen2004, Karten2004, WeillRoss2004b}. Weill |
461 |
and Ross add to these the \ac{it} investment approval process, the |
462 |
architectural exception process, chargeback, project tracking and the |
463 |
formal tracking of business value and benefit realisation |
464 |
\cite{WeillRoss2004b}. A review of such \ac{it} governance tools can |
465 |
be found in \cite{Larsen2006}. It should be noted though that these |
466 |
tools cannot provide universal solutions, but need to be assessed and |
467 |
adapted against the specific context of implementation. Learning |
468 |
achieved through iterative modifications is of great significance |
469 |
\cite{Weill2004}. |
470 |
|
471 |
\paragraph{Relational Mechanisms} |
472 |
|
473 |
Structures and committees, and processes and control frameworks, do |
474 |
not guarantee effective \ac{it} governance \cite{Peterson2004}. |
475 |
Organisations employ relational mechanisms to improve lateral |
476 |
communication and understanding between corporate executives, \ac{it} |
477 |
and business people \cite{HaesGrembergen2004}. The purpose is to find |
478 |
integrative solutions combining expert and tacit knowledge through |
479 |
participation and collaboration across boundaries. This type of |
480 |
relational integration is facilitated through direct informal contacts |
481 |
and negotiations, common locations and ``virtual meeting points'', |
482 |
lobbying, joint performance incentives and shared learning |
483 |
\cite{Peterson2004}. |
484 |
|
485 |
Weill and Ross have focused on the communication aspect of relational |
486 |
mechanisms \cite{WeillRoss2004b}. They have found that formal |
487 |
communication of \ac{it} governance mechanisms relates to more |
488 |
effective governance (while informal communication is not associated |
489 |
with governance effectiveness). Some examples of such communication |
490 |
devices include senior management announcements, communication between |
491 |
and within formal committees to coordinate efforts, web-based portals |
492 |
and intranets. Ownership in the sense of discussing \ac{it} governance |
493 |
in the office of the \acs{cio} or a devoted \ac{it} governance office are |
494 |
deemed equally important. Last but not least, a significant amount of |
495 |
time is spent to guide managers through \ac{it} architecture in order |
496 |
to increase acceptance and conformity to \ac{it} governance |
497 |
arrangements. |
498 |
|
499 |
Robbins proposes a more inclusive approach to \ac{it} governance, |
500 |
involving external parties such as partners, service providers and |
501 |
communities of practice \cite{Robbins2004}. In certain arrangements |
502 |
such as outsourcing this outside input to decision-making is sought |
503 |
regularly already \cite{WeillRoss2004b}. |
504 |
|
505 |
\begin{table} |
506 |
\caption{Structures, Processes and Relational Mechanisms \cite{HaesGrembergen2004, Grembergen2003, Peterson2004, WeillRoss2004b}} |
507 |
\begin{center} |
508 |
\begin{tabular}{ | p{2.5cm} | p{2cm} | p{2cm} | p{2,4cm} | p{2cm} |} |
509 |
\hline |
510 |
& \textbf{Structures} & \textbf{Processes} & \multicolumn{2}{c|}{\textbf{Relational Mechanisms}} \\ \hline |
511 |
|
512 |
\textbf{Tactics} & \ac{it} executives and accounts & Strategic \ac{it} decision-making & Stakeholder participation & Strategic dialog \\ |
513 |
& Committees and councils & Strategic \ac{it} monitoring & Business / \ac{it} partnerships & Shared learning \\ \hline |
514 |
\textbf{Mechanisms} & Roles and responsibilities\medskip |
515 |
|
516 |
\ac{it} organisation structure\medskip |
517 |
|
518 |
\acs{cio} on board\medskip |
519 |
|
520 |
\ac{it} strategy committee\medskip |
521 |
|
522 |
\ac{it} steering committee & Strategic information systems planning\medskip |
523 |
|
524 |
Balanced (\ac{it}) scorecards\medskip |
525 |
|
526 |
Information economics\medskip |
527 |
|
528 |
Service level agreements\medskip |
529 |
|
530 |
\ac{cobit} and \ac{itil}\medskip |
531 |
|
532 |
\ac{it} alignment / governance maturity models & Active participation by principal stakeholders\medskip |
533 |
|
534 |
Collaboration between principal stakeholders\medskip |
535 |
|
536 |
Partnership rewards and incentives\medskip |
537 |
|
538 |
Business/\ac{it} colocation & Shared understanding of business/\ac{it} objectives\medskip |
539 |
|
540 |
Active conflict resolution\medskip |
541 |
|
542 |
Cross-functional business/\ac{it} training\medskip |
543 |
|
544 |
Cross-functional business/\ac{it} job rotation\\ \hline |
545 |
\end{tabular} |
546 |
\end{center} |
547 |
\label{default} |
548 |
\end{table} |
549 |
|
550 |
The mechanisms mentioned above should be simple and unambiguous, |
551 |
transparent and suitable to engage appropriate individuals. The design |
552 |
of mechanisms should employ a mix of techniques from all three types |
553 |
and implement these at multiple organisational levels, use less but |
554 |
more effective decision-making structures focusing on alignment, while |
555 |
overlapping membership and clear accountability patterns should be |
556 |
considered \cite{WeillRoss2004b}. |
557 |
|
558 |
\section{Effective Governance} |
559 |
|
560 |
Weill and Ross suggest top for-profit governance performers have more |
561 |
managers who are able to accurately describe the role of \ac{it} |
562 |
governance in their organisation \cite{WeillRoss2004b}. Senior |
563 |
management engages more effectively through structural, relational and |
564 |
communication mechanisms. Objectives for \ac{it} investment are |
565 |
clearly articulated and communicated, through generally stable \ac{it} |
566 |
governance arrangements over time. They also observe more formal |
567 |
architecture exception processes, together with diversified business |
568 |
strategies. |
569 |
|
570 |
High-level commitment and communication emerge as significant elements |
571 |
of contemporary \ac{it} governance. Departing from an earlier focus on |
572 |
loci of control, Peterson concludes that collaboration is the |
573 |
foundation of effective \ac{it} governance, ``where the need for |
574 |
distinct competencies is recognized, developed, and shared adaptively |
575 |
across functional, organizational, cultural, and geographic |
576 |
boundaries'' \cite{Peterson2004}. |
577 |
|
578 |
%%% Local Variables: |
579 |
%%% mode: latex |
580 |
%%% TeX-master: "governance" |
581 |
%%% End: |