Skip to main content

ITIL's Service Design 5

What does the Service Design stage actually design? Many readers of ITIL V3 assume that Service Design is primarily responsible for IT services. In fact, this stage is responsible for five different aspects:
  • Service solutions
  • Service management systems and tools
  • Technology architectures and management systems
  • IT and service management processes
  • Measurement methods and metrics
ITIL’s holistic approach to design ensures consistency and integration across the full portfolio of IT services. Consideration of each design begins with an assessment of the “as-is” situation, with a view to identifying relationships, dependencies, compatibility, and, especially, opportunities to leverage existing capabilities and resources (service assets). Both opportunities and gaps are identified. This may validate the design of the new service, or may indicate the need to modify or adapt the design of the new service or other existing services.

Service Design is charged with designing services that deliver business value while being manageable, supportable, cost-effective, and flexible enough to scale and incorporate enhancements throughout the operational lifetime of that service.
Strongly emphasized in V3 is the idea that everyone in the IT organization is responsible for the successful provision of value to business customers in the form of IT services.

This is fundamental to ITIL’s treatment of the five aspects of design. Service Design must consider the requirements of all other stages of the service lifecycle. Likewise, processes and participants in other stages of the lifecycle have the responsibility to provide feedback on how well these goals are achieved in testing and in the live environment, and how design of IT services might be improved to optimize total cost of utilization of services throughout their operational lifetime.

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service". I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize: SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle. ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th