Skip to main content

Digital Transformation – Pro ITIL?

Some IT executives and practitioners still believe that Agile is the way to success for transformation.

Some IT executives and practitioners will argue that ITIL is the way to go.

Some will say LEAN should be the approach to ensure success.

Oh, you say, “they are all wrong?”  Perhaps you think DevOps and Continuous Delivery is the silver bullet?

Well guess what?   You are all right.  The truth of the matter is that no one best practice or method stands alone.  There are far too many examples of how this trinity of LEAN, Agile, and ITSM enable DevOps for digital transformation. 

ITIL’s Continual Service Improvement (CSI) Approach - Iterative ongoing continual service improvement is at the core of every Service Management Principle. The concept of ‘adopt and adapt’ involves adapting best practices to an organization's circumstances, needs, goals and objectives. Using Agile and Scrum will help increase your velocity. LEAN will help to remove waste to help with the ongoing ITIL Continuous Service Improvement approach.  And let’s not forget DevOps for an integrated approach all the way through.

ITIL’s Metrics and Measurement Best Practice - Key to good metrics and measurement is ensuring that what we measure is linked to the needs and goals of the organization.  The use of the ITIL vision to measurement trail is part of both metrics and measurement and the CSI approach. To move from “Where Are We Now?” to “Where do we want to be?” perhaps it would be good to use LEAN to get rid of all the irrelevant metrics and reports and then use Agile/Scrum to gradually improve and evolve for new never before thought of metric systems.   All along ITIL Best Practice and the ITIL Practitioners “Nine Guiding Principles” will help to keep you on target.

ITIL Practitioner Nine Guiding Principles

·      Focus on Value
·      Work holistically
·      Be transparent
·      Design for Experience
·      Progress iteratively
·      Collaborate
·      Start where you are
·      Observe directly
·      Keep it simple

Consider the culture of your organization and its use of ITIL’s CSI Approach and these principles.  You are not likely get the results you expect from any one methodology without them.  Feel free to respond to this and tell us your ideas and examples for how Agile, LEAN, DevOps and ITIL can dove tail together to optimize efforts for ongoing service evolution. 


And… Don’t forget to Educate and Inspire!

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