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

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 policies (r…

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 the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…