Introduction to ITIL v3 Foundation exam

19,818 views

Published on

I hope this introductory presentation to ITIL v3 Foundation exam will be very useful to the readers. The time one needs to spend on study depends upon one's experience with ITIL related practices in real world. Nonetheless, it is very simple study, but the exam questions may be trickier than expectation. So, focus on learning ITIL concepts rather than adding ITIL certificate to your resume.


References for the slides used from:
http://taruu.com/Documents/ITIL%20v3%20Foundation%20Study%20Guide%20v4.2.2.5.pdf
The Art of Service – ITIL v3 Foundation Complete Certification Kit (book and online course)
Skillport - IT Infrastructure Library (ITIL) v3 Foundation Syllabus v4.2 exam

Published in: Business, Technology
3 Comments
39 Likes
Statistics
Notes
  • More than 5000 registered IT consultants and Corporates.Search for IT online training Providers at http://www.todaycourses.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • Intriquing presentation. Also found these sample exam papers helpful too: www.v3examcertification.co.uk
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
  • MUITO BOM OS CONTEÚDO APRESENTADOS.....
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total views
19,818
On SlideShare
0
From Embeds
0
Number of Embeds
234
Actions
Shares
0
Downloads
2,568
Comments
3
Likes
39
Embeds 0
No embeds

No notes for slide

