9 Haziran 2015 Salı

#ITIL Homework-3 : Developing An IT Metric Portal


THE FINAL PROJECT OF ITSM COURSE


Date : 09.06.2015

Subject : Created an IT Metric Portal for this homework project.

By the following this link(Google Drive), you can reach our project report.

https://drive.google.com/open?id=0B2W2jocEIHQgTnBKa1dySTFsX3c&authuser=0

---------------------------------

After looking at the project report :

One of my group mate has a domain in order to show you how the project works.

http://metinhasdemir.net76.net/

You can reach our portal from this link.


8 Mayıs 2015 Cuma

#ITIL Homework-2 : ITIL Continual Service Improvement

ITIL CSI - Continual Service Improvement

The Objectives of Continual Service Improvement 
   
    Service improvement must focus on increasing the efficiency, maximizing the effectiveness and optimising the cost of services and the underlying IT service management processes. The only way to do this is to ensure that improvement opportunities are identified throughout the entire service lifecycleThe primary purpose of Continual Service Improvement (CSI) is to continually align and re-align IT services to the changing business needs by identifying and implementing improvements to IT services that support business processes. 
CSI looks for ways to improve process effectiveness, efficiency and cost effectiveness.
Other objectives include:
  •  Review, analyse and make recommendations on improvement opportunities in each lifecycle phase:
            -  Service strategy
            -  Service design
            -  Service transition
            -  Service operation
            -  and CSI itself!

  • Identify and implement individual activities to improve IT service quality and improve the efficiency and  effectiveness of enabling ITSM processes
  • Improve cost effectiveness of delivering IT services without sacrificing customer satisfaction
  • Ensure applicable quality management method is used

The Scope of Continual Service Improvement 


There are three main areas that CSI needs to address:
  • The overall health of IT service management as a discipline
  • The continual alignment of the portfolio of IT services with the current and future business needs
  • The maturity of the enabling IT processes for each service in a continual service lifecycle model

The Activities of Continual Service Improvement 


  • Reviewing management information and trends to ensure that services are meeting agreed service levels.
  • Reviewing management information and trends to ensure that the output of ITSM processes are achieving the desired results
  • Conducting maturity assessments against the process activities and roles to highlight areas of improvementor concern
  • Conducting internal audits verifying compliance
  • Conducting external and internal service reviews to identify CSI opportunities
  • Reviewing analysed data
  • Presenting recommendations to senior management for improvement
  • Helping prioritise improvement opportunities
  • Leading managing and delivering cross functional and cross divisional improvement projects
  • Building effective relationships with the business and IT senior managers
  • Influencing all levels of management to ensure that service improvement activities are receiving the necessary support and are resourced sufficiently to implement solutions.

(This part is prepared by Yusufcan YALDIZ & Metin HASDEMİR)

---------------------------------------------------------------------------------------------------------------


The Deming Cycle


“Improve constantly, and forever” (W. Edwards Deming)


The cycle for quality improvement:
 Plan - Do - Check - Act

  • Plan: Proposal or revision of processes that support IT services.
  • Do: Implementation of the plan and process management.
  • Check: Measurement of processes and IT services, comparing with the objectives and creation of reports.
  • Act: Planning and implementation of changes to improve processes.

(This part is prepared by Burak EREGAR & Deniz TUNCER)


---------------------------------------------------------------------------------------------------------------

The Continual Service Improvement Model




As the above figure shows, there are many opportunities for CSI. The figure also illustrates a constant cycle for improvement. The improvement process can be summarised in six steps:
  • Embracing the vision by understanding the high level business objectives. The vision should align the business and IT strategies
  •  Assessing the current situation to obtain an accurate, unbiased snapshot of where the organisation is right  now. This baseline assessment is an analysis of the current position in terms of the business, organisation, people, process and technology
  • Understanding and agreeing on the priorities for improvement based on a deeper development of the principles defined in the vision
  •  Detailing the CSI plan to achieve higher quality service provision by implementing IT service management processes
  •  Verify that measurements and metrics are in place to ensure that milestones were achieved, process  compliance is high, and business objectives and priorities were met by the level of service
  •  Finally, the process should ensure that the momentum for quality improvement is maintained by assuring  that changes become embedded in the organisation

Continual Service Improvement Process 

- Why measure?

