Skip to main content

Why ITSM and DevOps? Ask NYSE, United Airlines, Microsoft…!

The NYSE reportedly told floor traders the exchange had to suspend trading due to an error with a systems upgrade that was rolled out before the market opened.  Early in the morning the NYSE sent out a message alerting traders that there was a reported issue with a number of the exchange’s gateways.  It appears that performance degraded from there and a few short hours later trading halted! ( http://fortune.com/2015/07/08/nyse-halt/  for full story)

How does this happen?  Other issues reported that same week included United Airlines who closed all flight bookings due to what was labeled a “Router” issue.   Microsoft GoToTraining impacted several business owners and customers due to a suspected “Citrix” upgrade.   If ever a case for why do we need Service Management processes that are aligned with business outcomes can be made, one only needs to listen to the news.  Just yesterday a computer system outage disrupted Spirit Airlines flights at Chicago O'Hare, forcing the carrier to cancel flights.  The glitch occurred when an electrical spike led to a connectivity issue for Spirit's O'Hare operations.  They just keep on coming!  In order to manage demand and to respond to extremely dynamic business requirements Capacity Management, Availability Management, Service Continuity and Security requirements can no longer be viewed as afterthought but must be viewed as full on business critical requirements early in the service lifecycle. 

According to ITIL Best Practice “Utility” is what the product or the service does.  “Warranty” refers to the ability of a service to be available when needed, to provide the required capacity, and to provide the required reliability in terms of continuity and security.  Warranty can be summarized as ‘how the service is delivered’, and can be used to determine whether a service is ‘fit for use’.  For example, any aspect of the service that increases the availability or speed of the service would be considered warranty.  Warranty can therefore represent any attribute of a service that increases the potential of the business to be able to perform a task.  Warranty refers to any means by which utility is made available to the users.

It is time for the industry of service providers to get it right.  Agile, DevOps, and Lean are required, but without appropriate process activity early in the strategy and design lifecycle we are likely to continue to miss the mark.

Resources:
For more information on how to achieve “Warranty” of service for service providers and other Service Design processes I recommend the ITIL Service Design Core Publication:  http://www.itsmacademy.com/itil-sd-book/

If you are interested in training and certification to ensure “Utility and Warranty” throughout the value stream you will find these very helpful:


Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe

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