Your SlideShare is downloading. ×
ukoug-mi-200610.ppt - 1.8 MB.
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

ukoug-mi-200610.ppt - 1.8 MB.


Published on

Published in: Business, Technology

  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide
  • This sort of verbal obfuscation is what gives PROCESS a bad name… !
  • What we really mean is this. We increasingly have to think of IT as more than a collection of technical bits (servers, databases etc.) We need to think of IT as being a SERVICE and that we, as technical people and professionals, SUPPORT that Service. We then DELIVER that Service to the BUSINESS, for the purpose of making MONEY.
  • When we start thinking of IT as a Service, then we start thinking about how do we manage it better. Say “what are we trying to achieve overall?” Rather than “what does this team do?”
  • ITIL was conceived by the British Government who approached various organisations and experts to write the books which were originally published in the 1980s. These were revised in 2001 and 2002, and the library has expanded in scope since then. The latest version is being developed for publication in 2007.
  • Sometimes these methodologies can get in the way, sometimes they help. Either way, they can be useful, if you “pick-and-choose” what will help you. And remember - ITIL is NON-PRESCRIPTIVE - IT does not demand that you do anything!
  • Just as PRINCE2 is a methodology, an approach, which can be used successfully by development teams to manage projects, So ITIL is an approach, a set of “best practices” for managing the day-to-day support activities in Production.
  • This is what the ITIL library actually consists of. Recently Added: Introduction to ITIL Software Asset Management Small-Scale Implementation
  • As mentioned, the key volumes are SERVICE DELIVERY and SERVICE SUPPORT. They are often what is called “Core ITIL”. Most people, when they talk about ITIL, are thinking of these two books only, and the chapters in them. So, when we talk about ITIL, we need to understand what is meant by these 11 topics.
  • Fact One: The books themselves are meant to guide; they are not steadfast laws. None of the authors, contributors or publishers ever expected organizations to adhere to every word of their publications. Fact Two: You can't implement ITIL with just processes and technology. You must address the people involved as well. ITIL demands attention to three components: people, process and technology. Changes in process improve efficiency and effectiveness. Changes in technology reduce costs and accelerate responsiveness. But you ultimately have to change people to develop the culture you need to better support the business and optimize availability of critical IT services. (Brian Johnson)
  • What is the it SMF? A not-for-profit organisation owned by its members, the it SMF is a major influence on, and contributor to, industry b est practice , Standards and personal development, working with a wide range of governmental and standards bodies worldwide.Formed in the UK in 1991, there are now national chapters in an ever-increasing number of countries. There is an International body that guides and supports existing and emerging chapters, their website is www. itsmf .org .
  • Transcript

    • 1. Beginners Guide to ITIL - help or hindrance? Dennis Adams 4th October 2006 Dennis Adams a s s o c i a t e s Management and Infrastructure SIG Meeting Can it help me? What are the pitfalls?
    • 2. Introduction
      • Why we are doing this … (Target Audience)
        • Confused by what ITIL is?
        • Heard the buzz-words, but not sure of the substance?
        • Scared by the prospect of being inundated with too much processes, so that your teams are unable to get any work done?
      • These are all typical reactions from technical leaders and managers when faced with the ITIL “hype”.
      • The purpose of this presentation is to introduce what ITIL is really about, and take away the mystery.
      • Explain and Justify PROCESS to TECHNICAL Audience.
      “ ITIL for Dummies” ?
    • 3. Topics to Cover
      • What is ITIL ?
      • What do we mean by a “Process Approach” to the world as a different way of looking at how we work together ?
      • What are the main Processes within ITIL ?
      • What some of the main Processes look like in more Detail
      • The importance of the Configuration Management Database (CMDB)
      • Conclusions: Don’t “Implement ITIL?” (!?)
      • Time for Questions…
    • 4. The ITIL definition of IT “Service” - is this helpful ?? “ An integrated composite that consists of a number of components such as management processes, hardware, software, facilities and people that provides a capability to satisfy a stated management need or objective.” Dictionary of IT Service Management
    • 5. Think of MANAGING IT as PROVIDING a SERVICE £ IT SERVICE SERVICE DELIVERY SERVICE SUPPORT BUSINESS Align IT services with the needs of the Business Improve the Quality of the Service Reduce the long-term costs
    • 6. Think in terms of PROCESSES rather than SKILLS Functional Organization Process Approach Using a Process Approach, we no longer think in terms of individual technical teams “doing their own thing”. Rather we think in terms of the overall goal which should be directed to the main goals of the organization .
    • 7. What is ITIL?
      • ITIL = “Information Technology Infrastructure Library”
      • A Library of Processes books outlining “good practice” for managing IT Infrastructure.
      • A set of ready-made “how to” references.
      • ITIL® is a Registered Trade Mark, and a Registered Community Trade Mark of the Office of Government Commerce, and is Registered in the U.S. Patent and Trademark Office
      • ITIL revision 3 is currently being written.
      • A British Standard (BS 15000) certification (BS 25000 to come).
      • Linked to ISO 9000 Quality Certification.
    • 8. An Analogy: Remember Development Methodologies? Paralysis of Analysis ? Waterfall Development Hobby craft developer Prototype and User Design Quick and Dirty Structured Design Method Anarchy ? JFDI ? Development Methodologies define Ways of Working to ensure that we do things in a Repeatable, Professional manner.
    • 9. PRINCE 2 (Projects) ITIL (Infrastructure) Initiate Design Deploy Service Desk / Help Desk Identify root-cause of Problems Infrastructures Changes New Application Releases Document the Configuration Resolve Customer Incidents Build Test DEVELOPMENT PRODUCTION
    • 10. The ITIL Library of Process Books Application Management The Business Perspective Planning to Implement Service Management Supplementary Volumes Main Volumes “ CORE ITIL” Key: ICT Infrastructure Management Security Management Service Delivery Service Support
    • 11. The Core ITIL Books: IT Service Management
      • Capacity Management
      • Availability Management
      • IT Service Continuity Management.
      • Service Level Management
      • IT Financial Management
      • Service Desk
      • Incident Management
      • Problem Management
      • Change Management
      • Release Management
      • Configuration Management
      Service Support Service Delivery User Support Control Processes
    • 12. EXAMPLE: Process to manage CHANGE Impact Analysis Assess Priority Log RFC Categorize Approval Change Scheduling Testing Plans Inform Users Change Review Request for Change
      • Future Service requirements from the Business
      • Future Capacity from the Business
      • Resource Requirements in future.
      • What are the existing requirements?
      • Are we meeting SLAs?
      • How well are we utilising existing resources today?
      • How well are we using existing technology?
      • Are we using each component appropriately?
      • What future technologies could be better?
    • 14. EXAMPLE: The activities in CAPACITY PLANNING Business Strategy Business Planning IT Strategy IT Business Plan Service Level Exceptions Resource Utilisation Exceptions Monitoring Service Level Thresholds Resource Utilisation Analysis Tuning Ensuring we can meet our SLAs Implementation
    • 15. Some Best Practices in the ITIL Library
      • How to get the best benefit from a SERVICE DESK
        • Single point of contact, Monitoring and escalation on behalf of customers.
      • A systematic way of managing INCIDENTS:
        • Log / Classify / Investigate / Diagnose / Resolution
      • Being Pro-Active: PROBLEM MANAGEMENT
        • Root Cause Analysis, Kepner & Tregoe Analysis, Ishikawa diagrams.
      • Keeping track of IT Assets: CONFIGURATION MANAGEMENT
      • Stopping dangerous changes: CHANGE & RELEASE MANAGEMENT
        • Impact Analysis and Authorisation before Changes
      • Being Customer-Focused: SERVICE LEVEL MANAGEMENT
      • Bean-Counting: FINANCIAL MANAGEMENT
        • Charge-back to reflect the cost to the Business.
      • CAPACITY: Prediction instead of Panic
        • Design for continual up-time
        • Risk Assessment and Planning
    • 16. Why implement ITIL-based processes?
      • ITIL emphasises that IT should be seen as a service to the business.
      • ITIL could be (part of) a Quality Management strategy to improve the quality of the IT Service for the business.
      • Introducing clear processes should enable the company to grow and/or bring on more staff more easily.
      • Being based on a “best practice” approach means that you do not have to reinvent the wheel.
      • Cost reduction - Standardising “how you do things” can simplify and reduce costs.
      • Professionalism / Clear points of contact with external organisations and stakeholders.
    • 17. The BEST WAY to Implement ITIL Service Management? Incident Problem Change Release Configuration Service Desk Configuration Management Database (CMDB)
    • 18. … or MORE LIKE THIS ? Incident Problem Change Release Configuration Service Desk Configuration Management Database (CMDB)
    • 19. .. Just Some parts of a theoretical CMDB HARDWARE Specification Location Owner Financials Software SOFTWARE Licenses Versions APPLICATIONS Users Hardware USERS Applications Contracts Incidents INCIDENTS Applications Hardware Resolutions KNOWN ERRORS Incidents PROBLEMS Incidents Resolutions CHANGES Applications Users Equipment O/S Equipment INFRASTRUCTURE SOFTWARE e.g. Oracle RELEASES Applications NETWORK Linkages Dependancies SLA Applications Users Contracts DEFINITIVE SOFTWARE LIBRARY SERVICES Applications DEFINITIVE HARDWARE STORE B C P DOCS AVAILABILITY STATISTICS
    • 20. Case Study: Understanding Applications and Machines Data Collection Processes Hardware in Data Centre New Equipment Purchasing Objective: Impact Analysis of Applications <=> Machines Applications on machines Change Control: Usage of Machine Application Listing Release Management: Applications Server Naming Configuration Management: Naming Conventions
    • 21. Pitfalls and Warnings
      • “ Organisations should not be over ambitious when implementing Service Management ” (IT Service Management “Little ITIL”).
        • ITIL is a Framework of Best Practices, not a Prescriptive Manual
        • Use what is useful, when and where it is useful.
      • Remember that any IT Process will only work if the participants have the right data in the right place at the right time.
        • Configuration Management Database (CMDB)
      • Remember that the objective is to document and implement repeatable processes in order to make the organisation more efficient and/or more responsive to customers.
        • ITIL should never been seen as an end in itself.
    • 22. Some Recommendations
      • See ITIL processes as a way of standardising what is already done / should be already done.
        • Everyone should benefit from simplified and clearer ways of doing things.
      • Consider the ITIL Foundation Exam
        • For most IT Infrastructure Professionals, it is “common sense”
        • Looks good on the CV
        • Gives you a common “vocabulary” for discussing how things are done
        • Emphasises “customer focus” and “process”
        • 40 questions multiple-choice, pass mark is 25.
      • Keep asking “what is the business benefit ?”
    • 23. Further Useful Information
      • OGC Home Page for ITIL:
      • TSO (The Stationery Office):
      • IT Service Management Forum (itSMF):
      • Interactive Forum:
      • ITIL Toolkit:
      • Key Skills Training: ,
      • Square Mile Systems:
      • Pink Elephant Consultancy:
      • Dennis Adams Associates:
    • 24. Questions?
      • Is ITIL a panacea for all IT Infrastructure Management challenges?
        • It never claims to be !
        • It is a set of good practice processes to be used as a “toolkit”
        • ITIL itself speaks about:
          • Process / Product / People.
        • Implement ITIL as part of a Strategic Cultural change in the organisation, which should include:
          • Metrics, Operational Tools, Processes, Standards.
      • Can you implement “parts” of ITIL and ignore the rest?
        • Yes.
        • Remember that to make processes succeed you need appropriate data.
    • 25. More Questions ? Dennis Adams a s s o c i a t e s
    • 26. Beginners Guide to ITIL - help or hindrance? Dennis Adams 4th October 2006 Dennis Adams a s s o c i a t e s Management and Infrastructure SIG Meeting Can it help me? What are the pitfalls?