There are four reasons to monitor and measure:





  • To validate – monitoring and measuring to validate previous decisions
  • To direct – monitoring and measuring to set direction for activities in order to meet set targets. It is the most prevalent reason for monitoring and measuring
  • To justify – monitoring and measuring to justify, with factual evidence or proof, that a course of action is required
  • To intervene – monitoring and measuring to identify a point of intervention including subsequent changes and  corrective actions

The four basic reasons to monitor and measure lead to three key questions:

Why are we monitoring and measuring?, When do we stop? and Is anyone using the data?

To answer these questions,it is important to identify which of the above reasons is driving the measurement effort. Too often, measures are continued long after the need has passed. Every time a report is produced it should be asked: Do we still need this? 

Service metrics – these metrics are the results of the end to end service – component/technology metrics are used to produce the service metrics.

Process metrics – these metrics are captured in the form of Critical Success Factors (CSFs), Key Performance Indicators (KPIs) and activity metrics for the service management processes. Four key areas that KPIs can measure are quality, performance, value and compliance of following the process. CSI would use these metrics as input in identifying improvement opportunities for each process

Technology metrics – these metrics are often associated with component and application based metrics such as performance and availability



(This part is prepared by Burak EREGAR & Deniz TUNCER)

---------------------------------------------------------------------------------------------------------------

The Seven Step Improvement Process


Define what you should measure
  • At the onset of the service lifecycle, service strategy and service design should have identified this information. CSI can then start its cycle all over again at, Where are we now? This identifies the ideal situation for both the business and IT.

Define what you can measure
  • This activity is related to the CSI activities of Where do we want to be?. By identifying the new service level  requirements of the business, the IT capabilities (identified through service design and implemented via service transition) and the available budgets, CSI can conduct a gap analysis to identify the opportunities for improvement as well as answering the question, How do we get there?.

Gathering the data

  • In order to properly answer the Did we get there? question, data must first be gathered (usually through service operations). Data is gathered based on goals and objectives identified. At this point, the data is raw and  no conclusions are drawn.

Processing the data

  • Here the data is processed in alignment with the CSFs and KPIs specified. This means that timeframes are coordinated, unaligned data is rationalised and made consistent, and gaps in the data are identified. The simple goal of this step is to process data from multiple disparate sources into an apples to apples comparison.
           Once we have rationalised the data we can then begin analysis.


Analysing the data
  • Here the data becomes information as it is analysed to identify service gaps, trends and the impact on business. It is the analysing step that is most often overlooked or forgotten in the rush to present data to management.

Presenting and using the information

  • Here the answer to Did we get there? is formatted and communicated in whatever way necessary to present to the various stakeholders an accurate picture of the results of the improvement efforts. Knowledge is presented to the business in a form and manner that reflects their needs and assists them in determining the next steps.

Implementing corrective action

  • The knowledge gained is used to optimise, improve and correct services. Managers identify issues and present solutions. The corrective actions that need to be taken to improve the service are communicated and explained to the organisation. Following this step the organisation establishes a new baseline and the cycle begins anew.

(This part is prepared by Yusufcan YALDIZ & Metin HASDEMİR)

---------------------------------------------------------------------------------------------------------------

REFERENCES



25 Mart 2015 Çarşamba

# ITIL Homework-1 : Analyse the relation in between ITIL, Cobit, Togaf and CMMI.



First of all, I am going to explain all of these standards. These explanations include definitions and features about standards. After that, I am going to analyse the relations.

ITIL

   It refers to Information Technology Infrastructure Library. It’s the most well-known approach to information technology service management in the global world. It describes how IT resources should be organised to deliver business value, documenting the processes, functions and roles of IT Service Management. Actually, ITIL is a best-practice framework. The main aim of ITIL is that increasing earnings/reducing costs. Customers aspect’s is the main thing of ITIL. ITIL contains detailed process descriptions, flows, success factors, metrics and implementation guidance that organizations can adapt to work in their environment.


ITIL has been consisted of 5 lifecycle phases.
  1. Service Strategy : Focusing on understanding customer needs, directions, requirements, helping improve IT over time.
  2. Service Design : Focusing on turning strategies for services into a detailed Service description, not just the technology.
  3. Service Transition : Focusing on building, validating, and delivering new and changed services to customers.
  4. Service Operations : Focusing on the day to day care and feeding of services
  5. Continual Service Improvement : Focusing on identifying and managing incremental improvements to services.

