nexus/Interview/Learning_ITIL_Course_Notes.md

# Learning ITIL — Course Notes

> LinkedIn Learning Course: *Learning ITIL (UPDATED 2025-10-30)* by Dave Filtorek
> Structured summaries of all 39 video transcripts across 5 chapters.

---

# Chapter 1: Introduction

## Chapter 1 — 1. ITIL Unveiled: A Journey Begins

**Core Insights**
- ITIL is the leading global source of IT service management (ITSM) guidance, with millions of certified professionals worldwide.
- ITIL has been widely adopted by organizations and embedded into IT management software by many vendors.
- The course covers both ITIL 4 (introduced 2019) and ITIL V3 (retired as a certification path in 2022 but still widely used in practice).
- The target audience is anyone who creates, delivers, supports, or improves IT services.

**Detailed Notes**

*Course Scope*
- Covers the "what" and "why" of ITIL, plus strategies for learning ITIL and getting certified.
- Dual-version coverage: ITIL 4 (current) and ITIL V3 (legacy but still relevant in many organizations).

**Key Terms/Concepts**
- **ITIL (Information Technology Infrastructure Library)**: The leading source of IT service management guidance.
- **ITIL 4**: The 2019 refresh of ITIL, the current framework version.
- **ITIL V3**: The prior version of ITIL, retired as a certification path in 2022 but still widely used in practice.

---

## Chapter 1 — 2. Stand Apart with ITIL Knowledge and Certification

**Core Insights**
- This course is designed as an orientation and planning tool for your ITIL journey.
- ITIL training may be required by your employer, or pursued voluntarily for career advancement.
- There are critical decision points along the ITIL certification path where wrong turns can be costly (time, money, effort).
- Content covers: high-level ITIL/service management concepts, ITIL V3 and ITIL 4 basics, learning strategies, exam prep, and exam-taking strategies.

**Detailed Notes**

*Decision Points*
- The ITIL certification path has branching choices — being well-informed at the start avoids costly missteps.

**Action Items**
- Treat this course as the foundation for planning your ITIL certification journey.
- Identify your motivation (employer requirement vs. self-driven career advancement) before choosing a path.

**Key Terms/Concepts**
- **ITIL certification path**: The structured progression of ITIL certifications, with multiple entry points and branching options.

---

## Chapter 1 — 3. What You Should Know

**Core Insights**
- No formal prerequisites, but familiarity with IT service outcomes and practices is helpful.
- Prior experience working within an IT function is beneficial.
- Multiple options exist for preparing for and passing the ITIL Foundation exam.

**Detailed Notes**

*Prerequisites*
- None required. Helpful background: understanding of IT service outcomes/practices, and experience in an IT function.

*Companion Courses*
- Additional ITIL courses cover practical application of ITIL concepts in real-world settings, filling gaps where ITIL mentions concepts but lacks implementation detail.

**Action Items**
- Evaluate which exam preparation path suits your learning style and schedule.

**Key Terms/Concepts**
- **ITIL Foundation exam**: The entry-level ITIL certification exam, covering core concepts at a high level.

---

## Chapter 1 — 4. Why Learn ITIL V3 When ITIL 4 Has Been Released

**Core Insights**
- ITIL V3 was retired as a certification path in 2022, but its practices and terminology remain widely used in organizations.
- Many organizations still expect IT professionals to know essential ITIL V3 terminology, principles, practices, models, and concepts.
- ITIL V3 concepts are embedded in many IT management software applications — knowing them reduces the learning curve for these tools.
- At the Foundation level, ITIL 4 covers only a subset of concepts that ITIL V3 covered in full.
- ITIL V3 fills in the blanks on still-valid concepts that have carried over into ITIL 4.

**Detailed Notes**

*Organizational Adoption*
- Many organizations continue to operate on ITIL V3 frameworks and expect staff to know V3 terminology and principles.

*Software Embedding*
- IT management tools (e.g., ServiceNow, BMC Remedy) embed ITIL V3 concepts — familiarity accelerates tool adoption.

*Certification Gap*
- ITIL 4 Foundation covers fewer concepts than ITIL V3 Foundation did; V3 knowledge complements ITIL 4 by filling coverage gaps.

**Action Items**
- Do not skip ITIL V3 content — it remains practically relevant even though it is no longer a certification path.

**Key Terms/Concepts**
- **ITIL V3 terminology/principles/practices/models**: The core vocabulary and frameworks from ITIL V3, still widely referenced in organizations and software.
- **ITIL 4 Foundation coverage gap**: ITIL 4 Foundation covers a subset of the concepts that ITIL V3 Foundation covered; the remainder is deferred to advanced ITIL 4 certifications.

---
# Chapter 2: Service Management and ITIL

## Chapter 2 — 1. Why Learn Key ITIL Service Management Concepts

**Core Insights**
- Organizations need a common language and shared framework to avoid massive waste from missteps and rework.
- Service management frameworks highlight what should exist in an IT environment (artifacts, practices, metrics) and what good looks like.
- Without understanding key concepts, IT professionals underserve themselves, their teams, and their organizations.

**Detailed Notes**

*Why Common Language Matters*
- When people assume basic things (roles, meeting agendas, documents, processes) contain crucial elements that they don't, problems arise.

*What Frameworks Provide*
- They show what artifacts, practices, and metrics should be present and adequate.
- They provide a frame of reference for what desirable states look like.

**Action Items**
- Learn the key concepts of service management as an IT professional.
- Use frameworks to understand what should exist and what good looks like in your IT environment.

**Key Terms/Concepts**
- **Service Management Frameworks**: Structured approaches that highlight what should exist in IT environments and define desirable states.
- **Artifacts**: Tangible or intangible deliverables that should be present in IT environments.
- **Practices**: Organizational resources and capabilities designed to perform work or accomplish objectives.

---

## Chapter 2 — 2. Key Concepts of Services

**Core Insights**
- An IT service is something a provider does for a consumer to create value for both parties.
- IT services have IT at their core (like Microsoft 365, AWS), while non-IT services may use IT in supporting roles.
- Services deliver value by facilitating outcomes consumers want while hiding costs and risks.
- Good providers present lower cost and risk compared to alternatives, including doing it yourself.

**Detailed Notes**

*What is an IT Service?*
- Something a provider (person, system, or combination) does for a consumer to create mutual value.
- Distinguished by IT being core and front-and-center, not just supporting.

*Value Delivery*
- Services facilitate outcomes consumers want to achieve.
- Consumers don't have to own or manage specific details of costs and risks.
- You subscribe to services because you calculate lower cost/risk and better outcomes vs. alternatives.

**Key Terms/Concepts**
- **IT Service**: A service where IT is core and central to delivery (e.g., Microsoft 365, AWS).
- **Provider**: Someone or something that provides a service.
- **Consumer**: Someone who uses and benefits from a service.
- **Value**: Benefits, usefulness, and importance delivered to stakeholders through outcomes.
- **Outcomes**: Results stakeholders want to achieve, enabled by services.

---

## Chapter 2 — 3. Key Concepts of IT Service Management (ITSM)

**Core Insights**
- Multiple stakeholders (provider, customer, sponsor, user, supplier, shareholders, society) all have stakes in service value.
- Value is subjective and resides in the stakeholder's mind — both reality AND perception must be managed.
- Outcomes are results enabled by outputs; outcomes matter more than just checking boxes.
- ITIL 4 introduced value co-creation (multi-directional flow) vs. ITIL v3's unidirectional provider-to-customer model.
- ITSM is implementing and managing the quality of IT services through organizational capabilities (people, technology, partners, value streams, processes).

**Detailed Notes**

*Stakeholders*
- **Provider**: Has stake in ensuring service is valuable, superior to alternatives, and profitable.
- **Customer**: Defines requirements and takes responsibility for outcomes.
- **Sponsor**: Authorizes budget for service consumption.
- **User**: Person who uses the service.
- **Supplier**: Provides services that the provider uses to deliver their own services.

*Value and Outcomes*
- Value = perceived benefits, usefulness, and importance to a stakeholder.
- Value is subjective — in the stakeholder's mind.
- Must deliver both good reality AND good perception.
- Value changes over time due to technology, alternatives, and changing needs.
- Outcome = result for a stakeholder enabled by outputs.
- Output = tangible or intangible deliverables.

