PeopleCert / AXELOSITILFND V597 concepts

ITILFND V5 Cheat Sheet

Quick reference for the ITIL Foundation (Version 5) exam.

Quick Navigation

Core ITIL Definitions Stakeholder Roles ITIL Service Value System (SVS)Seven Guiding Principles Service Value Chain Activities Continual Improvement Model Four Dimensions of Service Management Product and Service Lifecycle (8 Stages)Value Streams and Governance ITIL Concepts: Incidents, Problems, Changes ITIL and AI: The 6C Model ITIL and Other Frameworks Exam Traps and Must-Know Distinctions

Core ITIL Definitions

Service: A means of enabling value co-creation by facilitating outcomes customers want to achieve, without managing specific costs and risks.
Product: A configuration of an organization's resources designed to offer value for a consumer. Products are the tangible offering; services are delivered through products.
Value: The perceived benefits, usefulness, and importance of something. Value is co-created through interaction between provider and consumer — not delivered unilaterally.
Utility (Fit for Purpose): The functionality offered by a product or service to meet a particular need. Utility = WHAT the service does. Without utility, the service provides no purpose.
Warranty (Fit for Use): Assurance that a product or service meets agreed requirements — availability, capacity, security, continuity. Warranty = HOW WELL the service performs.
Utility AND Warranty Required: Both are necessary for a service to create value. High utility + poor warranty = unreliable service. High warranty + no utility = pointless service.
Output: A tangible or intangible deliverable produced by an activity. Examples: a deployed application, a generated report, a configured server.
Outcome: The result that a stakeholder achieves through using a service or output — the actual change in state or condition that matters to them.
Risk: A possible event that could cause harm or loss, or make it harder to achieve objectives. Services help customers reduce the risks they manage themselves.
Value Co-Creation: Value emerges from the active interaction between service provider and consumer. Providers do not deliver value TO consumers — both parties create it together.

Stakeholder Roles

Customer: Defines service requirements and is accountable for the outcomes the service supports. Often negotiates service agreements and authorizes requirements.
User: Uses the service in day-to-day work to get tasks done. Does not define requirements or approve funding. Example: employees using an IT payroll system.
Sponsor: Authorizes the budget and approves the service. May or may not be the same as the customer. Example: CFO approving IT investment.
Role Overlap: One person can hold multiple stakeholder roles simultaneously. A small business owner can be customer, user, and sponsor all at once.
Customer vs User Trap: In enterprise IT: the department head (customer) defines requirements and owns outcomes; employees (users) use the service. Distinct roles, distinct responsibilities.

ITIL Service Value System (SVS)

SVS Definition: The model showing how all components and activities work together to enable value creation. Takes demand and opportunity as inputs; produces value as output.
SVS Component 1: Guiding Principles: Universal recommendations that guide all decisions and actions in any circumstance, at any level. Applied as relevant — not mandatory rules.
SVS Component 2: Governance: How the organization is directed and controlled. Evaluates, directs, and monitors activities. Provides accountability and strategic alignment.
SVS Component 3: Service Value Chain: The six activities (Plan, Improve, Engage, Design and Transition, Obtain/Build, Deliver and Support) that convert demand into value.
SVS Component 4: Practices: Sets of organizational resources (people, processes, technology, information) designed to achieve objectives. Examples: incident management, change enablement.
SVS Component 5: Continual Improvement: An ongoing effort at all levels to improve services, practices, teams, and the organization. Supported by the continual improvement model.
SVS = 5 Components: Exactly five: guiding principles, governance, service value chain, practices, continual improvement. Practices ≠ processes. Service value chain ≠ the whole SVS.

Seven Guiding Principles

1. Focus on Value: Everything the organization does should link, directly or indirectly, to value for itself, its customers, and other stakeholders.
2. Start Where You Are: Do not start from scratch unless necessary. Assess what currently exists and preserve/reuse what is working. Avoid waste.
3. Progress Iteratively with Feedback: Work in manageable iterations and use feedback at each step to improve. Aligns with Agile values. Avoid big-bang implementations.
4. Collaborate and Promote Visibility: Work together across boundaries. Share information openly. Lack of visibility leads to poor decisions and unnecessary duplication.
5. Think and Work Holistically: No service, practice, process, or department works in isolation. Consider the whole system and how parts interact.
6. Keep It Simple and Practical: Use the minimum number of steps to accomplish an objective. Eliminate anything that does not contribute to value creation.
7. Optimize and Automate: Optimize first (remove waste, improve flow), then automate. Automating a broken process makes it worse faster.
Principles Are Recommendations: Guiding principles apply in any circumstances but are not mandatory rules. Apply them thoughtfully based on context — not mechanically.

Service Value Chain Activities

