ITIL Framework and Processes Overview

ITIL

• ITIL is a framework for delivering IT services
• ITIL is considered the standard for organizations
• ITIL provides guidance on how to define, develop, build, and operate IT services
• Microsoft, IBM, and Hewlett-Packard Enterprise use ITIL for their internal operating guidelines

ITIL Processes

• ITIL processes are structured sets of activities to achieve specific objectives
• Processes take inputs and turn them into outputs
• Processes are a series of interconnected activities working toward a common goal
• Example: Cooking, where steps need to be followed to get the desired dish

ITIL Functions

• ITIL functions are teams or groups of people and the tools they use
• Examples of functions: Networking team, Java team, Web development team
• Teams are selected based on their expertise in a specific area
• Processes require functions to perform activities and provide resources

ITIL Practices (ITIL 4)

• In ITIL 4, practices replace processes and functions
• Practices extend processes by defining activities and bringing capabilities and tools together
• Practices combine functions and processes to achieve objectives

ITIL Guiding Principles

• Honesty & Visibility: Communicate progress, good or bad, and be open to feedback
• Think & Work Holistically: Connect all parts of the service delivery process to ensure alignment and avoid disruptions
• Keep it Simple & Practical: Avoid over-complicating processes, only include necessary steps, and eliminate non-value-adding activities
• Optimize & Automate: Optimize processes before automating them, automate repetitive tasks to free up human resources for complex work

DevOps

• DevOps combines development and operations teams to achieve an objective
• It builds on Continuous Delivery practices but focuses on an end-to-end automated approach
• DevOps and ITIL are complementary, not mutually exclusive

DevOps Technology

• DevOps utilizes various tools to support automation
• The choice of tools is crucial, as not all tools are compatible with all technologies
• Example: Git and Subversion are both used for source code versioning but operate differently

DevOps Principles (CALMS)

• Culture:
  • Taking responsibility for the entire product
  • Innovating and stepping outside of comfort zones
  • Communicating, collaborating, and building relationships
  • Experimenting
• Automation: Automating repetitive tasks that do not require human intelligence
• Lean:
  • Keeping things simple and straightforward
  • Reducing waste, including defects and convoluted processes
• Measurement: Measuring performance and outcomes to understand the effectiveness of the approach
• Sharing: Collaboration and knowledge sharing between teams

Source Code Version Control Systems

• Central Version Control System (CVCS):
  • Server-client relationship for storing and retrieving code
  • Developers need to check out, make changes, and check in code
• Distributed Version Control System (DVCS):
  • Each developer has the entire code on their computer
  • No check-out or check-in required
  • Faster accessibility, adding, combining, and delivering code

Explore the ITIL framework, which is essential for delivering IT services across organizations. This quiz will cover ITIL processes, functions, and the transition to ITIL 4 practices. Understand how these elements help in efficiently managing IT services.