*ITIL v3 vs. ITIL 4 Value Models*
- ITIL v3: Value flows unidirectionally from provider to customer.
- ITIL 4: Value is co-created by all stakeholders, flows multi-directionally.

*IT Service Management (ITSM)*
- Implementing and managing the quality of IT services that provide value stakeholders seek.
- Specialized organizational capabilities include: organizations & people, information & technology, partners & suppliers, value streams & processes.

**Key Terms/Concepts**
- **Stakeholders**: People and organizations with a stake in service value.
- **Value**: Perceived benefits, usefulness, and importance to a stakeholder (subjective, in the mind).
- **Outcome**: Result for a stakeholder enabled by outputs.
- **Output**: Tangible or intangible deliverables.
- **ITSM**: Implementing and managing quality of IT services through organizational capabilities.
- **Practice**: Set of organizational resources designed to perform work or accomplish objectives.

---

## Chapter 2 — 4. ITIL in a Nutshell: What's Unique

**Core Insights**
- ITIL is a set of publications describing best practices for IT service management, plus a training/certification/consulting industry.
- ITIL is ubiquitous (2+ million certified professionals), vendor-neutral, non-prescriptive, and represents best practice.
- ITIL is descriptive (what to do and why) not prescriptive (exactly how to do it).
- Best practice = what people do now that works, not bleeding-edge or leading-edge.

**Detailed Notes**

*What Makes ITIL Unique?*

**Ubiquitous**
- Most widely used service management approach.
- Over 2 million ITIL certified professionals.
- Embedded in RFPs and IT tools.

**Vendor-Neutral**
- Not driven by or intertwined with any particular vendor's products.
- Abstracted from specific technologies, widely applicable.

**Non-Prescriptive**
- Describes what to do and why, gives examples of how it may or may not work.
- Focus on getting outcomes (ends) correct, not prescribing 100% effective forever practices (means).

**Best Practice**
- Captures what people do now that works.
- Written by practitioners for practitioners.

**Action Items**
- Understand ITIL as descriptive guidance, not prescriptive rules.
- Adapt ITIL practices to your situation rather than applying dogmatically.

**Key Terms/Concepts**
- **ITIL**: Set of publications describing best practices for IT service management.
- **Best Practice**: What people do now that works; commonly accepted and implemented.
- **Vendor-Neutral**: Not tied to specific vendor products or technologies.
- **Non-Prescriptive**: Describes what to do and why, not exactly how to do it.

---

## Chapter 2 — 5. How ITIL Fits In and Why ITIL 4

**Core Insights**
- No serious competitors to ITIL; its uptake dwarfs alternatives.
- Many complementary frameworks exist (ISO 20000, DevOps, Agile, Lean) that map to ITIL.
- ITIL 4 (2019) addresses modern IT environments (hybrid: traditional, cloud, mobile) vs. ITIL v3 (2007) which suited traditional IT.
- Key difference: ITIL v3 had 26 processes + 4 functions in a lifecycle; ITIL 4 has 34 practices in a service value chain.
- IT service management is now a critical strategic capability for balancing predictability/quality with agility and faster time to value.

**Detailed Notes**

*ITIL's Position*
- No alternative IT service management frameworks compete seriously with ITIL.
- Many complementary frameworks and practices exist.
- ITIL has embraced DevOps, Agile, and Lean.

*ITIL v3 vs. ITIL 4*

**ITIL v3 (2007, updated 2011, retired 2022)**
- Most IT was physical and on-premise.
- 26 processes and 4 functions arranged in a lifecycle.

**ITIL 4 (2019)**
- IT environment is hybrid: traditional IT, cloud, and mobile.
- 34 practices (capabilities that can include processes and functions).
- Includes DevOps, Agile, and Lean practices.
- Organized in a service value chain.

**Key Terms/Concepts**
- **ITIL v3**: 2007 version with 26 processes + 4 functions in lifecycle; suited to traditional IT.
- **ITIL 4**: 2019 version with 34 practices in service value chain; addresses hybrid IT environments.
- **Service Value Chain**: ITIL 4's organizational model for practices.
- **Complementary Frameworks**: Other frameworks (ISO 20000, DevOps, Agile, Lean) that map to and work with ITIL.

---

## Chapter 2 — 6. What ITIL Means for Your Organization

**Core Insights**
- Organizations adopt ITIL for five key reasons: alignment, efficiency, reliability, agility, and compliance.
- Alignment: Better alignment among services, technology capabilities, customer needs, and all parts of organization/suppliers.
- Efficiency: Improved productivity through less translation overhead, fewer missteps/rework, and cost reduction.
- Reliability: Reduced firefighting, more reliable services, better commitments for mission/business-critical services.
- Agility: Increased responsiveness, faster changes and new capabilities while ensuring quality and continuous improvement.
- Compliance: Ready-made model for IT governance and regulatory compliance across jurisdictions.

**Detailed Notes**

*Alignment*
- Align services with what new technology makes possible.
- Align with what customers and users value and need.
- Align all parts of organization and suppliers around services and processes.
- Align around common language and key outcomes.

*Efficiency*
- Improve staff productivity through less language translation overhead.
- Fewer missteps and rework through shared terminology and practices.

*Reliability*
- Reduce time spent firefighting.
- More reliable services, especially for mission and business-critical services.

*Agility*
- Increase organizational responsiveness.
- Faster delivery of changes and new capabilities.
- Ensure quality while continuously improving.

*Compliance*
- Ready-made model to support IT governance initiatives.
- Facilitate meeting regulatory compliance requirements.

**Key Terms/Concepts**
- **Alignment**: Matching services, technology, customer needs, and organizational parts around common language and practices.
- **Efficiency**: Improved productivity and cost reduction through shared terminology and fewer missteps.
- **Reliability**: Consistent service delivery and ability to meet commitments.
- **Agility**: Responsiveness to incidents, faster delivery of changes, continuous improvement.
- **Compliance**: Meeting regulatory requirements and supporting IT governance.

---
# Chapter 3: Learning ITIL v3 Basic Concepts

## Chapter 3 — 1. Why Learn Key ITIL V3 Concepts

**Core Insights**
- ITIL v3 was retired as a certification path in 2022, but its terminology and concepts remain widely used in organizations and embedded in IT management tools.
- Without shared ITIL v3 understanding, teams waste time redefining terms, make mistakes, and create rework.
- Learning ITIL v3 basics enables better integration with colleagues, faster adoption of ITIL-based tools, and greater impact when improving capabilities.

**Key Terms/Concepts**
- **ITIL v3**: The 2007/2011 edition of ITIL, retired for certification in 2022 but still widely referenced.

---

## Chapter 3 — 2. Services, ITSM, the Four Ps, and the Service Life Cycle

**Core Insights**
- Services are how an organization presents itself and delivers value to customers (who pay) and users (who consume).
- Service management is the discipline of delivering that value well through processes, knowledge, and skilled people.
- The Four Ps (People, Processes, Products/Technology, Partners/Suppliers) define the proper scope of consideration for any IT decision.
- The ITIL v3 service lifecycle has five phases: Strategy → Design → Transition → Operation → Continual Improvement.

**Detailed Notes**

*The Four Ps*
- Use as a checklist for any project, change, or risk — e.g., when moving to production, check People (training, service desk readiness), Products (technical readiness), Partners (third-party readiness).

*Service Lifecycle*
- All value is realized in Operations, but quality depends on having the right Strategy, good Design, smooth Transition, and a Continual Improvement cycle.

**Action Items**
- Apply the Four Ps checklist in your next planning meeting to surface overlooked risks.

**Key Terms/Concepts**
- **Service**: A means of delivering value to customers without requiring them to own specific costs and risks.
- **Customer**: The person/group who pays for services.
- **User**: The person who uses services.
- **Four Ps**: People, Processes, Products (Technology), Partners (Suppliers).
- **Service Lifecycle**: Strategy → Design → Transition → Operation → Continual Service Improvement.

---

