ITIL 4 to ITIL v5 Study Guide Part 3 (of 3): Value Chain Activities Study Sheet and Management Practices

Posted on

Here’s the complete study sheet for the eight ITIL v5 value chain activities, plus how management practices enable and support them. New to the value chain? Start with Part 1 (service relationships, governance, and the guiding principles) and Part 2 (purpose, operating model, and the new value chain activities, with a quiz and flash cards).


1. DISCOVER

Purpose: To ensure continual alignment of the product roadmaps and related service offerings with the needs of service consumers and with the organizational strategy.

How it works:

  • Continual activity, not a one-time effort
  • Performed at 3 levels: organizational, portfolio, and product
  • Influenced by PESTLE factors and stakeholder input

Workflow (4 steps):

  1. Assess the product context
  2. Agree direction and objectives
  3. Prioritize actions and allocate resources
  4. Communicate changes in the product roadmap

Who does it:

  • Product teams and/or relationship managers
  • Business analysts
  • Service owners

Key Output:

  • Updated product and service roadmap

Success Factors:

  • Strategic fit of products and service offerings
  • Market relevance of products and service offerings
  • Stakeholder satisfaction with products and service offerings
  • Commercial success of products (if applicable)

Key Terms:

  • PESTLE factors: Political, Economic, Social, Technological, Legal, and Environmental influences
  • Product roadmap: Updated plan reflecting latest insights and strategic direction
  • Continual activity: Ongoing process, not one-time or long-interval based

2. DESIGN

Purpose: To create prototypes and specifications for products and services, detailing their functionality, user experience, and operational framework.

How it works:

  • Dynamic activity involving creating new ideas, adapting to changes, generating solutions
  • Can be proactive (anticipating needs) or reactive (responding to requirements)
  • Includes planning for future service interactions and experience

Workflow (4 steps):

  1. Analyse product and service demand
  2. Plan design activities
  3. Execute design plan
  4. Communicate solution design

Who does it:

  • Product teams
  • In some cases, specialized design teams

Key Outputs:

  • Product and service specifications and prototypes

Success Factors:

  • Quality of specifications and prototypes
  • Design cycle time
  • Adherence to product roadmap and guidelines
  • Stakeholder satisfaction with design activities

Key Terms:

  • Product specification: Detailed document outlining requirements, features, functionalities, and technical criteria
  • Product prototype: Initial version demonstrating form, functionality, and operational capabilities
  • Human-Centred Design (HCD): Problem-solving approach prioritizing user needs, empathy, and iteration

3. ACQUIRE

Purpose: To secure and allocate necessary resources efficiently, ensuring the sustainability and scalability of products and services.

How it works:

  • Can be internal (reallocating existing resources) OR external (sourcing from suppliers)
  • Resources needed for building products and for ongoing operations, delivery, and support
  • May be triggered by new product, operational needs, or supplier review cycles

Workflow (5 steps):

  1. Analyse requirements for resources or services
  2. Assess sourcing options
  3. Agree terms and conditions
  4. Procure resources or services
  5. Communicate resource/service availability to requestor

Who does it:

  • Specialized procurement teams in collaboration with product teams, project teams, and other stakeholders

Key Output:

  • Acquired resources and services

Success Factors:

  • Quality of resources and services
  • Acquire cycle time
  • Adherence to product roadmap and guidelines
  • Stakeholder satisfaction with acquire activity, timelines, and acquired resources

Key Terms:

  • Sourcing: Obtaining resources externally from suppliers or reallocating internally
  • Procurement: The process of acquiring resources and services
  • Resource allocation: Assigning resources to products and services

4. BUILD

Purpose: To develop, integrate, and test digital products, transforming designs into functional solutions.

How it works:

  • Activities: software development, system integration, configuration, process development
  • Includes documentation, validation and testing
  • Can be automated through continuous integration
  • Legacy systems may require manual integration

Workflow (4 steps):

  1. Assess solution design
  2. Plan building/testing and confirm resource availability
  3. Execute building and testing plans
  4. Deliver solutions and supporting documentation

Who does it:

  • Product teams
  • Specialized software development, infrastructure engineering, and testing teams
  • Project teams

Key Output:

  • Built and tested product and service solutions

Success Factors:

  • Quality of product solutions
  • Building cycle time
  • Adherence to product roadmap and guidelines
  • Stakeholder satisfaction with product solutions