Plan: Ensure a shared understanding of the vision, current status, and improvement direction. Applies to all products, services, and practices in the SVS.
Improve: Ensure continual improvement of products, services, and practices across all value chain activities. Every activity connects to Improve.
Engage: Provide understanding of stakeholder needs, transparency, and continual engagement. Interfaces with customers, users, and partners.
Design and Transition: Ensure that products and services continually meet stakeholder expectations for quality, costs, and time to market.
Obtain/Build: Ensure service components are available when needed and meet agreed specifications. Covers sourcing, procurement, and component creation.
Deliver and Support: Ensure services are delivered and supported according to agreed specifications and stakeholders' expectations.
Not a Linear Process: Service value chain activities can be combined in ANY sequence to form value streams. They are not a conveyor belt — they are flexible building blocks.

Continual Improvement Model

Step 1: What is the Vision?: Understand the high-level direction and objectives. Align improvement goals with organizational strategy.
Step 2: Where Are We Now?: Assess the current state using objective data, measurements, and baselines. Never skip this step.
Step 3: Where Do We Want to Be?: Define measurable targets and desired future state. Set specific, achievable improvement goals.
Step 4: How Do We Get There?: Plan the improvement initiative: actions, resources, timeline, and accountabilities.
Step 5: Take Action: Execute the improvement plan. Progress iteratively with feedback — do not wait for perfection before acting.
Step 6: Did We Get There?: Measure results and compare against the targets set in Step 3. Evaluate whether the improvement achieved its goals.
Step 7: How Do We Keep the Momentum?: Embed improvements, share successes, and feed back into the next improvement cycle. The model is circular, not linear.

Four Dimensions of Service Management

Organizations and People: Team structures, culture, roles, competencies, responsibilities, and staffing. Covers how people are organized and empowered to deliver services.
Information and Technology: Data, knowledge, IT infrastructure, AI tools, communication systems, and emerging technologies needed to deliver and manage services.
Partners and Suppliers: Relationships with external organizations contributing to service delivery — cloud providers, software vendors, outsourcing partners, and service integrators.
Value Streams and Processes: Specific activities, workflows, controls, and procedures that transform inputs into valuable outputs and outcomes.
All Four Must Be Balanced: Neglecting any single dimension creates service failures. A great technology solution with poor staffing planning (O&P) will still underperform.
PESTLE Factors: External factors that constrain all four dimensions: Political, Economic, Social, Technological, Legal, Environmental. Organizations cannot control PESTLE — they must respond to it.
PESTLE is Not a Dimension: PESTLE represents the external environment — it sits outside the four dimensions and influences all of them. It is not a fifth dimension.

Product and Service Lifecycle (8 Stages)

1. Discover: Identify and prioritize needs and opportunities, aligning with organizational strategy. Understand what customers need before designing anything.
2. Design: Create the service solution, architecture, and specifications to meet identified needs. Human-centered design principles apply here.
3. Acquire: Obtain resources, third-party software, cloud infrastructure, or other components needed before development begins.
4. Build: Develop, configure, test, and validate the service or product. Covers coding, configuration, and all development activities.
5. Transition: Manage the move from development to live environments — data migration, user training, go-live readiness, and cutover coordination.
6. Operate: Keep services running day-to-day. Includes monitoring performance and analyzing feedback for a live service.
7. Deliver: The stage where value is realized as users actively consume the service. Ongoing provision of the service to users.
8. Support: Restore normal operations and resolve issues when things go wrong. Handles incidents, service requests, and problem escalations.
Lifecycle Stage Pairs: Often grouped as pairs: Discover+Design (understand and plan), Acquire+Build (obtain and develop), Transition+Operate (go live and run), Deliver+Support (provide and fix).
Lifecycle vs ITIL v3: ITIL 5's 8-stage lifecycle (Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support) replaces ITIL v3's lifecycle (Strategy, Design, Transition, Operation, Continual Service Improvement).
Wrong Terms Trap: Develop, Deploy, Optimize, and Retire are NOT ITIL 5 lifecycle stage names. The correct terms are Acquire, Build, Transition, and Operate.

Value Streams and Governance

Value Stream: A series of steps an organization undertakes to create and deliver a product or service to a consumer. Built from combinations of service value chain activities.
Value Stream vs Service Value Chain: Service value chain = the six building-block activities. Value stream = a specific sequence of those activities for a particular service scenario.
Flow-Based Thinking: Optimizing the flow of work through a value stream to maximize efficiency and minimize waste. Reduce delays, handoffs, and rework.
Value Stream Mapping: A visual technique for documenting all steps, information flows, and handoffs in a value stream. Reveals both value-adding and non-value-adding activities.
Governance: Evaluate, Direct, Monitor: Governance bodies evaluate decisions, direct the organization toward objectives, and monitor performance and compliance.
Governance vs Management: Governance = oversight, accountability, strategic direction (top level). Management = day-to-day operations and execution. Both are necessary; neither replaces the other.
Value Stream Mapping vs Management: Mapping = a one-time diagnostic snapshot documenting all steps and handoffs in a value stream. Management = the ongoing daily practice of continuous workflow optimization.
Flow Efficiency: Value-adding time divided by total lead time. Low flow efficiency (e.g., 4 hours work in 5 days) indicates waste in queues and handoffs — the primary target for value stream optimization.

