ITIL Planning : Contents Articles Service Catalog Corporate governance of information technology Information….
Contents Articles Service Catalog Corporate governance of information technology Information Technology Infrastructure Library IT service management Method engineering Axios Systems Competitive Engineering Configuration management Fagan inspection IBM Tivoli Unified Process (ITUP) Information Services Procurement Library ITIL Planning to implement service management Market analysis for product software Marketing decision support systems Method Framework for Engineering System Architectures Technical architecture Corporate Governance of ICT AS 8015 Autonomic Networking Certified in the Governance of Enterprise IT Chief web officer COBIT Information technology controls Data custodian Data governance Data steward Data visualization Governance Interoperability Framework ISO/IEC 38500 Ministry of Communications and Information Technology (Egypt) Project governance Public ROI Risk IT SOA Governance 1 2 5 21 23 29 30 30 35 38 44 56 63 66 66 67 72 73 73 79 80 82 84 89 90 93 94 98 100 101 105 109 110 115 TickIT Total cost of ownership Val IT Web content lifecycle Website governance 116 118 120 123 127 References Article Sources and Contributors Image Sources, Licenses and Contributors 130 132 Article Licenses License 133 Service Catalog 1 — In practice, descriptions of operational items often already present.
It is important to make the distinction between functional and quality properties.
Descriptive item A descriptive item captures knowledge about the target domain.
They can be used to describe business organisations, business processes, information services et cetera.
ISPL gives guidance on describing descriptive items by providing a descriptive item profile in which all properties of the descriptive item can easily be ordered. External links • ISPL Homepage  • Information Services Procurement Group (in Dutch)  References  This article is a part of the Method Engineering Encyclopedia of the Utrecht University.  http:/ / projekte.
De/ ISPL/  http:/ / www.ispg.
Et al. (2003), ‘Procurement, projecten en processen in de praktijk, De samenhang tussen ISPL, PRINCE2 en ITIL’, IT Beheer Jaarboek 2003, chapter 5.4 (in Dutch) 2.
And Verhoef, editors (1999), ‘Managing Acquisition Processes’, Information Services Procurement Library, ten Hagen & Stam, Den Haag, The Netherlands, ISBN 978-90-76304-81-6 3.
And Verhoef, editors (1999), ‘Managing Risks and Planning Deliveries’, Information Services Procurement Library, ten Hagen & Stam, Den Haag, The Netherlands, ISBN 978-90-76304-83-0 4.
And Franckson (1999), ‘Risk Management for IT in the large’, CAiSE’99, LNCS 1626, pp. 57–72 5.
And Verhoef, editors (1999), ‘Specifying Deliverables’, Information Services Procurement Library, ten Hagen & Stam, Den Haag, The Netherlands, ISBN 978-90-76304-82-3 ITIL Planning to implement service management 56 ITIL Planning to implement service management The planning to implement service management is a set in the Information Technology Infrastructure Library (ITIL) framework.
This set is about the alignment of business needs and IT provision requirements.
Besides, this set describes how to implement or improve IT Service Management within an organization and it describes steps to ensure that business needs and IT provision requirements will be met.
Furthermore, the planning to implement service management set is mainly focused on the service management processes, but also generically applicable to other ITIL sets.
An approach to implement or improve service management is the Continuous Service Improvement Programme (CSIP).
A CSIP is defined as: “an ongoing formal programme undertaken within an organization to identify and introduce measurable improvements within a specified work area or work process.” OGC_book All the activities within a CSIP regarding one single improvement can be visualized generically by using the meta-modeling technique.
This results in a process-data diagram (figure 1), which does not describe the continuous improvement activity of the programme.
The process-data diagram shows the relationship between processes and artifacts and this diagram consists of two integrated diagrams.
The left-hand side of the process-data diagram describes the activities (processes) and is based on the UML activity diagram.
The right-hand side describes the data (artifacts) and is based on the UML class diagram.
Meta_modeling The table of concepts and the activity description regarding the process-data diagram can be found in the paragraph Process-data diagram descriptions.
The process-data diagram shows the following activities: • • • • • create vision analyze organization set goals implement IT service management measure goals First, a vision has to be created and the IT and business strategies should be aligned.
The second step consists of analyzing the organization and its current position.
In this step an answer has to be found on the question ‘where are we now?’ The following step is about setting goals and priorities regarding the improvement process.
The fourth step is the improvement of the service provision itself and during the fifth and final step the improvement will be measured to examine whether the goals have been met. ITIL Planning to implement service management 57 The planning to implement service management set Every activity in the planning to implement service management set, as depicted in figure 1, will be further explained. Create vision As figure 1 shows, the first step that needs to be taken in the process is creating a vision statement for a CSIP.
The vision statement describes the aim and purpose of the CSIP on a high level and should align the different strategies of business and IT.
Additionally, the vision statement should be well communicated to the stakeholder, to create commitment and buy-in for the CSIP. Figure 1: process-data diagram Analyze organization After having created a vision an IT organization should analyze itself, wherein the question ‘where are we now?’ has to be answered.
A useful technique to determine the current position is the IT organization growth model.
This model determines the maturity level of the IT organization and is based on the Process Maturity Framework (PMF), as well as on the Capability Maturity Model (CMM).
The maturity of the organization will be determined in terms of vision and strategy, steering, processes, people, technology and culture.
It is also required to understand who the stakeholders are, because stakeholders have an impact on the CSIP.
This can be achieved by defining, identifying and mapping the stakeholders.
Additionally, the specific needs of the stakeholders have to be identified and this can result in a stakeholder assessment report.
The third step of the organizational analysis in figure 1, consists of assessing the current report and measurement system.
Knowing the current way of using and producing reports, facts and figures gives insight in how well the organization is steered, but it also provides information about the next activity ‘set goals’.
The last step in analyzing the organization is conducting benchmarks.
A benchmark is a useful management technique to improve performance.
In a benchmark different parts of the organization can be compared, like units or processes.
But also organizations as a whole can be compared in a benchmark.
It is important to determine whether a service management process should be benchmarked or not.
A focus on the relevant service management processes is essential.
The results of the benchmarks can result in the identification of gaps. ITIL Planning to implement service management 58 Set goals The next activity in the CSIP is about the agreement between business and IT regarding the required and expected future roles and characteristics of the organization, which are based on the current maturity of the organization.
The first step that needs to be taken is the creation of a business case to describe the added value and the justification of the CSIP.
The business case is determined by the current maturity of the organization and the organizational strategy.
A stakeholder assessment, conducted in the previous activity, can also be a contribution to the focus on the results and the aim of the improvement programme.
Furthermore, risks should be identified and managed.
An approach to risk management should be applied during the CSIP.
Mainly the risks related to the business vision, existing processes and the environment and business constraints should be managed to reduce the effects of those risks.
After having created a business case, a gap assessment report should be completed.
A gap assessment report is used to compare the current state with the future state of the organization and this results in gaps to overcome (‘where do we want to be’).
It provides information about gaps, risks and the prioritization on where to start.
Once a gap assessment report has been completed, there is a need for understanding and clarity.
That means that the problems and the following steps have to be presented to the key stakeholders, to establish creditability for the assessment and support concerning the change.
The following step is the creation of a plan for quick wins.
A quick win is an early success during an improvement programme.
In the plan for quick wins short term wins should be identified and attained to keep the improvement programme running and to keep the commitment level high during the improvement programme.
The last step is setting the goals regarding the improvement programme in relation to the earlier defined stakeholder needs.
A management tool for setting goals and measuring performance is the balanced scorecard. Implement IT service management The first thing to consider regarding implementing or improving service management is finding an answer on where to start (‘which service management process?’).
Before identifying a process that need to be improved, the first condition that needs to be fulfilled is that the organization should have documented its current and desired state, which includes a completed gap assessment report. ‘Where to start’ also depends on the level of maturity and the strategic goals of the organization.
Besides these dependencies, it is important to understand the interrelationships between all the IT Service Management processes.
Another aspect which should be taken into consideration during the improvement programme is creating awareness of the change.
This can be done by making a communication plan, which will give an explanation about the IT policy to the stakeholders.
The next thing to consider is how the changes are going to be achieved.
Achieving changes requires a reliable change programme.
To prevent a CSIP from missing its intended goals the OGC recommends  the approach from J.P.
Kotter, called: ‘Eight steps to transforming your organisation’ in combination with project management such as PRINCE2.
The main reason for using this approach in combination with regular project management, is that this approach also takes the softer sides of change into account like resistance to change and creating commitment.
Kotter studied more than 100 companies with regard to their transformations in the past years.
This has resulted in eight main reasons why transformations succeed.
The duration of the studied transformations was quite long, about six to eight years.Transformation_fail The eight main reasons why transformations succeed are transformed into eight steps. 1.
Creating a sense of urgency 2.
Forming a guiding coalition 3.
Creating a vision 4.communicating the vision ITIL Planning to implement service management 5. 6. 7. 8. ‘Empowering’ to act on the vision Planning for and creating quick wins Consolidating improvements and producing more change Institutionalizing the change 59 These eight steps can be applied equally to a service management improvement programme.
The culture of the organization is a main issue to be taken into account during organizational change, because organizational change could support an implementation, and it can as well lead to resistance.
For that reason the organizational culture should be managed in order to avoid problems like resistance.
A critical success factor for a CSIP is the clear definition of accountability, roles and responsibility in relation to the new processes and the existing organizational structure.
New processes and working practices do often not fit within the existing organizational structure, because processes are often cross functional.
In other words, processes may run through the whole organization.
In this way new processes and working practices may introduce new roles, which may overlap the existing organizational structure.
The last aspect that has to be taken into account regarding the implementation of IT service management is training.
Training can contribute to a higher quality of service management and it can also lead to more productive and responsive employees.
Before setting up a training programme, questions like who to train, when to train, how to train and what to train should be answered.
For ITIL training see: ITIL Certification. Measure goals After the completion of each improvement process a Post Implementation Review (PIR) should be conducted to indicate if the objectives have been achieved.
This can be done by making a comparison between the achievement of the improvement and the goals earlier set in the programme.
When the results of the PIR are confirmed, new targets regarding improvement should be defined.During the improvement programme the Key Performance Indicators (KPIs), which are earlier created during setting the goals as a part of the balanced scorecard, are needed to be constantly monitored to confirm the PIR.
Also, the improvement of the customers perception (customer KPIs) during the CSIP needs to be surveyed.
This can be done by conducting a regular statistical survey regarding customer satisfaction, also called a Customer Satisfaction Survey (CSS). Process-data diagram descriptions Table of concepts Concept Assessment Balanced Scorecard Definition The classification of someone or something with respect to its worth.  An aid to organizational Performance management.
It helps to focus, not only on the financial targets but also on the internal processes, customers, and learning and growth issues.  A report that contains a comparison of performance between different organizations or between different units within an organization.  Information that describes the justification for setting up and continuing a PRINCE2 project.
It provides the reasons (and answers the question ‘Why?’) for the project.
It is updated at key points throughout the project.  A plan that describes how the IT policy will be explained to the stakeholders and as a result of this, it will create awareness in the organization.  The addition, modification or removal of the whole of the ideas, corporate values, beliefs, practices, expectations about behavior and daily customs that are shared by the employees in an organization.  Benchmark report Business case Communication plan Cultural change ITIL Planning to implement service management 60 Decision document A document which gives an answer on the question ‘Where should I start’ and depends on the completeness of the assessments conducted in the previous steps, like determining the maturity level of the organization, service processes and strategic goals.  A change management model, consisting of eight steps.  Gap analysis naturally flows from benchmarking or other assessments.
Once we understand what is the general expectation of performance in industry, we can then compare that with current capabilities, and this becomes the gap analysis.  The state of affairs that a plan is intended to achieve and that (when achieved) terminates behavior intended to achieve it.  A model that determines the current maturity of the IT organization in terms of vision and strategy, steering, processes, people, technology and culture.  The active employment of particular sets of measurement recommendations.  Measurable element of a service process or function.  Organizational change has two dimensions.
The first, OC involves a transformation of organizations between two points in time.
The second dimensions concerns the way the transformation occurs.  Responsibilities, authorities and relations organized in such a way as to enable the organization to perform its functions.  One or more reviews held after project closure to determine if the expected benefits have been obtained.  Eight step model Gap assessment report Goal IT Organizational growth model Measurement framework Metric Organizational change Organizational structure — Risk management Service improvement SM (service management) vision statement Stakeholder assessment Stakeholder goal Strategy Training programme Table 1: table of concepts with definitions References of table of concepts 1.
Office of Government Commerce (OGC). (2002).
Planning to Implement Service Management.
London : The Stationery Office. 2.
Raynor, M.E. (1998).
That vision thing: Do we need it?.
Long range planning, 31, 3. 3.
Folan, P., Browne, J. (2005), A review of performance measurement: Towards performance management.computers in industry, 56, 7. 4.
Mintzberg, H. (1978).
Patterns in Strategy Formation.
Management Science, 24, 9. 5.
WordNet Search – 2.1. (2006).
Retrieved March 8, 2006 from Princeton Website: http://wordnet.princeton.edu/ perl/webwn?s=goal 6.
WordNet Search – 2.1. (2006).
Retrieved March 8, 2006 from Princeton Website: http://wordnet.princeton.edu/perl/webwn?s=assessment ITIL Planning to implement service management 7.
Best practice. (2006).
Retrieved March 8, 2006 from OCG Website: http://www.get-best-practice.co.uk/glossary.aspx?product=successfulprojects 8.
Barnett; Glenn R.
Modeling Internal Organizational Change.
Annual Review of Sociology, 21, pp. 217-236. 9.
Egan, R.W., Fjermestad, J. (2005).
Change and Resistance: Help for the Practitioner of Change.
Proceedings of the 38th Hawaii International Conference on System Sciences – 2005 10.
Definitions of Terms. (2006).
Retrieved March 8, 2006 from Balanced Scorecard Institute Website: http:// www.balancedscorecard.org/basics/definitions.html 11.
Development of Quality Assurance System in Higher Education(QUASYS). (2001).
Retrieved March 10, 2006 from University of Zagreb Website: http://www.unizg.hr/tempusprojects/glossary.htm 61 Activity description Activity Create vision Sub-activity Description Creating a VISION STATEMENT for service management which fits with the organization STRATEGY.
Evaluate current position Evaluating the current position can be done by assessing the , IT ORGANIZATION GROWTH MODEL.
This gives an indication of the maturity of the organization.
Assess stakeholders Defining and analyzing the stakeholders and their needs, which results in a STAKEHOLDER ASSESSMENT.
Assessing the current report and measure system results in a MEASUREMENT FRAMEWORK. Analyze organization Assess current report and measure system Conduct benchmark Benchmarking results in a few BENCHMARKS, which can be used as a steering instrument and can be categorised in four categories, which are not further explained.
The IT ORGANIZATION GROWTH MODEL and STRATEGY determine the BUSINESS CASE (current position) which describes not only measurable targets, but also the costs, effort, benefits sense of urgency etc.
Managing risks results the artifact RISKMANAGEMENT, which is required by the BUSINESS CASE.
BENCHMARKS lead to the analyses of gaps to determine the start.
This activity results in a GAP ASSESSMENT REPORT.
A PLAN OF QUICK WINS is based on the GAP ASSESSMENT REPORT and is needed to convince the stakeholders of the changes/implementation.
Results in STAKEHOLDER GOALS, which is a generalization of GOAL Set goals Create business case Manage risks Conduct gap analysis Create plan for quick wins Set stakeholder goals ITIL Planning to implement service management 62 Implement ITSM Select starting point Selecting a starting point can be done by creating a DECISION DOCUMENT, which initiates ORGANIZATIONAL CHANGE.
The decision to start the implementation is based on the completeness of the previous activities see: Non-described rule Adapt results previous activities Create awareness Awareness can be achieved by creating a COMMUNICATION PLAN that supports ORGANIZATIONAL CHANGE Managing org.
Change results in ORGANIZATIONAL CHANGE and can be done by using the EIGHT STEPS MODEL combined with PROJECT MANAGEMENT Managing cult.
Change results in the artifact CULTURAL CHANGE and is required by ORGANIZATIONAL CHANGE.
CULTURAL CHANGE encloses the soft side of the CHANGE.orgANIZATIONAL CHANGE involves the ORGANISATION STRUCTURE, which may change aspects like authority, tasks, functions, roles etc.orgANIZATIONAL CHANGE requires ITIL training (TRAINING PROGRAMME).
Which training is needed, depends on the change.
This activity results in a POST IMPLEMENT.
REVIEW, which includes a comparison of the set and achieved goals/targets Manage organizational change Manage cultural change — Measure goals Table 2: description of activities and sub-activities Non-described rule • This activity will be started if no starting point can be selected.
In that situation, this activity will result in an adaptation of the already delivered incomplete products, such as a gap assessment report. References 1.
Office of Government Commerce (OGC). (2002).
Planning to Implement Service Management.
London : The Stationery Office. 2.
Van de (2005).
WEM: A design method for CMS-based web implementations.
UU WINFI Informatica en Informatiekunde. 3.
Kotter, J.P. (1995).
Why transformation efforts fail.
Harvard Business Review, 59–67 In: Journal of Product Innovation Management. 13, 2 , March 1996, 170 4.
Hochtstein, A., Tamm, G., Brenner, W. (2005).
Service oriented IT management: benefit, cost and success factors.
Proceedings 13 European conference on information systems (ECIS 2005), Regensburg, Germany. External links • • • • • • The OGC website  IT Service Management Forum  The ITIL definition site  The ITIL Forum  The OGC successful delivery toolkit  OGC get best practice  ITIL Planning to implement service management 63 References      http:/ / www.itsmf.com/ http:/ / www.itil.org.
Uk/ http:/ / www.itilcommunity.com http:/ / www.ogc.
Uk/ sdtoolkit/ deliveryteam/ briefings/ ITIL/ index.
Html http:/ / www.get-best-practice.
Uk Market analysis for product software Market analysis for product software consists of a number of techniques that allow an organization to collect and disseminate information from their external environment of software products for use in determining their market strategy and actions.
For example, market analysis helps to determine critical strategies for new software products such as time-to-market length, creating product differentiation, creating and preserving supplier credibility, developing effective distribution channels, forming relationships with large customers, and managing market efforts (Igel & Islam, 2001).
This topic has its roots in marketing discipline.
Many types of market research techniques are used to gather this information.
Market analysis plays a large part in explaining the current situation of a marketing plan.
Marketing is very important to new product development because software products have a short average lifespan of five years and incur 75% of the costs during the research and development phase (Atkinson et al., 2004).
Therefore, including market analysis information early on in the product lifecycle can ensure resources are not wasted.
It’s a wide field so this article is a sample of scientific work that has linked the fields of marketing and product software.
This consists of research in the fields of general market, customer, and competitor analysis which can be seen as processes that are hierarchically grouped under market analysis in the meta-process model from the figure below.
There are many processes that can be used for each of these three processes to acquire information from the market.
This article only lists a selected few for each. General Market Characteristics for Product Software Analysis of general market characteristics should lead to information about the market such as definition, size, trends, and market segmentation.
This analysis is needed to help develop and maintain marketing strategies for product software and overall business strategies.
The covered methods and techniques to obtain this information are Porter’s five forces model, risk analysis, marketing intelligence, and marketing decision support systems.Porter’s five forces analysis is useful for software since it highlights many important factors that will be discussed in customer and competitor analysis such as switching costs, brand equity, product differentiation, and price of total purchase. • risk analysis for product software*marketing intelligence • marketing decision support systems Customer analysis for product software Customer analysis is needed to predict behavior and create demand forecasts for product software.
It is also necessary in the development of new products to help select the most profitable choice.
To analyze customers, aspects such as demographics, buying motivation, and expectations are studied.
Besides basing behavior on software only, customers also look at the network externalities from software packages, such as manuals, add-ons, and training courses, to make purchase decision.All of these subjects are useful for determining target groups (also known as market segments).
Moreover, this information helps determine the optimal solution to the tradeoff between time-to-market and quality.
Market analysis results are important to help establish an optimal point between the tradeoff of time-to-market and — 129 External links • Web Governance LinkedIn group (http://www.linkedin.com/groups?home=&gid=1812891) • Usability.gov (http://www.usability.gov/) • Webcontent.gov (http://www.usa.gov/webcontent/) Article Sources and Contributors 130 Article Sources and Contributors Service Catalog Source: http://en.wikipedia.org/w/index.php?oldid=409386997 Contributors: Active Banana, Akramer2, Alespb, Charles T.
Betz, Dwmcnabb, Gusgregory, Isolde98, Jmgendron, Jonik, K2heikkila, KnightLago, Lpgeffen, MGS1978, Pmgnet, Robertmcneill, SDrugger7, SWAdair, Serviceguy, West81, 48 anonymous edits Corporate governance of information technology Source: http://en.wikipedia.org/w/index.php?oldid=419570209 Contributors: A.
B., AMPJA, Adrius42, Alanpc1, Andyjsmith, Ash, Beland, Brandguru, CelloerTB, Charles T.
Betz, China Crisis, Cirrus Editor, Cnilep, Coreygorman, Cverlinden, DaddyAndy, Dandan1, David.t.bath, Djamund, Edcolins, Ehheh, Everton1984, Frank Kai Fat Chow, Gforcewebdesign, GilbertoSilvaFan, Hairhorn, HectorM, Hervegirod, IT2BE, IvanLanin, JEH, Joe3600, Jpbowen, Juanpablosoto, Juster84, Jzupan, Khalid hassani, Kim Maes 23, Kimchi.sg, Kitdaddio, Kku, Kubanczyk, Kuru, LMPerry, LOL, Leoplus, Lumos3, Mantagroup, Marsim, Mgillett, Mmiriam, Moonriddengirl, NSR, Nancy, Nickcarr, Olivier.bally, Ps07swt, Randomalious, Rcardenas, Renaultal, Rich Farmbrough, Richard Bartholomew, RichardVeryard, Rkaseler, Rodecode, Ronz, Sadads, Saurabhdutta, Singhalawap, Steverapaport, Supadawg, TScabbard, Technopilgrim, Televi, TheTito, Tonywhite68, Vaceituno, Van helsing, Wayraw, Wiki3 1415, Xerstau, Yogishpai, 118 anonymous edits Information Technology Infrastructure Library Source: http://en.wikipedia.org/w/index.php?oldid=425499949 Contributors: A.
B., A3RO, AMe, Aberdeenwaters, Acm, Acpt22, ActiveSelective, Adrian.benko, Aerotheque, Aitias, Akbradford, Alanpc1, AlephGamma, Alimozcan, Allen4names, Andrea kempter, Andrzejkrajewski, Ankur onlyur, Anna Frodesiak, Antidoter, Aranel, AreJay, Ash, Aussieaubs, Avr, B Fizz, Barinder hothi, Baseball Bugs, Beland, BenAveling, BibTheLion, Bibikoff, Binarygal, Black Kite, Blehfu, Blroques, Bobrayner, Boekelj, Brandguru, Brandon, Brianj hill, Butrain, CALR, CPrehn, Cain Mosni, Can’t sleep, clown will eat me, Canderson7, Captain panda, Cblanquer, Ccordray, Cgroberts, Charles T.
Betz, Chowbok, Chris.fischer, ChrisCork, ChrisG, Chzz, Cinfosys01, Cjdavis, Cmdrjameson, Coherers, Cometstyles, Credible58, Cuttysc, Damon, Dancter, Danialshazly, DanielVonEhren, Danielgwj, Darinkeir, Darth Panda, DaveWFarthing, Davebremer, David Biddulph, David.T.Bath, Davidbspalding, Dennisc68, Dia^, Discospinster, Dnblack, Dnicolaid, Docu, Doug Alford, Dpv, DragonflySixtyseven, Dritil, Eahiv, Edholden, Ehheh, Emesis, Epbr123, Estherschindler, Eugene-elgato, Evilmn, Excirial, Firsfron, Fortdj33, Fox, Frank, Freek Verkerk, Fstop22, Fudoreaper, Fustbariclation, Gaius Cornelius, Gcanyon, GerardM, Ghewgill, Ghw777, Goonies, Guigui NYC, Haakon, Halfgoku, Hengeloov, Hennek, Herbys, Hkroger, Hu12, Hulmem, IBM Press, IDefx, IET-Solutions, IIVQ, ITServiceGuy, Iness it, Itbeme, Itildude, Itsgeneb, IvanLanin, J.delanoy, J04n, JT72, Jammus, Jasenlee, JbRIV, Jclemens, Jlmata, JoeSmack, JonHarder, Jonik, Jovianeye, Jowanner, KKuczko, Kaihsu, Kartisan, Keebrook, Keilana, Kevnosisyx, Kf4bdy, Kinu, Krackpot, Krusch, Kuru, Kycook, KyuuA4, Laug, Lehmannjl, Leirith, Lluinenb, MC MasterChef, MER-C, MMSequeira, Madman37, Magnus Manske, Majid iqbal, Malleus Fatuorum, Malo, Marcelo Pinto, Marcusmccoy, Markhoney, Martey, Martian, Materialscientist, Matthewedwards, Maximaximax, Mboverload, Mcsboulder, Mdd, Mellery, Metagraph, Mgillett, Michael Hardy, Michael J.
Cunningham, Michig, Michigan user, MikeDogma, Moeron, MrOllie, Mrehere, Mserge, Mudgen, Myszliak, Mzrahman, Najeh, Nasnema, NeilN, NickBush24, Nicoatridge, Niteowlneils, Nk, NoticeBored, Nslonim, Nuno Tavares, Nuujinn, Ocaasi, Oleh77, Olivier Debre, Omicronpersei8, OnePt618, OsvaldoCarvalho, Otto ter Haar, PRRfan, Panlm, Pansearch, Patchworker, Paulbruton, Paulbuchanan, Paulseatonsmith, Peterl, Pg133, Phil firstname.lastname@example.org, Philip ea, Piano non troppo, Pion, Pocopocopocopoco, Pparazorback, Pukerua, RHaworth, RainbowOfLight, Ralphbk, Raspolsky, Ravizone2000, Raysonho, Rchandra, Rehan20784, Rich Farmbrough, Rnsimmons, Robocoder, Rockfang, Ron Richard, Ronz, Rpeasley, Rugops, Runefrost, Sam Hocevar, SamG1978, SamTheButcher, Sandy ts2k, SaulPerdomo, Sbrumpton, Scott McNay, ScottWAmbler, Sdr, Sharpner, Shawnse, Smulvih2, Snori, Soifranc, Some jerk on the Internet, Somnoliento, Srandaman, Sspecter, Stakfry526, Stephanobianco, Stevegregory79, StoneIsle, StuartR, SunSw0rd, Svetlev, Ta bu shi da yu, Tabletop, Takamaxa, Tandric, Tarun.Varshney, Tassedethe, Tbsdy lives, Tcwilliams, Technobadger, The Anome, The Letter J, The Thing That Should Not Be, Thingg, Thumperward, Ticaro, Tiptoety, Tjarrett, Tobryant, Tpbradbury, TutterMouse, Twirligig, Twostardav, U11720, Uncle G, Vanbregt, Vashtihorvat, Veinor, VerdigrisP, Vince.meulle, VinitAdhopia, Vipinhari, Vlad, WECullen, Waggers, Watroba, Waturuochav, WebCoder11, West81, Wik, Wiki3 1415, WikiNickEN, Winterst, Woohookitty, Wren337, WxGopher, Xsmith, Zachlipton, Zsh, ??????, 1296 anonymous edits IT service management Source: http://en.wikipedia.org/w/index.php?oldid=420373787 Contributors: Abrahami, AbsolutDan, AndySonden, Ash, AtTal, Awotter, AzaToth, Beland, Bizservice, Black Kite, Blehfu, Blkrockin, Brads98, Brianj hill, Canton Viaduct, Charles T.
Betz, Chicagocos, ChristianBk, Christiansarkar, Claudio.risco, Codevest, Corpx, Danialshazly, Darp-a-parp, Davidoff, Davidpsalt, Diannaa, Dicklyon, ESkog, Floydpiedad, Fox, Gadget850, Garion96, Gerry.avilez, Godfreyk, Haakon, IDefx, ITServiceGuy, Icairns, IvanLanin, Ivormacfarlane, J.delanoy, JoeyDay, JonHarder, Jorrit, Jpabellon, Jpbowen, Jvlock, Kkm010, Korg, Kuru, Lavinci, Len Hendershott, Lpgeffen, Mackensen, Mbookworm, Mcicogni, Mcsboulder, Mdd, Mgillett, MikeDogma, Mild Bill Hiccup, MrOllie, Nasnema, Ncw0617, Neelttpl, Nono64, Ohnoitsjamie, Olevy, PhilipR, Pukerua, RHaworth, Raysonho, Rixmith, Robertmcneill, RoySmith, Runningonbrains, Sepersann, Servicemanagement101, Sgalup, Smiteri, Stephen, Storace, StuffOfInterest, Ta bu shi da yu, Tangotango, TastyPoutine, Technobadger, TheProject, Tjarrett, Tsiaojian lee, Tthheeppaarrttyy, Veinor, Vsevolod4, Wangfat, Webmasterwales, WeisheitSuchen, Xansmit, Xsmith, Yone Fernandes, 165 anonymous edits Method engineering Source: http://en.wikipedia.org/w/index.php?oldid=422192225 Contributors: CesarGon, DonFiresmith, Mdd, SEI Publications, 2 anonymous edits Axios Systems Source: http://en.wikipedia.org/w/index.php?oldid=404040170 Contributors: Cander0000, MGS1978, R’n’B, 7 anonymous edits Competitive Engineering Source: http://en.wikipedia.org/w/index.php?oldid=227894256 Contributors: ARAJ, Bwpach, ComputerGeezer, Elonka, Karpinski, R24in, SueHay, 2 anonymous edits Configuration management Source: http://en.wikipedia.org/w/index.php?oldid=422294953 Contributors: .digamma, ALMGuru, AbsolutDan, Ahoerstemeier, AlistairMcMillan, Altenmann, AndrewLighten, Assadchaudhry, Bartosz, Becky 55, Bestofcm, Billscottmorri, Bonwag, CanisRufus, Capricorn42, Chiz@sympatico.ca, Chowbok, ChrisG, ChristianBk, Cloudz1, ComputerGeezer, Cuttysc, Danipen, David Biddulph, Dchem, DoBBers, DonYonce8912, Douga, Druiloor, DynamSoft, Ebyabe, Emanhattan, Encoreopus, Ericlee748, Esdaniel, Everything counts, Exexpat, Fleminra, Flockmeal, Fstop22, Geraldo Medrano, Gleesona 7, Gtewallace, Gurch, HBowie, Haakon, Harald Hansen, Huerlisi, Igfrace, Imroy, JTN, Jaylobb, Jdotscott, JordanSamuels, JoshRyan, Jpalm 98, Julian Mendez, JullyKitty, Keebrook, Kuru, LeeHunter, Lichen0426, Lmarinho, Ludootje, M.e, M4gnum0n, Mandarax, Marc Girod, Marcelo Pinto, Mdd, Mild Bill Hiccup, Mjviscomi, Moreschi, MrOllie, Nixdorf, Ohnoitsjamie, Orderud, Ouc, Oveja, Owain.wilson, Pascal666, PatrickEgan, Patrickegan, Pekowski, Pelerin2, Petra.hegarty, Pg133, PhilKnight, Phobius, Project2501a, R.castelo, Raven22, Rickranger, RoySmith, Rwwww, Régis Décamps, SMcCandlish, SQL, Sabri76, Sam Hocevar, Sigma 7, SimonP, Smack, Soarhead77, Stephen1121, SunCreator, The Anome, Tiago simoes, Tivedshambo, Tom2856, Ttesmer, Ventonegro, Vsion, Wessel 1560, Wile E.
Heresiarch, 279 anonymous edits Fagan inspection Source: http://en.wikipedia.org/w/index.php?oldid=422349444 Contributors: Altenmann, Arthena, Ash, Attilios, Bigbluefish, Can’t sleep, clown will eat me, ChrisG, Courcelles, Drbreznjev, Epeefleche, Gaff, Gaius Cornelius, Gimmetrow, Hockeyc, Icarusgeek, Iwearavolcomhat, JIP, Kezz90, MacGyverMagic, Mjevans, Mkjadhav, Nick Number, Okok, Pedro.haruo, Slightsmile, Tagishsimon, Talkaboutquality, The Font, The Letter J, 43 anonymous edits IBM Tivoli Unified Process (ITUP) Source: http://en.wikipedia.org/w/index.php?oldid=404692540 Contributors: Chowbok, Eustress, Giraffedata, IDefx, Kubanczyk, MikeDogma, MrOllie, Palbright, WeisheitSuchen, Woohookitty, 4 anonymous edits Information Services Procurement Library Source: http://en.wikipedia.org/w/index.php?oldid=366553371 Contributors: Betacommand, ChrisG, ESkog, Grenavitar, Jorrit, Jstruve, Malo, Mcalukin, Mdd, Niteowlneils, R’n’B, Ravedave, Spiritofdeaddog, Tagishsimon, The Thing That Should Not Be, Uncle G, 10 anonymous edits ITIL Planning to implement service management Source: http://en.wikipedia.org/w/index.php?oldid=372065897 Contributors: 9Nak, Allstar18, Amatriain, Annafriel, Lluinenb, Mdd, MikeDogma, Raysonho, Rjwilmsi, WeisheitSuchen, 22 anonymous edits Market analysis for product software Source: http://en.wikipedia.org/w/index.php?oldid=394776123 Contributors: Burkestar, ChrisG, Crazykake, JonHarder, Luna Santin, Mailer diablo, Maurreen, Niteowlneils, Pgrieg, Pratheepraj, Pumpkincat, Radagast83, Rich Farmbrough, Rl, Robofish, Rossami, Ruud Koot, Winterst, Woohookitty, 13 anonymous edits Marketing decision support systems Source: http://en.wikipedia.org/w/index.php?oldid=386033483 Contributors: ChrisG, Colonel Warden, Ep.morgan, I dream of horses, Jezhotwells, Pumpkincat, Robofish, TJRC, The Wordsmith, TheGrappler, Unara, 4 anonymous edits Method Framework for Engineering System Architectures Source: http://en.wikipedia.org/w/index.php?oldid=405975100 Contributors: Abductive, DonFiresmith, MLauba, Mdd, Minimac, Miyagawa, Rich Farmbrough Technical architecture Source: http://en.wikipedia.org/w/index.php?oldid=424024669 Contributors: Aasch, Allan McInnes, Aylahs, Barts1a, ChrisG, Dave Barnett, Discospinster, Diturriaga, FreplySpang, Gletiecq, Graham Berrisford, Horatio Huxham, Interested, Iterator12n, JaGa, Jarretinha, Maria C Mosak, Mdd, Mercurywoodrose, Nazrani, Norm”, Oicumayberight, OverlordQ, Promethean, Reade, Shadowjams, Skyezx, Sprigot, Steven Zhang, Svick, Tonyshan, Uncle G, Userid333, Vanished user 39948282, Wikip rhyre, 63 anonymous edits Corporate Governance of ICT Source: http://en.wikipedia.org/w/index.php?oldid=398744708 Contributors: Itgovernancenetwork, Singhalawap, Themfromspace, 4 anonymous edits AS 8015 Source: http://en.wikipedia.org/w/index.php?oldid=402782757 Contributors: -Majestic-, BD2412, Bissinger, Edward, Frank Geerlings, Icd, KrakatoaKatie, Lester, Longhair, NickelShoe, RJFJR, Ulrichk, 10 anonymous edits Autonomic Networking Source: http://en.wikipedia.org/w/index.php?oldid=416338760 Contributors: 3pweqR2, Alouca, Cander0000, Cargious, DVdm, FlyHigh, Hhuili, JennyRad, LThiem, Luciole2013, Mvilcu, Oita2001, Paskornc, Perada, Pruetboonma, Psiphiorg, Shmlchr, Sjschmid, Thierry Grenot, Tide rolls, Welsh, Wknight94, Zollerriia, 17 anonymous edits Article Sources and Contributors Certified in the Governance of Enterprise IT Source: http://en.wikipedia.org/w/index.php?oldid=402937184 Contributors: Auntof6, Djharrity, IvanLanin, MelissaAndrews, MusketeeerMan, Pastore Italy, The Thing That Should Not Be, Titusmars, Varkonyib, 11 anonymous edits Chief web officer Source: http://en.wikipedia.org/w/index.php?oldid=412078934 Contributors: Avocade, Cirrus Editor, Squids and Chips, TaerkastUA, 1 anonymous edits COBIT Source: http://en.wikipedia.org/w/index.php?oldid=425704747 Contributors: Adrius42, Aeonx, Alan.rezende, Alanpc1, Alejo2083, AlephGamma, AllanBz, Ash, Awillcox, Azimout, Binarygal, Camitommy, Chowbok, Chrisco2005, CiudadanoGlobal, Cpaidhrin, Crazie 88, DanGalligan, David.T.Bath, David.t.bath, DiePerfekteWelle, Duke Ganote, Duncanrshannon, Dwandelt, Eccentric67, Face, Fedkad, Ferkelparade, FireballDWF2, Folajimi, Glen, Greyskinnedboy, Groovecoder, IvanLanin, Jamelan, Jef-Infojef, Jordav, Kcordina, Kjohnrussell, Kku, Kpk.in, Kuru, Lachnej, LeaveSleaves, LiDaobing, Lowzeewee, M.e, Manscher, MarkWahl, Mitnick, Oliver Lineham, Paradox11, Pastore Italy, PaulHanson, Peterhgregory, Ps07swt, REDMBACISA, RHaworth, Reaper Eternal, Refalm, RichardVeryard, Robertbowerman, Ron Richard, SK ISACA, ST47, Smitbruc, Snori, Spartyguy32, Sspecter, StaticGull, Stefano.Ferroni, SueHay, Sumantra sarkar, Super-Magician, TScabbard, Ta bu shi da yu, The Thing That Should Not Be, Timotheos, Vaceituno, Vashtihorvat, Xezbeth, Zaphod119, Zumbo, 251 anonymous edits Information technology controls Source: http://en.wikipedia.org/w/index.php?oldid=425810497 Contributors: AllanBz, Balloonguy, Beetstra, Billyarberry, Can’t sleep, clown will eat me, Cartermichael, Cwilli1024, David.t.bath, DerHexer, Dmccreary, Elham gholami, Esperry, Farcaster, FlyHigh, Giraffedata, JaGa, Joy, Kubanczyk, Kuru, Kyisauditor, Lachnej, M.e, Maurreen, Nricardo, P b1999, Pastore Italy, PaulHanson, Polluks, Ravichandar84, Ricky@36, Royalguard11, Sapuser1, Sarahjaneseddon, ShawnVW, TScabbard, Teetery, The Obfuscator, Vashtihorvat, Ww2censor, ZacBowling, 59 anonymous edits Data custodian Source: http://en.wikipedia.org/w/index.php?oldid=413039629 Contributors: Nolelover, TScabbard, 1 anonymous edits Data governance Source: http://en.wikipedia.org/w/index.php?oldid=423766001 Contributors: 12Mike12, BlueMoses, Chasingsol, DanPrimus, Dawnseeker2000, Jimmyviv, Kuru, Kyle.Lindsay, MDM maven, Markcowan, Martarius, Mdd, Michael Hardy, Misfitkid64, Mkrause2, Mpicazovico, MrOllie, Nicotin78, Nsaa, Oli Filth, Pdeleenh, RTddd, RichardVeryard, Shaw76, Spellmaster, Syaskin, TScabbard, Technopilgrim, Tetracube, Tgold65, Virtualelvis, WikHead, Woodsstock, 23 anonymous edits Data steward Source: http://en.wikipedia.org/w/index.php?oldid=413039630 Contributors: Bernburgerin, D’Artagnol, Dmccreary, Ian Burnet, Jschwa1, Markcowan, Martarius, MrOllie, Oli Filth, TScabbard, Tetracube, Winterst, 8 anonymous edits Data visualization Source: http://en.wikipedia.org/w/index.php?oldid=426216420 Contributors: Aaronzat, Abdel.a.saleh, Agor153, Ashash2288, Bcgrossmann, Blaz.zupan, Clemenza16, CommonsDelinker, Cristian Opazo, Danlev, Deeptext, Dekisugi, Delectate, Deville, EpicSystems, Ericmelse, GreenRoot, Ground Zero, Hanchuanpeng, Hgamboa, Infografica, Ivanpetrov, JamesXinzhiLi, Kellylautt, Kuru, Levenen, Linforest, MainFrame, Martin58474, Mdd, Nlan1igse, Ohspite, PeterWilfahrt, PrimaVista, Qwfp, Qwyrxian, Robiminer, SanFranArt, Stealth500, Stephroj, Stevemorr, Sweetmoose6, Talgalili, Teryx, Vsmith, Whibbard, Wing61, Yukimonster, Zeliboba7, ZweiOhren, 67 anonymous edits Governance Interoperability Framework Source: http://en.wikipedia.org/w/index.php?oldid=404405488 Contributors: Betacommand, Heather.taylor, Leolaursen, Mlaffs, Richard R White ISO/IEC 38500 Source: http://en.wikipedia.org/w/index.php?oldid=371504704 Contributors: Gene93k, LilHelpa, Nasa-verve, Psoenen, Sinnerxenogen, TScabbard, 15 anonymous edits Ministry of Communications and Information Technology (Egypt) Source: http://en.wikipedia.org/w/index.php?oldid=419490436 Contributors: BomBom, DaliaHalawa, Diaa abdelmoneim, Dialectric, Flatterworld, Islamhosni, Islamomt, Rich Farmbrough, 4 anonymous edits Project governance Source: http://en.wikipedia.org/w/index.php?oldid=417681284 Contributors: Akihabara, Auntof6, BenTremblay, Brightondays, Engi08, EurekaLott, GardmanVS, Giraffedata, Gsaup, JamesBWatson, Jauerback, Joekor, Jujutacular, Khalid hassani, Krakfly, Ktlonergan, Kuru, LeadSongDog, Lumos3, Malke 2010, Mapador, Mmiriam, MrOllie, Pleclech, Projectsponsor, R’n’B, Regregex, RichardVeryard, Schopi, Scrivener Scribe, Simple Bob, Tassedethe, 19 anonymous edits Public ROI Source: http://en.wikipedia.org/w/index.php?oldid=271836268 Contributors: Delirium, Melly77, RichardVeryard, 1 anonymous edits Risk IT Source: http://en.wikipedia.org/w/index.php?oldid=421398522 Contributors: DVdm, Leszek Ja?czuk, Mild Bill Hiccup, Pastore Italy, Peterhgregory, 3 anonymous edits SOA Governance Source: http://en.wikipedia.org/w/index.php?oldid=425551718 Contributors: Ajindy, Ashishvaid, Atakdoug, Bartash, Bostonmace, Brhubart, Dan weblayers, DeePatton, Ehheh, Falsodar, GerdInFrisco, Heather.taylor, Irishguy, Jadtnr1, JamesLWilliams2010, Jeffrschneider, Jswaroop, Layer7tech, MrOllie, RememberSoa, RichardVeryard, Ronz, Sadads, Saligron, SamJohnston, SpandauBeta, Toddbiske, Tomschepers, TracieWiki, 74 anonymous edits TickIT Source: http://en.wikipedia.org/w/index.php?oldid=389061645 Contributors: Cybercobra, Cyreath, D6, DavidWBrooks, Gzkn, Kbh3rd, Neilbmartin, Nikhildhar, Northernhenge, Pearle, Ratarsed, Redeagle688, Rillian, The Rambling Man, Toughnrough, 28 anonymous edits Total cost of ownership Source: http://en.wikipedia.org/w/index.php?oldid=426324951 Contributors: Acc4sid, Aixroot, Android Mouse, Arthena, Arundel77, Awis, B Fizz, BBCWatcher, Bender235, Bob A, CIOGuru, CapitalR, Chachi32, Ckraju, DH85868993, David Shay, Deeb, Dendlai, ENeville, FrankTobia, Ft1, Fubar Obfusco, Hilel14, J04n, Jake Nelson, Jaredroberts, Jdfellows, Kelly Martin, Kozuch, Levineps, Mariordo, Mattisse, Mayfly may fly, Mellery, Michael Hardy, Nephron, OS2Warp, Ojigiri, Oleg Alexandrov, Omphaloscope, Pne, Quadra23, RJBurkhart, Radagast83, Rcollman, Ronz, S.K., SJP, Saibo, SirIsaacBrock, Suegerman, Thorpe, Vaquerito, Zaf, Zondor, 110 anonymous edits Val IT Source: http://en.wikipedia.org/w/index.php?oldid=419914625 Contributors: Alexconceicao, B.
Wolterding, Charles T.
Betz, David.T.Bath, David.t.bath, Excirial, Fdfhdgh, GardmanVS, Greyskinnedboy, RichardVeryard, Simple Bob, SueHay, Umbertoumm, Viking59, WestCGuy, 10 anonymous edits Web content lifecycle Source: http://en.wikipedia.org/w/index.php?oldid=425464875 Contributors: AnOddName, Brianann MacAmhlaidh, Chanakal, Chowbok, Cirrus Editor, Donkeydonkeydonkeydonkey, Kku, Mgiganteus1, Ntsimp, 1 anonymous edits Website governance Source: http://en.wikipedia.org/w/index.php?oldid=425815471 Contributors: Cirrus Editor, Cybercobra, Missylou2who, R’n’B, 2 anonymous edits 131 Image Sources, Licenses and Contributors 132 Image Sources, Licenses and Contributors Image:Wearer of an ITIL Foundation Certificate pin.jpg Source: http://en.wikipedia.org/w/index.php?title=File:Wearer_of_an_ITIL_Foundation_Certificate_pin.jpg License: Creative Commons Attribution-Sharealike 2.5 Contributors: User:IIVQ File:Method engineering process.jpg Source: http://en.wikipedia.org/w/index.php?title=File:Method_engineering_process.jpg License: Public Domain Contributors: Richard J.
Mayer and others Image:ConfiurationActivityModel.png Source: http://en.wikipedia.org/w/index.php?title=File:ConfiurationActivityModel.png License: Public Domain Contributors: Department of Defense Handbook Image:Fagan Inspection Simple flow.gif Source: http://en.wikipedia.org/w/index.php?title=File:Fagan_Inspection_Simple_flow.gif License: Public Domain Contributors: Monkeybait, Okok Image:Procesdatadiagram planning to implement ITIL.png Source: http://en.wikipedia.org/w/index.php?title=File:Procesdatadiagram_planning_to_implement_ITIL.png License: Creative Commons Attribution-Sharealike 2.5 Contributors: L.
Luinenburg (Lluinenb) Original uploader was Lluinenb at en.wikipedia File:WorldWideWebAroundWikipedia.png Source: http://en.wikipedia.org/w/index.php?title=File:WorldWideWebAroundWikipedia.png License: unknown Contributors: User:Chris 73 file:MCIT Premises.JPG Source: http://en.wikipedia.org/w/index.php?title=File:MCIT_Premises.JPG License: Public Domain Contributors: User:DaliaHalawa Image:website_governance_roles.png Source: http://en.wikipedia.org/w/index.php?title=File:Website_governance_roles.png License: Public Domain Contributors: User:Missylou2who License
Read more about ITIL Planning : Contents Articles Service Catalog Corporate governance of information technology Information….: