icegov2012 proceedings
icegov2012 proceedings
icegov2012 proceedings
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
are necessary to obtain a uniformity regarding functionality, as<br />
well as a desired quality level [4]. Reviewing available literature<br />
on the subject under study is an essential part of developing<br />
guidelines which can be based on experience - either practical or<br />
theoretical [45]. We summarize our guidelines in Table 1.<br />
3.2 IT Governance/Management Main Areas<br />
Many frameworks exist and each one calls their processes/areas<br />
with different names which culminate in overlap and contribute to<br />
organization confusion as well as waste of resources [35].<br />
Therefore a formalization of ITG and ITM areas is needed. We<br />
summarize the ITG and ITM areas in Table 2.<br />
4. EVALUATION<br />
In order to validate our artefacts, besides the complete literature<br />
review and despite the little empirical work concerning ITG in the<br />
literature, we also mapped the artefacts with current theories and<br />
Table 2. Main ITG/M Areas summary<br />
Main Area Description Topics/subjects Literature Reference<br />
Strategy<br />
Management<br />
Service<br />
Management<br />
Resource<br />
Management<br />
Risk<br />
Management<br />
Development<br />
Management<br />
Architecture<br />
Management<br />
Project<br />
Management<br />
Quality<br />
Management<br />
Investment<br />
Management<br />
Outsourcing<br />
Management<br />
Support<br />
Management<br />
Compliance<br />
Management<br />
Improvement &<br />
Innovation<br />
Management<br />
Table 1. ITG Guidelines Summary<br />
Guidelines About what? What do we need? Literature Reference<br />
1 Where do we want to be? BIT objectives and vision<br />
BIT strategies<br />
BIT goals<br />
[34][41][27][48][16][12][43]<br />
[38][15][46][33]<br />
2 Where are we now?<br />
BIT alignment, maturity,<br />
BIT strategic plan<br />
Core competences, assess IT department and maturity,<br />
assess enterprise, assess BIT alignment<br />
[34][41][27][48] [16][12][43]<br />
[38][15][46][33]<br />
3 What do we need to get there?<br />
Structures, processes, and<br />
mechanisms<br />
Collect information about contingency factors of the<br />
organization, define the necessary mechanisms<br />
[1][13][9][29] [8][46][33] [2][22]<br />
4 How do we get where we want to be? IT processes Materialize the plan defined in the previous step [41][48][12] [44][43][15] [46][2]<br />
5<br />
How do we know we have arrived<br />
there?<br />
Metrics<br />
Measurements<br />
IT Balance Scorecard<br />
Enterprise Balance Scorecard<br />
[1][41][27][48] [44][8][39]<br />
[46][33][30]<br />
6<br />
Are we following the market’s best<br />
practices?<br />
Best practices<br />
Frameworks<br />
Be aware of best practices frameworks and standards [28][17][12] [8][11]<br />
7<br />
How do we know we are doing it<br />
right?<br />
Compliance<br />
Audit<br />
Audit regularly<br />
Internal and external compliance<br />
[41][36][24]<br />
8 How do we keep it on track?<br />
Improvement<br />
Innovation<br />
Collect information to I&I in order to prepare organization<br />
for current and future challenges<br />
[16][38][15] [2][24][19]<br />
Responsible for business/IT objectives and alignment, contingency<br />
factors, and other reasons pointed out as possible differentiators of ITGI.<br />
Responsible for service definition, service catalogue, service portfolio,<br />
service levels, and other subjects about provided services.<br />
Accountable for the correct management of the organization’s resources,<br />
like people, technology, applications, etc. Training is included.<br />
Responsible for the correct assurance of the business’ continuity by<br />
anticipating and preventing possible risks of the IT department, which are<br />
correlated with business risk.<br />
Responsible for the design and development of software as well as its<br />
maintenance.<br />
Responsible for the design of the necessary architectures for the good<br />
functioning of the IT department.<br />
Accountable for the management of the entire cross IT department<br />
project, all kinds of projects.<br />
Responsible for the assurance of the required procedures to guarantee<br />
functionality and provide services and products with the required quality.<br />
In charge of assuring the correct financial functioning of the IT<br />
department and of providing budget, costs, and financial plans.<br />
Manages all the aspects concerning outsourcers, as contracts, service<br />
levels, relations, etc.<br />
Responsible for user interaction and mainly keeps user satisfaction<br />
Accountable for the control of internal and external regulations, as well as<br />
report and measurement.<br />
Responsible for the management of the improvements and innovations<br />
that can be required or provided by the entire IT department.<br />
321<br />
also used the results of a series of experts interviews.<br />
We used structured interviews covering a diverse sample of<br />
organization types, sizes, and roles. By space limitations we won’t<br />
present interviewees details. The respondents have a lot of<br />
experience in the area. To support the interviews, we designed a<br />
questionnaire to lead the discussion. In the interviews, the<br />
majority of the questions weren’t open-response questions<br />
because of the nature of the information we need to elicit. The<br />
interviews were conducted over a one month period. Each session<br />
lasted from 60 to 90 minutes and was transcribed into digital data.<br />
We performed nine interviews with ITG experts who have<br />
strategic alignment and ITG knowledge in their organizations.<br />
Seven interviews were performed in Portugal and two in Ireland<br />
by Skype. The interviewees were 3 consultant organizations (1, 2<br />
and 7) and 6 non-consultant (3, 4, 5, 6, 8 and 9) organizations.<br />
Table 3 shows a summary of the results. We used “yes/no” to<br />
Demand Management, Market analyze,<br />
IT/Business strategy plan/definition/alignment<br />
Service Level Management<br />
Service Portfolio<br />
Human resource, Hardware, Software, Capacity<br />
and Configuration Mngt., Information Mngt.<br />
Disaster recovery, Backups and security<br />
Management, Business continuity, Identity and<br />
access Management<br />
Application Management<br />
Application maintenance<br />
IT architecture and engineering<br />
Infrastructure Management<br />
Project Portfolio Management<br />
Project Management<br />
Quality control<br />
Product Quality Management<br />
Portfolio and Value Mngt., Define budgets,<br />
Manage costs<br />
Manage contracts<br />
Control outsourcers<br />
Incident and Problem Mngt.<br />
Service desk<br />
[41][28][48][12][47]<br />
[39][15][46][2][11][19]<br />
[30]<br />
[34][24][26]<br />
[13][41][28][47][39][2]<br />
[19][30]<br />
[29][48][15][46][2]<br />
[11][30]<br />
[50][12][2]<br />
[13][41][12][47][39]<br />
[43][15][2]<br />
[13][41][16][12][39]<br />
[15][30]<br />
[42][40][7]<br />
[14][29][48][16][12]<br />
[15][39][46][2][24][30]<br />
[47][39][15][2][24]<br />
[20][3][10][25]<br />
Audit, Policy and Report Mngt., Internal Control [44][15][24]<br />
Analyze reports and options<br />
Prospection, Improvement and Innovation,<br />
Change Mngt<br />
[39][39][15][2][24][19]<br />
[30]