ITIL Concepts: Incidents, Problems, Changes

Incident: An unplanned interruption or reduction in quality of a service. Goal of incident management: restore normal service operation as quickly as possible.
Problem: A cause, or potential cause, of one or more incidents. Goal of problem management: identify and eliminate root causes to prevent future incidents.
Workaround: A solution that resolves an incident temporarily without fixing the underlying problem. Incidents can be closed with a workaround; problems remain open.
Change: Adding, modifying, or removing anything that could affect IT services. Change enablement manages risks associated with changes.
Incident vs Problem Trap: Resolving an incident does NOT fix the problem. Incident management restores service; problem management finds and eliminates root causes. Separate activities.
SLA vs XLA: SLA (Service Level Agreement) = technical performance metrics (availability %, response time). XLA (Experience Level Agreement) = user satisfaction and perceived value. SLAs can be met while users remain unhappy.

ITIL and AI: The 6C Model

6C AI Capability Model: ITIL 5's framework classifying AI into six functions: Creation, Curation, Clarification, Cognition, Communication, and Coordination.
Creation: AI generates new content or code — e.g., auto-generating incident reports, documentation, or configuration scripts.
Curation: AI improves data quality — e.g., cleaning CMDB records, deduplicating assets, enriching service catalog data.
Clarification: AI helps users understand complex information — e.g., summarizing long incident histories or explaining technical errors in plain language.
Cognition: AI detects patterns and provides proactive insights — e.g., anomaly detection in service performance data before users are impacted.
Communication: AI provides natural language interfaces — e.g., service desk chatbots and virtual assistants answering user questions autonomously.
Coordination: AI orchestrates actions autonomously across systems — e.g., automatically routing incidents, executing remediation scripts, and closing tickets.
AI Governance in ITIL: Responsible AI adoption requires oversight, transparency, accountability for AI outputs, and ethical use policies. Human oversight remains essential.
AI Does Not Replace ITIL: AI enhances ITIL practices — it accelerates monitoring, automates repetitive tasks, and supports decisions. It does not replace the practices themselves.

ITIL and Other Frameworks

ITIL + DevOps: Complementary, not competing. DevOps brings speed, collaboration, and automation. ITIL provides governance and service management structure. ITIL 5 was designed with DevOps in mind.
ITIL + Agile: 'Progress iteratively with feedback' aligns directly with Agile values. ITIL 5 can wrap around Agile delivery methods like Scrum and Kanban.
ITIL + PRINCE2: PRINCE2 manages the project that creates or changes a service. ITIL manages the service once it is live. They cover different stages — not alternatives.
Framework Selection Principle: No single framework covers everything. Select complementary frameworks based on organizational context, goals, and existing capabilities.

Exam Traps and Must-Know Distinctions

Output ≠ Outcome: Deploying software (output) enables improved employee productivity (outcome). Outputs are deliverables you can count; outcomes are the results that matter.
Utility ≠ Warranty: A service can have perfect uptime (warranty) but do nothing useful (no utility). Or it can be very useful (utility) but constantly unavailable (no warranty). Both required.
SVS ≠ Service Value Chain: The SVS is the full model (5 components). The service value chain is ONE of those 5 components (6 activities). Do not equate the two.
Guiding Principles ≠ Mandatory Rules: Principles are recommendations — universal guidance applied thoughtfully. They are not compliance requirements or process steps.
PESTLE ≠ Fourth Dimension: PESTLE factors are external constraints that influence all four dimensions from outside. There are four dimensions, not five.
Incident ≠ Problem: Incidents are service disruptions (restore fast). Problems are root causes (eliminate permanently). An incident can be closed while its problem remains open.
ITIL v5 Lifecycle ≠ ITIL v3 Lifecycle: ITIL 5: Discover, Design, Acquire, Build, Transition, Operate, Deliver, Support (8 stages). ITIL v3: Strategy, Design, Transition, Operation, Continual Service Improvement (5 stages).
Governance ≠ Management: Governance = evaluate, direct, monitor (top-level oversight). Management = execute day-to-day activities. Both are SVS-relevant but serve different purposes.

Ready to test yourself?

Start a timed ITILFND V5 mock exam or review practice questions by domain.