## Chapter 3 — 3. Terminology, Key Principles, and Models

**Core Insights**
- A shared, standardized ITIL terminology eliminates costly rework from miscommunication.
- ITIL v3 defines seven foundational principles and models: value creation, Four Ps, five aspects of service design, six-step CSI approach, CSFs/KPIs, baselines, and metrics.
- CSFs are things without which a service/process cannot succeed; KPIs are the key metrics used to manage CSFs.

**Detailed Notes**

*Five Aspects of Service Design*
1. Services
2. MIS & tools
3. Technology & management architectures
4. Processes
5. Measurement methods & metrics

*Six-Step CSI Approach*
1. What is the vision?
2. Where are we now?
3. Where do we want to be?
4. How do we get there?
5. Did we get there?
6. How do we keep the momentum going?

*CSFs & KPIs*
- Example — for health, blood is a CSF; blood pressure/sugar are KPIs.
- For change management, "change is under control" is a CSF; backed-out changes and emergency changes are KPIs.

*Baselines*
- Snapshots recorded at a point in time for later comparison — vital for troubleshooting and restoring to a known good state.

**Action Items**
- Audit your team's definitions of incident, change request, problem, event, known error, and service request — align them to ITIL.

**Key Terms/Concepts**
- **CSF (Critical Success Factor)**: Something without which a service/process cannot succeed.
- **KPI (Key Performance Indicator)**: The most important metrics used to manage the success of CSFs.
- **Baseline**: A snapshot recorded at a specific point in time as a reference for later comparison.

---

## Chapter 3 — 4. ITIL v3 Service Strategy Processes

**Core Insights**
- ITIL v3 defines 26 processes across the lifecycle plus 4 functions; the Foundation course covers 21 of 26 processes.
- The five Service Strategy processes define what services to offer, to whom, and how to fund and manage demand.

**Detailed Notes**

*The Five Strategy Processes*
1. **Strategy Management for IT Services**: Define a strategy that guides and aligns services, clarifies customers/markets, differentiates value proposition.
2. **Service Portfolio Management**: Maximize portfolio returns at acceptable risk; adjust the portfolio when conditions change.
3. **Financial Management for IT Services**: Accurately account for IT costs, map costs to services, support investment/budgeting decisions.
4. **Demand Management**: Understand and influence service demand; provide capacity to meet it.
5. **Business Relationship Management**: Maintain positive customer relationships by identifying needs and ensuring they are met through an appropriate service catalog.

**Key Terms/Concepts**
- **Service Portfolio**: The complete set of services an organization manages.
- **Demand Management**: Balancing capacity against service demand to avoid over- or under-provisioning.
- **Business Relationship Management**: Ongoing process of understanding and meeting customer needs.

---

## Chapter 3 — 5. ITIL v3 Service Design Processes

**Core Insights**
- The eight Service Design processes ensure new or changed services are designed holistically — covering services, tools, architectures, processes, and metrics.
- Design Coordination orchestrates all design activities; the remaining seven processes each own a specific design domain.

**Detailed Notes**

*The Eight Design Processes*
1. **Design Coordination**: Orchestrates all service design activities.
2. **Service Catalog Management**: Produces and maintains a single, current, accurate, widely-available service catalog.
3. **Service Level Management**: Keep paying customers satisfied by knowing what "done right" looks like, making only commitments you can keep.
4. **Capacity Management**: Ensure IT capacity matches business needs now and in the future — right resources, right time, right cost.
5. **IT Service Continuity Management (Disaster Recovery)**: Ensure IT can be restored to resume business after a major interruption.
6. **Information Security Management**: Align IT security with business security; protect confidentiality, integrity, and availability (CIA).
7. **Supplier Management**: Ensure all supplier contracts support business needs and that suppliers meet quality/cost commitments.

**Action Items**
- Verify your service catalog is current and accessible to approved users.
- Review supplier contracts against actual delivery.

**Key Terms/Concepts**
- **Service Catalog**: A single source of consistent information on all agreed services.
- **Service Level**: A committed measure of service quality (e.g., availability %, response time).
- **CIA Triad**: Confidentiality, Integrity, Availability — the three pillars of information security.

---

## Chapter 3 — 6. ITIL v3 Service Transition Processes

**Core Insights**
- The seven Service Transition processes move new or changed services from design into production while minimizing disruption and ensuring value.
- Transition bridges Strategy/Design intent with Operations reality.

**Detailed Notes**

*The Seven Transition Processes*
1. **Transition Planning & Support**: Coordinate and plan resources to deliver new/changed services into production.
2. **Change Management**: Minimize business disruption of changes; deliver changes quickly with quality.
3. **Service Asset & Configuration Management (SACM)**: Define, control, and maintain an accurate logical model (CMDB) of IT services, assets, and components.
4. **Release & Deployment Management**: Define and agree on release/deployment plans; ensure releases are put into production successfully.
5. **Service Validation & Testing**: Assure new/changed services are fit for purpose and fit for use.
6. **Service Evaluation**: Formally assess new/changed services to ensure risks are managed.
7. **Knowledge Management**: Ensure correct information reaches the right person at the right time for informed decisions.

**Action Items**
- Confirm your CMDB is accurate and actively maintained.
- Ensure release plans are agreed with stakeholders before deployment.

**Key Terms/Concepts**
- **CMDB (Configuration Management Database)**: The database storing the logical model of IT services, assets, and components.
- **Release**: A set of related changes deployed into production together.
- **Fit for Purpose / Fit for Use**: Utility (what the service does) and warranty (how well it does it).

---

## Chapter 3 — 7. ITIL v3 Service Operation Processes

**Core Insights**
- The five Service Operation processes run day-to-day IT: detecting events, restoring services, fulfilling requests, solving root causes, and controlling access.
- Incident management restores service quickly; problem management finds and resolves root causes.

**Detailed Notes**

*The Five Operation Processes*
1. **Event Management**: Manage state changes of significance through their lifecycle — detection, diagnosis, appropriate actions.
2. **Incident Management**: Minimize business disruption from unplanned interruptions — get users back up and running as quickly as possible.
3. **Request Fulfillment**: Help users request and receive standard services they are entitled to.
4. **Problem Management**: Resolve problems (the root cause of one or more incidents).
5. **Access Management**: Grant authorized users rights to use services while preventing access by non-authorized users.

**Action Items**
- Ensure clear handoff between incident management (restore service) and problem management (fix root cause).
- Automate recurring standard service requests.

**Key Terms/Concepts**
- **Event**: A state change that has significance for the management of IT services.
- **Incident**: An unplanned interruption to an IT service or a reduction in its quality.
- **Problem**: The root cause of one or more incidents.
- **Standard Service**: A pre-approved, low-risk service users can request (e.g., password reset, new laptop).

---

## Chapter 3 — 8. ITIL v3 Service Operation Functions

**Core Insights**
- ITIL v3 defines four functions for service operation: Service Desk, Technical Management, Operations Management, and Application Management.
- The Service Desk is the single point of contact for users; the other three manage infrastructure, day-to-day ops, and applications respectively.

**Detailed Notes**

*The Four Functions*
1. **Service Desk**: Dedicated staff handling service activities via phone, web, or automated events.
2. **Technical Management**: Teams providing technical expertise and overall management of the IT infrastructure.
3. **Operations Management**: Team responsible for day-to-day operational activities — backups/restores, monitoring jobs/systems, facility management.
4. **Application Management**: Team managing applications through their lifecycle — a DevOps-like concept from ITIL circa 2007.

**Action Items**
- Clarify which tier handles which issues across Service Desk, Technical Management, and Application Management.

**Key Terms/Concepts**
- **Function**: A department or organizational unit (as opposed to a process, which crosses functions).
- **Service Desk**: Single point of contact between users and IT.
- **Technical Management**: Custodians of the IT infrastructure.
- **Application Management**: Custodians of applications through their lifecycle.

---

## Chapter 3 — 9. ITIL v3 Continual Improvement Process

**Core Insights**
- There is only one process in the Continual Service Improvement (CSI) lifecycle phase: the Seven-Step Improvement Process.
- Its goal is to increase efficiency, effectiveness, and cost-effectiveness by continually measuring and improving performance.

