The service value chain is useful for describing the kind of activities that a service provider executes at a high level of abstraction. The visual rearrangement of the interrelated value chain activities helps explain and discuss the different kinds of situations.
The concept of ‘continuous’ is quite popular in high-velocity IT environments. The DevOps community usually illustrates the concept of ‘continuous’ using the infinity symbol, as shown in the following figure.
The symbol depicts a continuous loop of connected activities of application development and IT operations. The Dev and Ops activities, such as coding, testing, deployment, and production, are enabled by infrastructure and platforms. You can use the service value chain activities to unite the DevOps perspective with an ITIL perspective.
ITIL terminology, DevOps focuses on developing, deploying, and running concrete service components than intangible services.
In ITIL terminology, DevOps focuses on developing, deploying, and running concrete service components than intangible services. The dominant service components in DevOps are applications, data, and platforms that together form a product for the consumer. The focus of the service value chain is on products and services than individual service components. It describes the needs for the interaction between the service provider’s products and other resources, including the service consumer’s resources.
The following figure shows some service value chain activities that have been split into two subactivities to map these to various parts of the DevOps model.
The example is of a high-velocity IT application of the service value chain that will enable you:
- Discuss work from different but interrelated perspectives.
- Bridge the gap between professional disciplines.
About the author
As an IT Service Management trainer, consultant and line manager with over 25 years of experience in IT, Marcel has performed strategic and tactical assignments in a wide variety of areas. For the ITIL 4 update, Marcel has been part of the ITIL 4 Lead Architect Team and Review Team at AXELOS. Through his association with AXELOS, Marcel comprehends the background, the architecture, and the underlying reasons of the ITIL 4 update.
Sorry, we couldn't find any posts. Please try a different search.