COBIT
  
    It refers to Control Objectives for Information and Related Technology. It is an IT governance framework and supporting toolset published as an open standard by the IT Governance Institute and ISACA. COBIT is designed to allow managers to bridge the gap between control requirements, technical issues and business risks. It is a control model that guarantees the integrity of the information system. COBIT ensures quality, control and reliability of information systems in organization, which is also the most important aspect of every modern business.

 

 



IT activities were divided into 4 domains by the COBIT framework.

1-) Plan and Organize : Provides direction to solution and service delivery.

2-) Acquire and Implement : Provides the solutions and passes them to be turned into services. 

3-) Deliver and Support : Receives the solutions and makes them usable for end users. 

4-) Monitor and Evaluate : Monitors all processes to ensure that the direction provided is followed.

TOGAF
   
    It refers to The Open Group Architecture Framework. The framework itself is a well-documented body of knowledge comprising a detailed method and a set of supporting tools for developing enterprise architectures.
   
    Developing and sustaining an enterprise architecture is a complex process, involving many stakeholders and decision processes. TOGAF helps by documenting the Enterprise Architecture discipline, process and work products. By using TOGAF, organizations can develop an enterprise architecture that is consistent, reflects the needs of stakeholders, employs best practice, and gives due consideration to current requirements and the perceived future needs of the business.

    There are four architecture domains.(for enterprise architectures supported by TOGAF)

1-) The Business Architecture : Defines the business strategy, governance, organization, and key business processes. 

2-) The Data Architecture : Describes the structure of an organization's logical and physical data assets and data management resources. 

3-) The Application Architecture : Provides a blueprint for the individual applications to be deployed, their interactions, and their relationships to the core business processes of the organization. 

4-) The Technology Architecture : Describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, networks, processing, standards…

CMMI

    It refers to The Capability Maturity Model Integration. It is a process model that provides a clear definition of what an organization should do to promote behaviors that lead to improved performance.

    The CMMI helps us understand the answer to the question “how do we know?”. For instance, how do we know if our requirements change process is useful? This question is an example what the CMMI try to tell us. We may ask many questions to ourselves starting with “how do we know?”.

    The CMMI also helps us identify and achieve measurable business goals, build better products, keep customers happier, and ensure that we are working as efficiently as possible.

    The model identifies five levels of process maturity for an organization:
  1. Initial (adhoc): The starting point for use of a new process.
  2. Repeatable (project management, process discipline): The process is used repeatedly.
  3. Defined (institutionalized): The process is defined/confirmed as a standard business process.
  4. Managed (quantified): Process management and measurement take place.
  5. Optimizing (process improvement): Process management includes deliberate process optimization or improvement.

                                          ANALYZING RELATIONS
* COBIT is broader than ITIL, CMMI and ISO standards in its scope of coverage.

* ITIL focuses on ITSM and provides much more in-depth guidance in this area, addressing five stages of the service life cycle. Also, COBIT and ITIL are well aligned in their approach to ITSM.

* The distinction between the COBIT and ITIL is sometimes described as COBIT provides the ‘why’ and ITIL provides the ‘how.’ COBIT focuses on what needs to be achieved rather than how to achieve.

* COBIT provides an overall, high level governance framework which is applicable to most organizations but is not specific about certain aspects of the business like IT service management or information security. As ITIL covers particular areas in more detail, it can be mapped to COBIT to enhance the framework and build a hierarchy of processes. This means that COBIT can be used to shape ITIL processes to the business needs and measure the success of ITIL implementation.










You may see three figures relationship between TOGAF and ITIL. Business architecture is addressed by TOGAF but not by ITIL. IT services are addressed by ITIL but not by TOGAF. The other elements are covered in both frameworks. As a consequence, TOGAF gives you all you need to build the perfect IT solution and monitors, but provides no guidance on how to deliver IT services. ITIL gives you all you need to deliver IT services perfectly.

* CMMI is mainly focused on continuous and long-term improvement for business processes, while ITIL targets all areas included in the IT aspect of an organization. CMMI is often used for developing new and efficient software, but it does not address hardware concerns. On the other hand, ITIL addresses hardware issues as they fall under the IT umbrella of an organization.

* The CMMI is not a process, it is a book of “whats” not a book of “hows,” and does not define how your company should behave. 

* CMMI and ITIL are two distinctly different maturity models that can complement each other when used together. The fundamental difference between the two is that CMMI is a method of process improvement for software development, while ITIL focuses mainly on IT issues.


 

This is a general figure about relation between COBIT – TOGAF – ITIL.

    REFERENCES

    Many websites and articles(like OGC’s) from the Internet.