**Detailed Notes**

*Seven-Step Improvement Process*
- Defines and manages the steps to identify, define, gather, process, analyze, present, and implement improvements across processes, services, and IT infrastructure.

**Action Items**
- Establish a regular CSI review cadence using the seven-step approach.

**Key Terms/Concepts**
- **CSI (Continual Service Improvement)**: The lifecycle phase dedicated to ongoing improvement of services and service management.
- **Seven-Step Improvement Process**: The sole CSI process — a structured method for identifying and implementing improvements.

---

## Chapter 3 — 10. ITIL v3 Roles, Technology, and Architecture

**Core Insights**
- ITIL v3 defines three process-related roles (owner, manager, practitioner) plus a Service Owner role.
- RACI (Responsible, Accountable, Consulted, Informed) is the model for sorting role involvement against activities.
- Technology and automation cover scripting, tooling, and automated responses to demand.

**Detailed Notes**

*Process Roles*
- **Process Owner**: Accountable for the process.
- **Process Manager**: Responsible for day-to-day management of the process.
- **Process Practitioner**: Performs the process activities.
- **Service Owner**: Accountable for a specific service throughout its lifecycle.

*Technology & Automation*
- Automated resource capacity responding to demand; automated self-service off-hours.
- Automation for knowledge capture, optimization, measurement, improvement, and unnecessary variation reduction.

**Action Items**
- Assign a RACI matrix for each key process.
- Identify automation candidates: repetitive tasks, off-hours service requests, knowledge capture.

**Key Terms/Concepts**
- **RACI**: Responsible, Accountable, Consulted, Informed — a matrix for clarifying role involvement.
- **Process Owner**: Accountable for ensuring a process meets its objectives.
- **Service Owner**: Accountable for a specific service's end-to-end delivery and improvement.

---

## Chapter 3 — 11. ITIL v3 Certification Scheme

**Core Insights**
- The ITIL v3/2011 certification scheme (launched 2007, revised 2011, retired 2022) is a five-level, points-based system: Foundation → Practitioner → Intermediate → Expert (22 points) → Master.
- Over 2 million hold Foundation; Experts number in the thousands; Masters in the hundreds.
- Intermediate has two streams: Lifecycle (one cert per lifecycle phase) and Capability (four clustered certs: OSA, PPO, RCV, SOA).

**Detailed Notes**

*Certification Levels*
- **Foundation**: Knowledge/comprehension of essential ITIL v3 concepts, terminology, processes.
- **Practitioner**: Optional; emphasizes applying CSI principles.
- **Intermediate — Lifecycle Stream**: Five certs based on the five lifecycle phases.
- **Intermediate — Capability Stream**: Four certs clustering processes across the lifecycle:
  - **OSA (Operational Support & Analysis)**: Event, incident, request, problem, access management.
  - **PPO (Planning, Protection & Optimization)**: Capacity, availability, continuity, security, demand, risk management.
  - **RCV (Release, Control & Validation)**: Change, release & deployment, validation & testing, SACM, knowledge management.
  - **SOA (Service Offerings & Agreements)**: Portfolio, service level, catalog management; demand, supplier, financial management.
- **MALC (Managing Across the Lifecycle)**: Capstone course required to reach ITIL Expert.
- **Expert**: 22+ points; completed intermediate units + Foundation + MALC.
- **Master**: Assesses ability to apply and analyze ITIL concepts in new areas.

**Key Terms/Concepts**
- **ITIL Foundation**: Entry-level certification covering ITIL v3 essentials.
- **ITIL Expert**: 22+ credit points; demonstrates deep ITIL knowledge across the lifecycle.
- **ITIL Master**: Highest level; demonstrates ability to apply ITIL in real-world, novel situations.
- **MALC**: Managing Across the Lifecycle — the capstone exam for ITIL Expert.

---
# Chapter 4: ITIL v4 — Structured Summaries

## Chapter 4: ITIL v4 — 1. Why Learn Key ITIL 4 Concepts

**Core Insights**
- ITIL v3 (2007) targeted traditional IT: physical, on-premise, no mobile apps
- Today's environment is primarily cloud and mobile with vestiges of physical infrastructure
- Management has shifted from waterfall processes/departments to practices (DevOps, Agile, Lean)
- Using v3 practices on modern tech is a complete mismatch (like fixing a Tesla with 2007 diesel tools)
- New terminology and practices are needed for digital organizations

**Detailed Notes**

*Historical Context*
- ITIL v3 released 2007 for traditional IT environments
- Target environment was largely physical, on-premise, no mobile apps

*Current Environment*
- Primarily cloud and mobile
- Some physical on-premise equipment remains
- Digital organizations face new challenges requiring new practices

*Management Shift*
- From: waterfall processes, departments/functions
- To: practices including DevOps, Agile, Lean ways of working
- Best practices = what people typically do now that works

**Action Items**
- Learn new ITIL 4 terminology and practices suited for digital organizations
- Understand how practices address challenges digital organizations face

**Key Terms/Concepts**
- **Best practices**: What people typically do now that works
- **Traditional IT**: Physical, on-premise infrastructure (pre-cloud/mobile era)
- **Digital organizations**: Organizations operating in cloud/mobile environments

---

## Chapter 4: ITIL v4 — 2. Why ITIL 4

**Core Insights**
- ITIL v3 released 2007, revised 2011, retired 2022; ITIL 4 released 2019
- ITIL 4 is lighter weight: single 200-page book vs v3's 2,000 pages across 5 books
- Course reduced from 3 days to 2 days
- Exam format unchanged: 40 questions, multiple choice, 1 hour, 65% to pass
- IT service management is now a critical strategic capability

**Detailed Notes**

*Timeline*
- ITIL v3: released 2007, revised 2011, retired as certification path 2022
- ITIL 4: released 2019

*Environmental Changes Since 2007*
- Cloud computing, IaaS, machine learning, blockchain
- New practices: DevOps, Lean, Agile
- IT-enabled services are integral to business
- Need to balance stability/predictability/quality with agility and faster time-to-value

*Key Differences: ITIL 4 vs v3 Foundation*
1. **Source material**: ITIL 4 = one 200-page book; v3 = nearly 2,000 pages across 5 books
2. **Course length**: ITIL 4 = 2 days; v3 = 3 days
3. **Exam**: Same format (40 questions, 65% to pass), different topics

*Strategic Importance*
- IT service management is now a critical strategic capability
- Helps visualize and manage key outcomes
- Balances stability, predictability, quality with operational agility

**Action Items**
- Compare ITIL 4 exam specification vs v3 syllabus modules to understand topic differences

**Key Terms/Concepts**
- **ITIL 4 Foundation**: 2019 release, lighter weight approach aligned with agile organizations
- **Service management as strategic capability**: Critical for balancing stability with agility

---

## Chapter 4: ITIL v4 — 3. What to Look for in ITIL 4

**Core Insights**
- Individuals seek ITIL 4 for certification, career advancement, and better team integration
- Teams benefit from shared framework, common terminology, reduced waste
- Organizations gain alignment, efficiency, predictability, agility, and compliance enablement
- Two-step approach: (1) understand terminology/principles/practices, (2) apply to assess and improve capabilities

**Detailed Notes**

*Benefits by Stakeholder*

**Individuals**
- Training and certification to stand out
- Demonstrate knowledge
- Career advancement
- Better integrate work into teams and organization

**Teams**
- Everyone on same page with shared framework
- Avoid misunderstandings, missteps, waste
- Shared understanding of concepts and terminology
- Basis for collaboration with other groups using ITIL practices

**Organizations**
- Alignment of people's work
- Increased efficiency and predictability
- Agility to respond to business and technology change
- Basis for regulatory compliance

*Implementation Steps*
1. Understand ITIL terminology, principles, practices, concepts, and models
2. Apply understanding to assess and improve capabilities

**Action Items**
- Seek to understand ITIL 4 terminology, principles, practices, concepts, and models
- Put understanding to work in assessing and improving capabilities

**Key Terms/Concepts**
- **Shared framework**: Common language and approach enabling team collaboration
- **Capability assessment**: Using ITIL understanding to evaluate and improve organizational capabilities