Key Terms:

  • Continuous integration: Developers regularly merge code changes; automated builds and tests run to catch integration issues early
  • Testing: Validating that outputs meet quality criteria before transition
  • Solution design: Approved design that triggers build iterations

5. TRANSITION

Purpose: To seamlessly introduce new or updated products into operational environments and to ensure effective onboarding/offboarding of suppliers.

How it works:

  • Safely move built products/resources into live environments
  • May require planned interruptions (especially for legacy products)
  • Modern digital products allow smooth, low-impact updates
  • Includes onboarding/offboarding suppliers and decommissioning resources/products
  • Ensures readiness for operations through monitoring, testing, continuity, and security controls

Workflow (4 steps):

  1. Assess solutions and transition requirements
  2. Plan transition activities and confirm resource availability
  3. Execute transition plans
  4. Communicate transition results to stakeholders

Who does it:

  • Product teams
  • Specialized software development, infrastructure engineering, operations, support, and other relevant teams
  • Project teams

Key Outputs:

  • Products, services, and resources deployed to target live environment and ready for operation
  • Onboarded/offboarded suppliers

Success Factors:

  • Transition cycle (timeliness and duration)
  • Negative impact of transition on service availability and performance
  • Number and impact of transition errors
  • Adherence to product roadmap and guidelines
  • Stakeholder satisfaction with transition process and results

Key Terms:

  • Release: A version of a product/service/configuration item made available for use
  • Change: Any addition, modification, or removal that could impact services
  • Continuous delivery: Software always in release-ready state; deployments possible anytime but controlled
  • Continuous deployment: Changes automatically flow through pipeline into live environment

6. OPERATE

Purpose: To maintain and monitor digital products and supporting systems, ensuring optimal performance and reliability.

How it works:

  • Runs platforms/systems to ensure performance and availability
  • Performs routine tests, backups, monitoring, event processing
  • Ensures existing services are delivered as designed and in line with commitments to customers
  • Ensures compliance with policies (continuity, security, certificates, licenses)
  • Activities mostly invisible to customers unless issues arise
  • Proper operations prevent disruptions and ensure reliability

Workflow (3 steps):

  1. Assess transitioned solutions and operational requirements
  2. Plan operations activities and confirm resource availability
  3. Execute operational plans and report status to stakeholders

Who does it:

  • Product teams
  • IT operations teams
  • SRE (Site Reliability Engineering) teams

Key Outputs:

  • Operating products and services
  • Product performance records and reports

Success Factors:

  • Coverage and effectiveness of monitoring and analysis
  • Live products’ reliability, performance, and information security
  • Number and impact of incidents and performance deviations
  • Adherence to product roadmap and guidelines
  • Stakeholder satisfaction with product and service operation

Key Terms:

  • Reliability: Ability of a product/service to perform its intended function consistently over time
  • SRE (Site Reliability Engineering): Discipline applying software engineering to infrastructure/operations to create scalable, highly reliable systems
  • Observability: Understanding internal system state through external outputs (metrics, logs, traces)
  • Event: Signal about change of state that may require monitoring or action
  • Incident: Unplanned interruption or degraded service quality

7. DELIVER

Purpose: To provide services to users, manage user onboarding/offboarding, maintain service quality standards, and gather consumers’ feedback.

Difference from Operate:

  • Operate: Ensures products remain in working state
  • Deliver: Focuses on providing agreed levels of service defined in SLAs

How it works:

  • Provides access to product resources
  • Transfers goods as part of the service
  • Performs service actions with or for users
  • Directly linked to SLAs and quality criteria
  • Exact scope depends on product architecture, design, and service agreements

Workflow (3 steps):

  1. Assess service delivery commitments and available solutions
  2. Identify and confirm delivery plan and resource availability
  3. Execute delivery plans and report delivery status to stakeholders

Who does it:

  • Product teams
  • Service delivery teams
  • User support teams
  • Service desk teams

Key Outputs:

  • Delivered services
  • Service performance and user feedback records and reports

Success Factors:

  • Customer and user satisfaction with service quality
  • Service performance against agreed SLA targets
  • Adherence to product and service strategy and guidelines
  • Stakeholder satisfaction with service delivery

Key Terms:

  • SLA (Service Level Agreement): Documented agreement defining services and required service levels
  • Service request: User-initiated request for agreed service actions under SLAs

8. SUPPORT

Purpose: To identify and resolve incidents, fulfill disaster recovery procedures, and capture consumer feedback.