Introduction to ITIL v3 Foundation exam

  1. 1. Prepared by Kadimil
  2. 2. ITIL v3 Certification Scheme Overview Terminology ITIL Lifecycle phases Service Strategy Service Design Service Transition Service Operation Continual Service Improvements
  3. 3. ITIL v3 Certification Scheme This presentation is on ITIL v3 Foundation Certificate
  4. 4. Overview <ul><li>Your purpose – Certification vs. Learning </li></ul><ul><li>Certification track </li></ul><ul><ul><li>2 hours introduction </li></ul></ul><ul><ul><li>6 hours self-study and mock tests </li></ul></ul><ul><ul><li>http://taruu.com/Documents/ITIL%20v3%20Foundation%20Study%20Guide%20v4.2.2.5.pdf </li></ul></ul><ul><ul><li>The Art of Service – ITIL v3 Foundation Complete Certification Kit (book and online course) </li></ul></ul><ul><li>Mock tests </li></ul><ul><ul><li>http://www.itskeptic.org/itil-version-3-certification-eight-sources-free-it </li></ul></ul><ul><ul><li>http://www.accelerated-ideas.com/exams/practice-exam.aspx?group=ITIL&fq=1&qmax=15 </li></ul></ul>
  5. 5. Overview <ul><li>Learning track </li></ul><ul><ul><li>2 hours introduction </li></ul></ul><ul><ul><li>15 hours self-study and mock tests </li></ul></ul><ul><ul><li>SkillPort - Course Curricula/English - US/IT Professional Certifications/IT Infrastructure Library (ITIL)/ITIL V3/IT Infrastructure Library (ITIL) v3 Foundation Syllabus v4.2 exam </li></ul></ul><ul><li>Exam registration </li></ul><ul><ul><li>http://pearsonvue.com/exin/ or http://www.register.prometric.com/Centers.asp </li></ul></ul><ul><ul><li>Fees - $174; 1 hour exam; 40 questions; 26 out of 40 to pass (65%) </li></ul></ul>
  6. 6. Overview <ul><li>Office of Govt Commerce in the UK owns trademark of ITIL as the ITIL framework evolved from their efforts to document how successful organizations approached service management. </li></ul><ul><li>ITIL describes good practices and best practices, including those documented by Public frameworks, Standards, wide-industry best practices etc </li></ul>
  7. 7. Terminology <ul><li>ITSM – A set of specialized organizational capabilities for providing value to customers in the form of services </li></ul><ul><li>Service – A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. E.g. Pizza delivery service, Payroll service </li></ul><ul><li>Service owner – The person who is accountable for the delivery of a specific service. </li></ul>
  8. 8. Terminology <ul><li>Process – A set of coordinated activities combining and implementing resources and capabilities in order to produce an outcome and provide value to customers or stakeholders. E.g. Availability management process </li></ul><ul><li>Process owner – The person responsible for ensuring that the process is fit for the desired purpose and is accountable for the outputs of that process. </li></ul><ul><li>Functions – A team or group of people and the tools they use to carry out one or more processes or activities. E.g. Service Desk, IT Operations management </li></ul>
  9. 9. Terminology <ul><li>RACI chart – Connecting processes and functions by the way of defining clear roles and responsibilities </li></ul>
  10. 10. ITIL Lifecycle Phases
  11. 11. Service Strategy <ul><li>Define strategic objectives of the IT organization </li></ul><ul><li>Stop and think WHY something has to be done, before thinking HOW </li></ul><ul><li>Service Package </li></ul><ul><ul><li>Core Service Package </li></ul></ul><ul><ul><li>Supporting Services Package </li></ul></ul><ul><ul><li>Service Level Package </li></ul></ul>
  12. 12. Service Strategy <ul><li>Creating Value </li></ul>
  13. 13. Service Strategy - Processes <ul><li>Service Portfolio Management </li></ul><ul><ul><li>It contains 3 service groups – Service Pipeline, Service Catalogue, Retired Services </li></ul></ul><ul><ul><li>Balancing Service Portfolio – Run the Business, Grow the Business, Transform the Business </li></ul></ul>
  14. 14. Service Strategy - Processes <ul><li>Financial Management </li></ul><ul><ul><li>It manages conflicting perspectives of IT and Business in terms of IT capabilities and Business opportunities </li></ul></ul><ul><ul><li>Three fundamental activities – Funding/Budget, Accounting, Charging/Chargeback </li></ul></ul>
  15. 15. Service Strategy - Processes <ul><li>Demand Management </li></ul><ul><ul><li>Objective: Identification and analysis of Patterns of Business Activity and user profiles; And maintaining business and customer satisfaction while reducing excess capacity </li></ul></ul><ul><ul><li>Two ways to influence or manage Demand </li></ul></ul><ul><ul><ul><li>Physical/Technical constraints – e.g. restrict number of connections, users etc </li></ul></ul></ul><ul><ul><ul><li>Financial chargeback – e.g. extra charges for over capacity quotas </li></ul></ul></ul>
  16. 16. Service Design <ul><li>Concerned primarily with the design of IT services </li></ul><ul><li>Designs to convert strategic objectives into Services </li></ul>
  17. 17. Service Design - Processes <ul><li>Service Level Management (Design phase) </li></ul><ul><ul><li>Primary goal is to ensure that an agreed level of IT service is provided for all current IT services, and that future services are delivered to agreed achievable targets. </li></ul></ul><ul><ul><li>Service Level Agreement vs Operational Level Agreement </li></ul></ul><ul><ul><li>Three types of SLAs – Customer based SLA, Service based SLA, Multi-level SLA(Corporate level, Customer level, Service level) </li></ul></ul>
  18. 18. Service Design - Processes <ul><li>Supplier Management </li></ul><ul><ul><li>Primary goal is to manage suppliers and services they supply, to provide seamless quality of IT service to the business and ensure that value for money is obtained. </li></ul></ul><ul><ul><li>Types of Supplier Agreements – Co-sourcing, Multi-sourcing, Business Process Outsourcing, Knowledge Process Outsourcing etc </li></ul></ul><ul><ul><li>Supplier and contract information is stored in Supplier and Contract Database (SCD). </li></ul></ul>
  19. 19. Service Design - Processes <ul><li>Service Catalogue Management </li></ul><ul><ul><li>Primary goal is to ensure that a Service Catalogue is produced, maintained and always contains accurate information. </li></ul></ul><ul><ul><li>Two Types </li></ul></ul><ul><ul><ul><li>Business Service Catalogue - e.g. various Business Processes </li></ul></ul></ul><ul><ul><ul><li>Technical Service Catalogue – e.g. Hardware, Software, DB, etc </li></ul></ul></ul><ul><ul><ul><li>They two interact to provide services to customers </li></ul></ul></ul>
  20. 20. Service Design - Processes <ul><li>Capacity Management </li></ul><ul><ul><li>Primary goal is to ensure that the current and future capacity and performance demands of customers regarding IT service provision are delivered. </li></ul></ul><ul><ul><li>Main activities </li></ul></ul><ul><ul><ul><li>Performance monitoring </li></ul></ul></ul><ul><ul><ul><li>Application sizing </li></ul></ul></ul><ul><ul><ul><li>Tuning </li></ul></ul></ul><ul><ul><ul><li>Capacity planning </li></ul></ul></ul><ul><ul><ul><li>Reporting, etc </li></ul></ul></ul>
  21. 21. Service Design - Processes <ul><li>Availability Management </li></ul><ul><ul><li>Primary goal is to ensure that the level of service availability delivered in all services is matched to or exceeds the current and future agreed needs of the business. </li></ul></ul><ul><ul><li>Incident life cycle </li></ul></ul>
  22. 22. Service Design - Processes <ul><li>IT Service Continuity Management </li></ul><ul><ul><li>Primary goal is to support the overall Business Continuity Management by ensuring that the required IT infrastructure and the IT service provision can be recovered within required and agreed time scales. </li></ul></ul>
  23. 23. Service Design - Processes <ul><li>Information Security Management </li></ul><ul><ul><li>Primary goal is to align IT security with Business security and ensure that information security is effectively managed in all services and IT Service Management activities. </li></ul></ul><ul><ul><li>Three major aspects </li></ul></ul><ul><ul><ul><li>Confidentiality </li></ul></ul></ul><ul><ul><ul><li>Integrity </li></ul></ul></ul><ul><ul><ul><li>Availability </li></ul></ul></ul>
  24. 24. Service Transition <ul><li>It focuses on the vulnerable transition from Design phase to Operation phase of a new/enhanced service. </li></ul><ul><li>It is critical as technical/functional errors NOT found during this phase will result in significantly higher impact levels to the business and/or IT infrastructure and will usually cost much more to fix once the Service is in operation. </li></ul>
  25. 25. Service Transition - Processes <ul><li>Knowledge Management </li></ul><ul><ul><li>The primary purpose is to improve efficiency by reducing the need to rediscover knowledge. This requires accessible, quality and relevant data and information available to staff. </li></ul></ul><ul><ul><li>Moving from data to wisdom </li></ul></ul><ul><ul><ul><li>Data </li></ul></ul></ul><ul><ul><ul><li>Information (Who, what, when, where?) </li></ul></ul></ul><ul><ul><ul><li>Knowledge (How?) </li></ul></ul></ul><ul><ul><ul><li>Wisdom (Why?) </li></ul></ul></ul>
  26. 26. Service Transition - Processes <ul><li>Service Asset and Configuration Management </li></ul><ul><ul><li>The goal is to support the agreed IT service provision by managing, storing and providing information about Configuration Items and Service Assets throughout their life cycle. </li></ul></ul><ul><ul><li>This assists in providing logical model of the infrastructure, including the relevant relationships and dependencies that exist. </li></ul></ul>
  27. 27. Service Transition - Processes <ul><li>Change Management </li></ul><ul><ul><li>The goal is to ensure that standardized methods and procedures are used for controlled, efficient and prompt handling of all changes. </li></ul></ul><ul><ul><li>Various types of changes </li></ul></ul><ul><ul><ul><li>Normal change – A change that follows all steps of change process </li></ul></ul></ul><ul><ul><ul><li>Standard change – A pre-approved change that is low risk and relatively common, e.g. password reset request. Usually logged as Service Request. </li></ul></ul></ul><ul><ul><ul><li>Emergency change – A change that must be introduced as soon as possible. </li></ul></ul></ul>
  28. 28. Service Transition - Processes <ul><ul><li>Change Advisory Board(CAB) – A group that provides expert advice to the Change Manager. </li></ul></ul>
  29. 29. Service Transition - Processes <ul><li>Release and Deployment Management </li></ul><ul><ul><li>Goal is to deploy new releases into production, provide transition support to service operation, and enable its effective use in order to deliver value to the customer. </li></ul></ul><ul><ul><li>Various options for deployment of releases </li></ul></ul><ul><ul><ul><li>Big bang </li></ul></ul></ul><ul><ul><ul><li>Phased approach </li></ul></ul></ul><ul><ul><ul><li>Push approach </li></ul></ul></ul><ul><ul><ul><li>Pull approach </li></ul></ul></ul><ul><ul><ul><li>Automated </li></ul></ul></ul><ul><ul><ul><li>Manual </li></ul></ul></ul>
  30. 30. Service Transition - Processes <ul><li>Service Validation and Testing </li></ul><ul><ul><li>Main goal is to assure fitness for purpose and fitness for use </li></ul></ul>
  31. 31. Service Operation <ul><li>Primary objective is to enable effectiveness and efficiency in delivery and support of IT services. </li></ul><ul><li>Strategic objectives are ultimately realized through Service Operations, therefore making it critical phase. </li></ul><ul><li>Terminology: Incident vs Problem vs Error </li></ul><ul><ul><li>Incident is any occurrence which may cause interruption or degradation to an IT service </li></ul></ul><ul><ul><li>Problem is the unknown underlying cause of one or more incidents </li></ul></ul><ul><ul><li>Error is the known underlying cause of one or more incidents </li></ul></ul>
  32. 32. Service Operation - Functions <ul><li>Service Desk Function </li></ul><ul><ul><li>Service desk types </li></ul></ul><ul><ul><ul><li>Call centre – Handling/logging large volumes of calls. Low first-time resolution rate for calls and requests. </li></ul></ul></ul><ul><ul><ul><li>Help desk – Manage and coordinate incidents </li></ul></ul></ul><ul><ul><ul><li>Service desk – Wide variety of services offered. High first-time resolution rate for calls and requests. </li></ul></ul></ul><ul><ul><li>Service desk structures: Local, Central, Follow-the-sun </li></ul></ul>
  33. 33. Service Operation - Functions <ul><li>Technical Management </li></ul><ul><ul><li>Goal is to plan, implement and maintain a stable technical infrastructure to support the organization’s business processes </li></ul></ul><ul><ul><li>Examples of functions – Mainframe, Server, Network, Storage, Database, etc </li></ul></ul>
  34. 34. Service Operation - Functions <ul><li>IT Operations Management </li></ul><ul><ul><li>Goal is to perform daily operational activities needed to manage the IT infrastructure </li></ul></ul><ul><ul><li>Two types </li></ul></ul><ul><ul><ul><li>IT Operations control </li></ul></ul></ul><ul><ul><ul><ul><li>Console management </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Job scheduling </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Backup and restore </li></ul></ul></ul></ul><ul><ul><ul><li>Facilities management </li></ul></ul></ul><ul><ul><ul><ul><li>Data centers </li></ul></ul></ul></ul><ul><ul><ul><ul><li>Recovery sites </li></ul></ul></ul></ul>
  35. 35. Service Operation - Functions <ul><li>Application Management </li></ul><ul><ul><li>Goal is to help design, implement and maintain stable applications to support the organization’s business processes, e.g. HR apps, Business apps, etc </li></ul></ul>
  36. 36. Service Operation - Processes <ul><li>Event Management </li></ul><ul><ul><li>Goal is to provide the capability to detect events, make sense of them and determine the appropriate control action. </li></ul></ul><ul><ul><li>Different types events: Events that signify </li></ul></ul><ul><ul><ul><li>Regular operation </li></ul></ul></ul><ul><ul><ul><li>Warning </li></ul></ul></ul><ul><ul><ul><li>Exception </li></ul></ul></ul>
  37. 37. Service Operation - Processes <ul><li>Incident Management </li></ul><ul><ul><li>Goal is to restore normal service operation as quickly as possible and minimize adverse impact on business operations. </li></ul></ul><ul><ul><li>Setting priority of an incident </li></ul></ul><ul><ul><ul><li>Impact + Urgency = Priority </li></ul></ul></ul><ul><ul><li>Escalation </li></ul></ul><ul><ul><ul><li>Functional/Horizontal escalation </li></ul></ul></ul><ul><ul><ul><li>Hierarchical/Vertical escalation </li></ul></ul></ul>
  38. 38. Service Operation - Processes <ul><li>Problem Management </li></ul><ul><ul><li>Main goal is to eliminate recurring incidents, and prevent problems/incidents from happening </li></ul></ul><ul><ul><li>Difference from Incident management: </li></ul></ul><ul><ul><ul><li>Incident management only addresses the symptoms, while Problem management addresses the root-cause of the symptom so that incident doesn’t recur. </li></ul></ul></ul>
  39. 39. Service Operation - Processes <ul><li>Request Fulfillment </li></ul><ul><ul><li>Goal is to fulfill requests from end users using consistent and repeatable methods </li></ul></ul><ul><ul><li>It is related to fulfilling standard changes which are pre-approved for implementation, e.g. password reset request </li></ul></ul>
  40. 40. Service Operation - Processes <ul><li>Access Management </li></ul><ul><ul><li>Goal is to provide capabilities for the granting of authorized users the right to use a service while preventing access to non-authorized users. </li></ul></ul>
  41. 41. Continual Service Improvement <ul><li>Goal is to ensure continual improvements to IT Service Management Processes and IT Services </li></ul><ul><li>The Continual Service Improvement Model </li></ul>
  42. 42. Continual Service Improvement - Processes <ul><li>Service Level Management </li></ul><ul><ul><li>It proactively seeks and implements improvements to the level of service delivered to customers and users </li></ul></ul>
  43. 43. Continual Service Improvement - Processes <ul><li>Service Measurement and Reporting </li></ul><ul><ul><li>Goal is to coordinate the design of metrics, data collection and reporting activities from other processes and functions </li></ul></ul><ul><ul><li>Three types of metrics </li></ul></ul><ul><ul><ul><li>Technology metrics </li></ul></ul></ul><ul><ul><ul><li>Process metrics </li></ul></ul></ul><ul><ul><ul><li>Service metrics </li></ul></ul></ul>
  44. 44. Continual Service Improvement - Processes <ul><li>CSI (7 step) Improvement Process </li></ul><ul><ul><li>Goal is to coordinate a structured approach for improvements to IT services and ITSM processes </li></ul></ul><ul><ul><li>The Deming Cycle is used as foundation for continual improvement </li></ul></ul><ul><ul><ul><li>Plan(design)  Do(pilot)  Check(results)  Act(rollout) </li></ul></ul></ul><ul><ul><li>7 step improvement process </li></ul></ul><ul><ul><ul><li>Define what you should measure </li></ul></ul></ul><ul><ul><ul><li>Define what you can measure </li></ul></ul></ul><ul><ul><ul><li>Gather the data </li></ul></ul></ul><ul><ul><ul><li>Process the data (Frequency? Format? etc) </li></ul></ul></ul><ul><ul><ul><li>Analyze the data relationships/trends/targets met etc </li></ul></ul></ul><ul><ul><ul><li>Present and use the information, assessment, action plans etc </li></ul></ul></ul><ul><ul><ul><li>Implement corrective action </li></ul></ul></ul>

×