---

## Chapter 4: ITIL v4 — 4. What's Different in ITIL 4 Foundation: Part 1

**Core Insights**
- Four dimensions of service management replace v3's four P's
- Service value chain (6 activities) replaces v3's 5-part service lifecycle
- New pairings: information + technology, value streams + processes
- Engage activity is new, emphasizing customer/user experience
- Modern organizations work in sprints with feedback loops, not waterfall phases

**Detailed Notes**

*Four Dimensions of Service Management (replaces Four P's)*
1. Organizations and people (≈ People)
2. Information and technology (≈ Products/Technology)
3. Partners and suppliers (≈ Partners)
4. Value streams and processes (≈ Process)

Key change: pairing information with technology, and value streams with processes

*Service Value Chain (replaces Service Lifecycle)*

| ITIL 4 Value Chain Activity | ITIL v3 Equivalent |
|---|---|
| Plan | Strategy |
| Improve | Continual Service Improvement |
| Engage | NEW (customer/user experience emphasis) |
| Design and transition | Design + Transition phases |
| Obtain/build | Part of Design phase |
| Deliver and support | Service Operation |

*Why the Changes?*
- Current effective organizations work in sprints, smaller frequent chunks
- Lots of feedback loops
- No large waterfall distance between strategy and improvement
- Strategy and improvement happen together, go into product backlog together

**Action Items**
- Understand how each value chain activity maps to modern agile/DevOps ways of working

**Key Terms/Concepts**
- **Four dimensions of service management**: Organizations & people, information & technology, partners & suppliers, value streams & processes
- **Service value chain**: Six interconnected activities replacing the v3 lifecycle
- **Engage**: New value chain activity focused on stakeholder relations and customer/user experience

---

## Chapter 4: ITIL v4 — 5. What's Different in ITIL 4 Foundation: Part 2

**Core Insights**
- Five-part service value system (SVS) packages elements v3 covered separately
- Practices replace both processes and functions from v3
- 7 guiding principles (adapted from v3 Practitioner's 9) are new to Foundation
- ITIL 4 Foundation has 19 key terms + 7 principles vs v3's 34 terms
- No specific service/process roles coverage in Foundation (reflects shared ownership in DevOps/Agile)
- ITIL 4 is prescriptive ("optimize and automate") vs v3's descriptive stance

**Detailed Notes**

*Service Value System Components*
1. **Guiding principles**: Maxims guiding organizations across changing circumstances
2. **Governance**: How organization is directed and controlled
3. **Service value chain**: Interrelated activities to create and deliver value
4. **Practices**: Organizational resources for performing work (replace processes + functions)
5. **Continual improvement**: Recurring activity at all levels

*Key Terminology Changes*
- v3 Foundation: 34 key terms, principles, and models
- ITIL 4 Foundation: 19 key terms + 7 guiding principles
- 7 guiding principles adapted from v3 Practitioner's 9 principles
- Terms like output, risk, service, service management were covered in v3 even if not listed

*Roles Coverage*
- v3 Foundation: extensive coverage of service/process roles and RACI
- ITIL 4 Foundation: no equivalent coverage
- Reflects DevOps/Agile/Lean ideas of shared ownership and less hierarchical approach

*Technology and Architecture → Optimize and Automate*
- v3: covered technology and architecture (optimization through automation)
- ITIL 4: guiding principle "optimize and automate"
- Shift from a "thing" to an "action statement/directive"
- Huge in DevOps, Lean, Agile, and modern business/IT

*Descriptive vs Prescriptive*
- v3 positioned itself as descriptive (what to do and why, not how)
- ITIL 4 with 7 principles becomes prescriptive (tells you to do something)
- Still doesn't prescribe how (varies by technology/platform/organization)
- Continues to point out key outcomes and fundamental principles/practices

**Action Items**
- Focus on grasping key outcomes and fundamental principles/practices
- Cherry-pick ideas for action from the content

**Key Terms/Concepts**
- **Service Value System (SVS)**: How all components and activities work together as a system to enable value creation
- **Practices**: Organizational resources designed for performing work (replaces processes + functions)
- **Guiding principles**: Universal and enduring maxims guiding organizations across all circumstances
- **Prescriptive vs descriptive**: ITIL 4 tells you to do something (prescriptive); v3 described what to do

---

## Chapter 4: ITIL v4 — 6. ITIL 4 vs v3: Practices versus Processes

**Core Insights**
- ITIL 4 defines 34 management practices (14 general, 17 service management, 3 technical)
- 15 practices covered at Foundation level
- Practices replace v3's 26 processes + 4 functions
- Unlike v3, practices are NOT aligned to specific value chain activities (they fire across all activities)
- Some v3 processes dropped; IT asset management added; release and deployment separated
- Fundamental shift toward lighter weight, DevOps/Agile/Lean-aligned approach

**Detailed Notes**

*Practice Categories*
- **General management practices** (14): Adopted/adapted from general business management
- **Service management practices** (17): Developed in service management industry
- **Technical management practices** (3): Adapted from technology management for service purposes

*v3 Structure (2011 edition)*
- 5 lifecycle phases: strategy, design, transition, operation, improvement
- 26 processes + 4 functions arranged within lifecycle
- Processes/functions placed in lifecycle where they first become important

*ITIL 4 Structure*
- 34 practices (15 at Foundation)
- 6-part service value chain (not lifecycle)
- No alignment of practices to specific value chain activities
- Practices and outcomes they support fire in ALL value chain activities
- Effort/attention/nature of tasks varies by activity and over time

*v3 Processes/Functions NOT in ITIL 4*
- Demand management
- Design coordination
- Service catalog management
- Transition planning and support
- Validation and testing
- Change evaluation
- Knowledge management
- Access management
- 3 of 4 functions: IT operations, applications management, technical management

*New/Changed in ITIL 4*
- **IT asset management**: New addition (was missing from ITIL, established industry practice)
- **Release management**: Separated from deployment
- **Deployment management**: Separated from release (honors DevOps continuous deployment)
- **Software development and management**: ≈ v3's application management
- **Infrastructure and platform management**: ≈ v3's technical management

*Process Definition (unchanged from v3)*
A set of interrelated or interacting activities that transforms one or more defined inputs into defined outputs through a defined series of actions and their dependencies.

*Practice Definition*
A set of organizational resources designed for performing work or accomplishing an objective.

**Action Items**
- Focus on outcomes for each practice
- Work to align resources to enable those outcomes

**Key Terms/Concepts**
- **Management practice**: A set of organizational resources designed for performing work or accomplishing an objective
- **Process**: A set of interrelated/interacting activities transforming inputs into outputs
- **Function** (v3): An organizational unit or department

---

## Chapter 4: ITIL v4 — 7. ITIL 4: Service Management Four Dimensions

**Core Insights**
- Four dimensions reposition v3's four P's for holistic service management
- Each dimension represents a perspective critical to delivering value efficiently and effectively
- All four dimensions must be considered for any decision or action in service management
- Dimensions apply to both the services themselves and the management of those services

**Detailed Notes**

*Dimension 1: Organizations and People*
- Ensure organization is well structured and managed
- Define roles, responsibilities, systems of authority and communication
- Align people's capacity and competence with strategy and operating model
- Ensure right culture to support objectives

*Dimension 2: Information and Technology*
- Applies to information/technology that ARE part of services
- Also applies to information/technology USED TO MANAGE services
- For services: information created, managed, used during provision and consumption
- Technologies supporting services
- For service management: workflow systems, knowledge bases, inventory systems, communication systems, analytical tools

*Dimension 3: Partners and Suppliers*
- Design, development, deployment, delivery, support, and continual improvement of services
- Incorporates contracts and other agreements between organization and partners/suppliers

*Dimension 4: Value Streams and Processes*
- Activities, workflows, controls, and procedures needed to achieve agreed objectives
- Focus on: what activities the organization undertakes, how they're organized
- Ensures value creation for all stakeholders efficiently and effectively

**Action Items**
- Consider all four dimensions for every service management decision or action

**Key Terms/Concepts**
- **Four dimensions of service management**: Organizations & people, information & technology, partners & suppliers, value streams & processes
- **Holistic approach**: Considering all dimensions together for effective service management

---

## Chapter 4: ITIL v4 — 8. ITIL 4: Service Value System

**Core Insights**
- Service Value System (SVS) describes how all components work together as a system
- Key input: opportunity and demand; Key output: value for customers and stakeholders
- Five components: guiding principles, governance, service value chain, practices, continual improvement
- Continual improvement is a recurring activity at ALL levels
- SVS must function as a system for service management to work correctly

**Detailed Notes**

*Service Value System Overview*
- Input: opportunity and demand
- Output: value for customers and other stakeholders
- Describes how all components and activities work together as a system to enable value creation

*Five Components*

1. **Guiding Principles** (7)
   - Recommendations guiding organizations in ALL circumstances
   - Apply regardless of changes in goals, strategies, work type, or management structure

2. **Governance**
   - How an organization is directed and controlled
   - Activities enable continual alignment of operations with strategic direction
   - Strategic direction set by governing body

3. **Service Value Chain**
   - Set of interconnected activities
   - Delivers valuable product/service to consumers
   - Facilitates value realization

4. **Practices**
   - Sets of organizational resources for performing work or accomplishing objectives
   - What you do to achieve and sustain outcomes over time and through changing circumstances

5. **Continual Improvement**
   - Recurring organizational activity performed at ALL levels
   - Ensures performance meets stakeholder expectations over time
   - Supported by ITIL continual improvement model
   - Slight revamp of v3 approach, starts with "what is the vision?"

**Action Items**
- Ensure all five SVS components work together as an integrated system

**Key Terms/Concepts**
- **Service Value System (SVS)**: How all components and activities work together as a system to enable value creation
- **Opportunity and demand**: Key inputs to the SVS
- **Value**: Key output of the SVS for customers and stakeholders
- **Governance**: How an organization is directed and controlled

---

## Chapter 4: ITIL v4 — 9. ITIL 4: Service Value Chain

**Core Insights**
- Six value chain activities replace v3's five-phase lifecycle
- Each activity has scope across all four dimensions of service management
- Engage is new, emphasizing customer/user experience and stakeholder relations
- Design & transition combined; obtain/build separated (honoring DevOps continuous delivery)
- Stakeholders include customers, users, sponsors, provider employees, community, shareholders

**Detailed Notes**

*Six Value Chain Activities*

1. **Plan** (≈ v3 Strategy)
   - Align around vision, status, and improvement direction
   - Scope: all four dimensions (orgs & people, info & tech, partners & suppliers, value streams & processes)

2. **Improve** (≈ v3 Continual Service Improvement)
   - Same scope as plan: all four dimensions
   - Continuous improvement across all areas

3. **Engage** (NEW)
   - Stakeholder relations and customer/user experience
   - Stakeholders include:
     - Service consumers: customers (pay bills), users (use services), sponsors (authorize budgets)
     - Provider and its employees
     - Community and society at large
     - Charitable organizations
     - Shareholders

4. **Design and Transition** (≈ v3 Design + Transition combined)
   - Honors DevOps/Lean/Agile values: design and transition happen continuously, often, quickly
   - Not just at service level, but also at feature and service quality level
   - Service qualities = non-functional requirements / the "-ilities" (accessibility, availability, etc.)

5. **Obtain/Build** (separated from v3 Design phase)
   - Obtaining and building service components as distinct activity

6. **Deliver and Support** (≈ v3 Service Operation)
   - Day-to-day delivery and support of services

**Action Items**
- Understand how each value chain activity applies across all four dimensions
- Recognize that design/transition and obtain/build operate at feature level, not just service level

**Key Terms/Concepts**
- **Service value chain**: Six interconnected activities (plan, improve, engage, design & transition, obtain/build, deliver & support)
- **Service qualities / "-ilities"**: Non-functional requirements like accessibility, availability
- **Service consumers**: Customers (pay), users (use), sponsors (authorize budgets)

---

## Chapter 4: ITIL v4 — 10. ITIL 4: Guiding Principles

**Core Insights**
- Seven universal and timeless guiding principles for all organizations in all circumstances
- Adapted from v3 Practitioner's 9 principles (reduced to 7, some combined, one added)
- Each principle acts as a "North Star" informing millions of daily decisions
- Principles echo DevOps, Agile, and Lean values throughout
- "Optimize and automate" is new, replacing "design for experience"

**Detailed Notes**

*The Seven Guiding Principles*

1. **Focus on Value**
   - Every individual and team must relentlessly focus on value
   - Eliminate/reduce things that don't add value
   - Add/amplify things that do add value for stakeholders

2. **Start Where You Are**
   - Like city planning: can't bulldoze everything and start over
   - Leverage existing services, processes, programs, projects, and people
   - Initiatives uninformed by what exists waste many resources

3. **Progress Iteratively with Feedback**
   - Echoes DevOps/Agile/Lean values
   - Many feedback loops driving what you create and improve
   - Work in smaller chunks, smaller sprint cycles
   - Deliver outcomes stakeholders want, even if they changed
   - Not just checkbox delivery of X, Y, Z that may no longer be on target

4. **Collaborate and Promote Visibility**
   - Echoes DevOps/Agile/Lean practices
   - Visible management tools, communication, collaboration
   - Break down silos
   - Drive toward shared vs competing objectives
   - Combined from v3's "collaborate" and "be transparent"

5. **Think and Work Holistically**
   - From systems thinking (heavily cited in DevOps community)
   - Can de-optimize the whole by optimizing just a part
   - Think up and out (synthetic thinking), not just down and in (analytical thinking)
   - Work on the system, not just its parts

6. **Keep It Simple and Practical**
   - Eliminate unnecessary complexity and bloated ways
   - Focus on ends/means or outcomes
   - Don't lose the "why" and "for whom" in over-focus on activities/means

7. **Optimize and Automate** (NEW)
   - Aligns with v3's technology and automation concept
   - Aligns with "A" for Automate in DevOps CAMS model
   - Aligns with Lean's core principle of eliminating waste
   - Use resources (especially human) to best effect
   - Relentless focus on automation to drive out variation, dependencies, waste
   - Use human intervention only where it contributes value

*Evolution from v3 Practitioner (9 → 7)*
- "Collaborate" + "Be transparent" → "Collaborate and promote visibility"
- "Design for experience" → replaced
- "Observed directly" → removed (folded elsewhere)
- "Optimize and automate" → added

**Action Items**
- Apply all seven principles as North Stars for daily decisions
- Use principles to evaluate and improve current practices

**Key Terms/Concepts**
- **Guiding principle**: A universal and enduring maxim guiding an organization across changing time and circumstances
- **Synthetic thinking**: Thinking up and out, understanding the whole system context
- **Analytical thinking**: Thinking down and in, analyzing parts
- **CAMS**: DevOps value model (Culture, Automation, Measurement, Sharing)

---

## Chapter 4: ITIL v4 — 11. ITIL 4: 15 Practices Covered at Foundation Level (Part 1)

**Core Insights**
- First 8 of 15 Foundation-level practices covered
- All repositioned as practices (vs v3's processes/functions)
- Only new addition: IT asset management
- Release and deployment separated (honoring DevOps continuous deployment)
- Information security management covers CIA triad (confidentiality, integrity, availability)

**Detailed Notes**

*Practice 1: Information Security Management*
- ≈ v3 information security management process
- **Confidentiality**: Protecting information assets from bad actors
- **Integrity**: Protecting assets from damage (e.g., hacker randomizing customer data)
- **Availability**: Ensuring no denial of access for authorized people

*Practice 2: Relationship Management*
- Extends v3's business relationship management
- Now includes ALL stakeholders (not just business):
  - Service consumers: customers, users, sponsors
  - Provider and employees
  - Community and society
  - Charitable organizations
  - Shareholders

*Practice 3: Supplier Management*
- ≈ v3 supplier management process

*Practice 4: IT Asset Management* (NEW to ITIL)
- IT asset: any valuable component contributing to IT product/service delivery
- Well-established industry discipline
- Related to but distinct from service configuration management

*Practice 5: Monitoring and Event Management*
- ≈ v3 event management process

*Practice 6: Release Management*
- ≈ release portion of v3's release and deployment management
- Collection of related changes managed at release zoom level
- Can pilot, rollback, deploy at release level (not just individual changes)

*Practice 7: Service Configuration Management*
- ≈ v3 service asset and configuration management
- Ensures accurate/reliable information about service configurations available when needed

*Practice 8: Deployment Management*
- ≈ deployment portion of v3's release and deployment management
- Separation honors DevOps practices: continuous deployment, continuous integration, continuous testing
- Move value faster in smaller chunks (individual features, not just full releases)

**Action Items**
- Understand CIA triad for information security
- Distinguish between release management (collection of changes) and deployment management (individual feature delivery)

**Key Terms/Concepts**
- **CIA triad**: Confidentiality, Integrity, Availability
- **IT asset**: Any valuable component contributing to IT product/service delivery
- **Release**: A collection of related changes deployed together
- **Configuration item**: Component that must be managed to deliver an IT service

---

## Chapter 4: ITIL v4 — 12. ITIL 4: 15 Practices Covered at Foundation Level (Part 2)

**Core Insights**
- Remaining 7 of 15 Foundation-level practices
- Service desk repositioned from function (v3) to practice (ITIL 4)
- Change management renamed to change enablement (reflects outcome focus)
- Incident vs problem: incidents are symptoms, problems are root causes
- Known error = analyzed but unresolved problem

**Detailed Notes**

*Practice 9: Incident Management*
- ≈ v3 incident management process
- Gets things broken fixed quickly
- "Broken" ranges from service down to individual user trouble with features

*Practice 10: Problem Management*
- ≈ v3 problem management process
- Goes after root cause of one or more incidents
- Incidents = specific instances of impact (symptoms)
- Problems = underlying cause

*Practice 11: Service Request Management*
- ≈ v3 request fulfillment process
- Effective/efficient way to provide users with things they're entitled to based on subscription

*Practice 12: Service Level Management*
- ≈ v3 service level management process
- Make and keep good commitments around service levels
- Requires sometimes difficult conversations about wherewithal and associated cost

*Practice 13: Service Desk*
- v3: a function (organizational unit/department)
- ITIL 4: a practice
- Captures demand for incident resolution and service requests
- Acts as communication concentration point between provider and users
- Repositioning reflects trends: chatbots and portals fully represent support face

*Practice 14: Change Enablement*
- ≈ v3 change management process
- Focus: minimizing business disruption of changes, knowing what changed
- Name shift: "management" → "enablement"
- Reflects true outcome: enable needed changes, balancing speed, quality, and risk

*Practice 15: Continual Improvement*
- ≈ v3 continual service improvement process
- Explicit process allocating time, resources, funding for improvements
- Improvements across all four dimensions of service management

**Action Items**
- Distinguish incident management (fix broken things fast) from problem management (find root cause)
- Understand service desk as practice, not just a department
- Apply change enablement mindset: enable changes, don't just manage them

**Key Terms/Concepts**
- **Incident**: Unplanned interruption or quality reduction (symptom)
- **Problem**: Cause or potential cause of one or more incidents (root cause)
- **Known error**: Problem that has been analyzed but not yet resolved
- **Change enablement**: Enabling needed changes while balancing speed, quality, and risk
- **Service desk** (as practice): Capturing demand and serving as communication concentration point

---

## Chapter 4: ITIL v4 — 13. ITIL 4: Terminology and Model

**Core Insights**
- Seven key terms defined for Foundation level
- Continual improvement model has 7 steps (added "take action" step vs v3)
- Clear distinction between incident (symptom) and problem (cause)
- Known error = analyzed but unresolved problem
- Configuration items include hardware, software, networks, buildings, people, services, suppliers, documentation

**Detailed Notes**

*Key Term Definitions*

1. **IT Asset**: Any financially valuable component that can contribute to delivery of an IT product or service
   - Subset of service components that are financially valuable

2. **Event**: Any change of state that has significance for management of a service or configuration item
   - Types: informational (batch job completed), warnings (circuit at 10%), exceptions (service down)

3. **Configuration Item (CI)**: Any service component that must be managed to deliver an IT service
   - Examples: hardware, software, networks, buildings, people, services, suppliers, documentation

4. **Change**: Addition, modification, or removal of anything that could directly or indirectly affect services

5. **Incident**: Unplanned interruption to a service or reduction in service quality
   - Something important is broken/down/degraded, affecting or potentially affecting service quality

6. **Problem**: Cause or potential cause of one or more incidents
   - Related to but distinct from incidents
   - Incidents impact users/business processes and must be resolved for normal activity
   - Can resolve incident (restore service) without finding underlying cause

7. **Known Error**: A problem that has been analyzed but not yet resolved
   - Contrast: problem = unknown error; known error = analyzed but unresolved

*Continual Improvement Model Steps*
1. What is the vision?
2. Where are we now?
3. Where do we want to be?
4. How do we get there?
5. Take action (NEW step added in ITIL 4)
6. Did we get there?
7. Keep the momentum going

**Action Items**
- Use precise definitions when discussing incidents, problems, and known errors
- Apply continual improvement model with the new "take action" step

**Key Terms/Concepts**
- **IT asset**: Financially valuable component contributing to IT service delivery
- **Event**: Change of state with significance (informational, warning, exception)
- **Configuration item (CI)**: Service component managed to deliver IT service
- **Change**: Addition/modification/removal affecting services
- **Incident**: Unplanned interruption or quality reduction
- **Problem**: Cause of one or more incidents
- **Known error**: Analyzed but unresolved problem
- **Continual improvement model**: 7-step structured approach to implementing improvements

---

## Chapter 4: ITIL v4 — 14. ITIL 4 Certification Scheme

**Core Insights**
- Foundation is entry-level; not everyone needs to go beyond it
- Two main streams: Managing Professional (MP) and Strategic Leader (SL)
- ITIL Strategist (Direct, Plan, Improve) is common to both streams
- ITIL Master is highest achievement, requiring all designations
- ITIL Leader module requires 3 years managerial experience

**Detailed Notes**

*Certification Path*

**Foundation Level**
- Entry-level certification
- General awareness of key elements, concepts, terminology
- Prerequisite for all advanced modules

**Managing Professional (ITIL MP) Stream**
- For IT practitioners in technology/digital teams across businesses
- Practical and technical knowledge for successful IT projects, teams, workflows
- Requires 4 modules:
  1. Create, Delivery and Support
  2. Drive Stakeholder Value
  3. High Velocity IT
  4. ITIL Strategist: Direct, Plan and Improve (shared with SL stream)

**Strategic Leader (ITIL SL) Stream**
- Recognizes ITIL value beyond IT operations, for all digitally enabled services
- Demonstrates understanding of how IT influences and directs business strategy
- Requires 2 modules:
  1. ITIL Strategist: Direct, Plan and Improve (shared with MP stream)
  2. ITIL Leader: Digital and IT Strategy
- **Prerequisite for Leader module**: 3 years managerial experience + ITIL 4 Foundation

**Additional Modules**
- **Practice-based modules**: Shorter, more flexible training; mix and match
- **Extension modules**: Extend ITIL 4 framework for future challenges

**ITIL Master**
- Highest level of achievement
- Requires: Practice Manager + Managing Professional + Strategic Leader designations
- Demonstrates capability to apply ITIL at strategic, tactical, and operational levels

**Key Stream Summary**
| Designation | Required Modules |
|---|---|
| ITIL Managing Professional | Foundation + Create/Delivery/Support + Drive Stakeholder Value + High Velocity IT + Direct/Plan/Improve |
| ITIL Strategic Leader | Foundation + Direct/Plan/Improve + Digital/IT Strategy |
| ITIL Master | Practice Manager + MP + SL |

**Action Items**
- Determine which stream (MP, SL, or both) aligns with career goals
- For SL Leader module, ensure 3 years managerial experience prerequisite is met

**Key Terms/Concepts**
- **ITIL Managing Professional (MP)**: Designation for IT practitioners running successful projects/teams/workflows
- **ITIL Strategic Leader (SL)**: Designation recognizing ITIL for all digitally enabled services and business strategy
- **ITIL Strategist**: Universal module (Direct, Plan, Improve) shared by both MP and SL streams
- **ITIL Master**: Highest achievement, requires all designations

---

# Chapter 5: Conclusion

## Chapter 5 — 1. Preparing to Pass the Exam

**Core Insights**
- Multiple training modalities exist (classroom, virtual, e-learning, video, CBT, mobile); choose based on learning style, cost, and efficacy.
- Hard-copy and e-books support active learning (annotation, highlighting); verify device compatibility and licensing limits.
- LMS-based e-learning offers progress tracking, cohorts, quizzes, and gamification; requires stable internet.
- Video-based learning chunks content into <5-minute digestible units — a modern, effective format.
- CBTs work offline and are searchable, but typically can't be annotated and may expire.

**Detailed Notes**

*Training Modalities*
- **Traditional classroom**: Best for aligning a team collectively; embeds company-specific context; expensive.
- **Virtual instructor-led (VILT)**: Live, synchronous via web conferencing.
- **E-learning (LMS)**: Cloud-hosted; may include audio/video, job aids, badges, cohort grouping, progress dashboards.
- **Video training**: Short chunks (<5 min); analogous to texting vs. email compared to traditional e-learning.
- **CBT (Computer-Based Training)**: Downloadable, offline, searchable; check OS/device compatibility.
- **Mobile learning**: Learn on the go; content must be properly scaled for small screens.

**Action Items**
- Choose a modality that fits your learning style and schedule.
- Verify e-book/CBT compatibility with your devices and OS before purchasing.
- Check licensing terms: offline access, expiry, per-user limits.

**Key Terms/Concepts**
- **LMS (Learning Management System)**: Cloud platform hosting e-learning content with tracking, quizzes, and cohort management.
- **VILT (Virtual Instructor-Led Training)**: Live, synchronous online training with a remote or hybrid instructor.
- **CBT (Computer-Based Training)**: Downloadable, offline-capable training software.

---

## Chapter 5 — 2. What the ITIL Exam Is Like

**Core Insights**
- The ITIL Foundation exam: 40 multiple-choice questions, closed book, 65% (26/40) to pass.
- Non-native language takers get +15 minutes and a dictionary.
- A quality accredited course is "half the battle" — ensure it covers everything needed to pass.
- Official Axelos sample exams (with rationales cross-indexed to syllabus/book) are the only reliable practice source.

**Detailed Notes**

*Exam Format*
- 40 multiple-choice questions, closed book.
- Passing score: 26/40 (65%).
- Non-native speakers: +15 minutes + dictionary allowed.

*Preparation Strategy*
- Take a quality, accredited course with real-world examples and engaging instructors.
- Complete all official Axelos sample/mock exams; review every wrong answer using the provided rationales.
- Avoid free online tests — they often contain outdated, deprecated, or incorrect questions.
- Use the course syllabus to identify weak areas; revisit glossary and course content.

*Logistics*
- Register early to secure your preferred date/time.
- Read exam requirements carefully; prepare your room to spec.
- Run the technical test well before exam day.

**Action Items**
- Complete all official Axelos sample exams and understand every rationale.
- Review weak syllabus topics via glossary and course content.
- Register for the exam early; run the technical test ahead of time.

**Key Terms/Concepts**
- **ITIL Foundation Certificate in IT Service Management**: The entry-level certification earned by passing the foundation exam.
- **Axelos**: The accrediting body that provides official sample exams, syllabi, and publications.

---

## Chapter 5 — 3. ITIL Exam-Taking Strategies

**Core Insights**
- Answer every question; skip uncertain ones and return later — later questions may trigger recall.
- No trick questions or answer-pattern tricks exist; use process of elimination.
- Read questions carefully — watch for "not," and read the actual question first if there's a long preamble.
- "The book answer is the book answer" — use ITIL terminology, not your organization's jargon.

**Detailed Notes**

*General Approach*
- Answer all 40 questions; guess if necessary, or mark and revisit.
- Later questions may jog your memory for earlier skipped ones.
- No trick questions or predictable answer patterns.

*Question-Reading Tactics*
- Watch for the word **"not"** — easy to miss, changes the question entirely.
- For long preambles: read the actual question first, then the context.
- Absolutes ("always," "only," "guarantees") are often wrong — but not always.

*Answer Selection Tactics*
- **Process of elimination**: Remove clearly wrong answers to narrow down.
- **"Best/most correct" questions**: Choose the most inclusive one.
- **Sequence/list questions**: Compare answers starting from the last item.
- **Keyword matching**: An answer sharing a key term with the question may be correct.
- **Outlier detection**: If three answers share a pattern and one doesn't, examine the outlier.

*Critical Rule*
- Use ITIL/book terminology, not your organization's synonyms.

**Action Items**
- Practice with official sample exams using these strategies.
- Train yourself to spot "not" and absolutes in questions.
- Always default to ITIL glossary terms on the exam.

**Key Terms/Concepts**
- **Process of elimination**: Removing clearly wrong answers to increase odds of selecting the correct one.
- **Book answer**: The official ITIL terminology/definition as stated in the accredited coursebook.

---

## Chapter 5 — 4. What to Look for in ITIL Training

**Core Insights**
- Choose accredited, authoritative, cost-effective courses with practitioners as instructors.
- Providers should connect training to organizational context before, during, and after.
- Look for solid exam-prep elements (quizzes, sample exams with rationales) and real-world templates.
- Courseware should be easy to navigate, with progress tracking and searchable indexes.

**Detailed Notes**

*Provider Quality*
- Accredited courses written by practitioners who are also engaging instructors.
- Recent glowing references; above-average exam pass rates; 4–5/5 course evaluation scores.

*Context & Alignment*
- Provider should ask: What goals do you have? What action should participants take? How does this fit broader initiatives?

*Courseware Features*
- Exam prep: quizzes, sample exams with answers and rationales.
- Real-world templates and samples usable immediately at work.
- Easy navigation: progress tracking, jump-around capability, index by glossary term.
- Instructor access for questions (chat, email) during/after the course.

*Logistics & Compatibility*
- Runs on your LMS; provides reporting.
- Flexible options: à la carte packages, mixed modalities.
- Covers all training levels, geographies, languages, and accessibility needs.

**Action Items**
- Verify accreditation and instructor credentials before purchasing.
- Ask providers for recent references, pass rates, and evaluation scores.
- Confirm LMS compatibility, offline access, and reporting capabilities.

**Key Terms/Concepts**
- **Accredited courseware**: Officially approved by Axelos/PeopleCert to cover the full syllabus.
- **Modalities/form factors**: Different delivery formats — e-learning, traditional classroom, live online (VILT), CBT, mobile.

---

## Chapter 5 — 5. Next Steps on Your ITIL Journey

**Core Insights**
- Visit axelos.com for the latest certification scheme, glossaries, syllabi, sample papers, and provider search.
- Official publications are now included digitally with exam purchase.
- Schedule your exam on PeopleCert's website; consider the "take-two" retake option.
- Courses are available in multiple languages; check localization on Axelos.

**Detailed Notes**

*Resources on Axelos.com*
- Up-to-date certification scheme.
- Downloadable glossaries, syllabi, and sample papers for each module.
- Training provider finder by region and modality.
- Language localization info.

*Exam Scheduling (PeopleCert)*
- Purchase and schedule on PeopleCert's website.
- **Take-two option**: Allows a retake if you don't pass the first attempt, at a fraction of full cost — must be ordered upfront.

**Action Items**
- Visit axelos.com to download glossaries, syllabi, and sample papers for your target module.
- Find an accredited training provider in your region/language.
- Purchase and schedule your exam on PeopleCert; add the take-two option if desired.
- Plan your next ITIL certification level.

**Key Terms/Concepts**
- **PeopleCert**: The examination institute that administers ITIL exams globally.
- **Take-two option**: A PeopleCert add-on allowing one exam retake at reduced cost if the first attempt fails; must be purchased upfront.
- **Axelos**: The owner/accreditor of the ITIL framework; provides official publications, syllabi, and training provider accreditation.