How it works:

  • Resolves incidents and disasters
  • Includes recovery and restoration of services
  • Investigates incidents and identifies errors in products
  • Involves multiple teams across the organization
  • Can be automated and proactive, but also reactive when needed
  • Strong collaboration between teams is essential

Workflow (3 steps):

  1. Identify and assess incidents and disasters
  2. Respond to incidents/disasters and restore normal operations and delivery
  3. Review and report support actions

Who does it:

  • Product teams
  • SRE teams
  • IT operations teams
  • User support teams
  • Service desk teams
  • Other specialized teams as needed

Key Output:

  • Restored normal product operation and service delivery

Success Factors:

  • Customer and user satisfaction with service support
  • Speed of normal service restoration
  • Negative impact of incidents and disasters on organization and customers
  • Support performance against agreed SLA targets and product performance objectives
  • Adherence to product and service strategy and guidelines

Key Terms:

  • Incident: Unplanned interruption or service degradation
  • Disaster: Large-scale incident threatening entire business
  • Error: Issue that may trigger incidents
  • Problem: Root cause of incidents
  • Known Error: Documented but unresolved problem

Quick Reference: The Value Chain at a Glance

ActivityMain FocusKey OutputWho Does It
DiscoverAlign roadmaps with strategy & needsUpdated roadmapProduct teams, BAs, Service owners
DesignCreate specifications & prototypesSpecs & prototypesProduct teams, Design teams
AcquireSecure resources efficientlyAcquired resourcesProcurement + Product teams
BuildDevelop & test solutionsBuilt & tested solutionsProduct/Dev/Test teams
TransitionMove to live environmentDeployed productsProduct + Operations teams
OperateMaintain & monitor systemsOperating productsIT Ops, SRE, Product teams
DeliverProvide services to usersDelivered servicesService delivery, Service desk
SupportResolve incidents & restore serviceRestored operationsSupport, Service desk, SRE

Play ITIL IDOL

Ready to test yourself on the value chain activities and practices? Give ITIL IDOL Game 4 a spin:

🎤 ITIL IDOL 🌟

Game 4 — The Full Tour!

🔗 Chain Reaction!

This round covers the Value Chain, all 8 Lifecycle Activities, and ITIL Management Practices! 15 questions from discover to support. Show us you know the full lifecycle! 🏆


Management Practices Enable and Support the Value Chain 📊Know These Come Test Day

Value chain activities are not stand-alone. They are consistently enabled and strengthened by management practices, which provide the methods, resources, and guidance to perform them effectively.

  • Enabling practices (E): Activities of these practices are directly involved in the value chain activity
  • Supporting practices (S): Not directly involved in the value chain activity, but they support it with information and methods

For example, the design activity is enabled by 17 practices (including service design, architecture management, and measurement and reporting) and supported by seven practices (including IT asset management and knowledge management).

There’s a big table mapping the practices to the value chain activities (though it doesn’t seem we need to memorize it, phweew!). The mapping should always be adapted to the organization and the product. For example, organizational change management may be very important for designing digital products and services when the design requires changes to the service provider’s or service consumer’s organization, and it isn’t included in many other cases of product and service design.

When organizations include a value chain activity in their operating model, they need to develop the relevant management capabilities.

34 Management Practices in Two Groups 📊Know These Come Test Day

  • 12 general management practices
  • 22 product and service management practices

The ITIL Official Practice Guides share a consistent structure and deliver practical, effective guidance, including metrics and capability criteria for evaluating each practice.


Recap

✅ The purpose of the value chain is to transform demand and opportunities into value through interconnected lifecycle activities

✅ The ITIL Product and Service Lifecycle covers discover, design, acquire, build, transition, operate, deliver, and support

✅ These activities are flexible and adaptive, not always sequential, and must align with organizational strategy and consumer needs

✅ Success is measured by metrics such as stakeholder satisfaction, reliability, and alignment with roadmaps

✅ Management practices strengthen and enable each value chain activity by providing the methods and resources that make it work

✅ ITIL defines 34 management practices: 12 general management practices and 22 product and service management practices

🎮 Want more practice? Play ITIL IDOL (6 rounds, 90 questions, with an explanation after every answer) and grab the free ITIL v5 Foundation Fast-Track Study Guide over at OPM Coach Resources.

Want to drill the eight activities? The quiz and flash cards are in Part 2.

Good luck with your studies! 🎯