SkarpChapter 12 of 13
End‑to‑End Scenarios: Connecting Practices into Value Streams
Rather than treating each practice as a silo, this chapter walks through realistic end‑to‑end scenarios and shows how ITIL 5 expects practices to collaborate from demand to value.
From Siloed Practices to End-to-End Value Streams
Why Value Streams?
ITIL 5 focuses on value streams: end-to-end paths from demand to value. The key question is not "Which practice?" but "How do practices collaborate across the whole journey?"
Typical End-to-End Flows
Common streams include:
- Incident to resolution
- Request to fulfillment
- Change to deployment
Each stream uses multiple practices, roles, and tools working together.
Link to Previous Modules
Design, architecture, configuration, AI, and automation all appear inside these value streams. You will now see how they connect into real workflows.
Goal for This Module
You should be able to trace who does what, when, and why in realistic scenarios, and recognize how several practices appear together in exam questions.
Guiding Principles and Four Dimensions Across a Stream
Guiding Principles Travel
ITIL guiding principles like focus on value and collaborate and promote visibility apply across every step in a value stream, not just within one practice.
Four Dimensions as a Checklist
The four dimensions are:
- Organizations and people
- Information and technology
- Partners and suppliers
- Value streams and processes
Use them to spot gaps in any scenario.
Holistic Thinking in Exams
Exam scenarios often show multiple teams, tools, and suppliers. This usually tests your ability to think holistically, not just recall one practice definition.
Scenario 1: Incident to Resolution (End-to-End Walkthrough)
Incident Scenario Overview
A payment service is slow and fails at peak times. Customers complain via the app and social media. We trace the incident to resolution stream and see which practices collaborate.
Detect and Log
Monitoring tools and customer reports trigger the incident. Practices: incident management, monitoring and event management, service desk.
Classify and Prioritize
Service desk categorizes the incident and sets priority using configuration data. Practices: incident management, service configuration management.
Workaround and Knowledge
Support applies a workaround using known errors and knowledge articles. Practices: incident management, knowledge management, problem management.
Escalation and AI Support
The incident escalates to technical teams. AI tools analyze telemetry to suggest causes. Practices: incident management, problem management, analytics capabilities.
Root Cause and Change
A faulty configuration change is found. A new change is raised to fix capacity. Practices: problem management, change enablement, service configuration management, release management.
Deploy, Validate, Improve
Automated deployment delivers the fix. Monitoring validates recovery. Knowledge and improvement actions are updated. Practices: change enablement, deployment management, continual improvement.
Map the Practices: Incident Stream
Use this thought exercise to solidify the incident scenario.
Task: For each step below, write down (mentally or on paper) two key practices that are most central. Then check the suggested answers.
- Step: "Service desk logs multiple user complaints and links them to existing monitoring alerts."
- Your guess: ?
- Suggested answer: Incident management, service desk, plus monitoring and event management.
- Step: "A temporary traffic reroute is applied while engineers investigate."
- Your guess: ?
- Suggested answer: Incident management (restoring service), problem management (thinking about root cause), possibly infrastructure and platform management.
- Step: "A change request is created to adjust database auto-scaling settings."
- Your guess: ?
- Suggested answer: Change enablement, service configuration management, and software development and management if code or scripts are changed.
- Step: "After deployment, the team reviews monitoring dashboards and closes the incident."
- Your guess: ?
- Suggested answer: Monitoring and event management, incident management, and deployment management.
Reflect:
- Did any step feel like "only one" practice? In reality, most steps involve at least two collaborating practices.
- In exams, if an option suggests that only a single practice is involved in a complex step, treat it with caution.
Scenario 2: Request to Fulfillment (Self-Service and Automation)
Request Scenario Overview
An employee requests access to a new analytics tool via a self-service portal. We follow the request to fulfillment stream and highlight design and automation.
Catalog and Design
The employee selects a catalog item designed with needed data built in. Practices: service catalog and portfolio management, service request management, service design.
Policy and Risk
Automated checks validate access rules and data protection. Practices: information security management, risk management, service request management.
Approvals
Manager or data owner approvals are triggered when required; low-risk requests can be auto-approved. Practices: service request management, access management, governance.
Automated Fulfillment
Orchestration tools create accounts, assign licenses, and update groups and configuration data. Practices: access management, infrastructure and platform management, service configuration management.
Communicate and Improve
The user receives instructions; feedback is captured to refine the catalog. Practices: service request management, knowledge management, continual improvement.
Quick Check: Request vs Incident
Test your ability to distinguish a request value stream from an incident value stream.
A scenario describes an employee using a portal to get access to a standard reporting tool. The request is auto-approved and fulfilled by scripts that create the account. Which combination of practices is MOST central to this value stream?
- Incident management and problem management
- Service request management, access management, and automation/orchestration
- Change enablement and deployment management
- Release management and monitoring and event management
Show Answer
Answer: B) Service request management, access management, and automation/orchestration
This is a **standard access request** handled through the catalog and automation. The central practices are **service request management** (handling the request), **access management** (granting rights), and **automation/orchestration capabilities** (scripts doing the work). Incidents and problem management focus on restoring service, not granting standard access.
Scenario 3: Change to Deployment (From Idea to Live Service)
Change Scenario Overview
A new "one-click refund" feature is proposed for the mobile app. We follow the change to deployment value stream from idea to live service.
From Demand to Design
Customer feedback creates demand; a proposal enters the portfolio. Practices: business relationship management, portfolio management, product management.
High-Level Design
Architects design APIs, data flows, and observability with resilience and security in mind. Practices: service design, architecture management, information security management.
Configuration and Build
Teams define configuration models and infrastructure, then build the feature. Practices: service configuration management, infrastructure and platform management, software development and management.
Automated Build and Test
CI/CD pipelines run automated tests and package releases. Practices: software development and management, release management, test management, automation.
Change and Deployment
Change enablement assesses risk; deployment management rolls out the feature gradually with monitoring. Practices: change enablement, deployment management, monitoring and event management.
Review and Improve
Metrics on usage and risk drive improvements. Practices: measurement and reporting, continual improvement, product management.
Integrated Scenario Question (Exam-Style)
Practice recognizing multiple practices inside one story.
A team designs a new feature, defines monitoring dashboards before go-live, uses automated tests in a pipeline, and then gradually releases the feature to 10% of users while watching error rates. Which set of practices is MOST clearly represented across this value stream?
- Incident management, service desk, and access management
- Service design, monitoring and event management, software development and management, and deployment management
- Problem management, configuration management, and supplier management
- Service request management, change enablement, and portfolio management
Show Answer
Answer: B) Service design, monitoring and event management, software development and management, and deployment management
The scenario emphasizes **designing the feature and monitoring**, **automated build and tests**, and **gradual deployment**. These map to **service design**, **monitoring and event management**, **software development and management**, and **deployment management**. Incident, problem, and request handling are not central here.
Review: Key Concepts and Terms
Use these quick flashcards to reinforce the main ideas from this module.
- Value stream
- An end-to-end series of activities an organization undertakes to respond to demand and deliver value to stakeholders. In ITIL 5, practices collaborate within value streams rather than operating as isolated processes.
- Incident to resolution stream
- A value stream focused on restoring normal service as quickly as possible after an unplanned interruption or reduction in quality, typically involving incident management, problem management, change enablement, and monitoring.
- Request to fulfillment stream
- A value stream that handles predefined, user-initiated requests (such as access or information), often using service request management, access management, catalog management, and automation.
- Change to deployment stream
- A value stream that takes a change idea from proposal through design, build, risk assessment, and deployment into live use, involving service design, architecture, change enablement, release and deployment management, and configuration management.
- Hand-off between practices
- The transfer of work, information, or responsibility from one practice or role to another within a value stream, such as from incident management to problem management, or from change enablement to deployment management.
- Guiding principles in value streams
- High-level recommendations (such as focus on value, collaborate and promote visibility, and optimize and automate) that should shape decisions and behaviors across every step of a value stream.
- Four dimensions of service management
- Organizations and people; information and technology; partners and suppliers; value streams and processes. Used together to ensure holistic design and operation of value streams.
- Exam pattern: integrated scenario
- A question style where multiple practices appear in one story. You must identify which practices are at play in each step and how they collaborate, rather than treating the scenario as belonging to only one practice.
Key Terms
- Value stream
- An end-to-end sequence of activities that an organization performs to convert demand into value for stakeholders.
- Change enablement
- The practice of maximizing the number of successful service and product changes by ensuring that risks are properly assessed and changes are authorized and scheduled.
- Guiding principles
- Recommendations in ITIL that guide an organization in all circumstances, regardless of changes in its goals, strategies, or management structure.
- Release management
- The practice of making new and changed services and features available for use.
- Incident management
- The practice of minimizing the negative impact of incidents by restoring normal service operation as quickly as possible.
- Deployment management
- The practice of moving new or changed hardware, software, documentation, processes, or any other component to live environments.
- Service request management
- The practice of handling predefined, user-initiated requests in an effective and user-friendly manner.
- Service value system (SVS)
- The ITIL model that describes how all components and activities of an organization work together as a system to enable value creation.
- Service configuration management
- The practice of ensuring that accurate and reliable information about the configuration of services and the CIs that support them is available when and where needed.
- Four dimensions of service management
- A model in ITIL that ensures a balanced, holistic approach by considering organizations and people, information and technology, partners and suppliers, and value streams and processes.