Skip to main content

Agile_ITSM - Ingredients for Success! - Part 1 of 2

Dynamic

We the service provider must meet the “dynamic needs of the business”!

Someone recently asked me “What does that mean exactly?”  If that is what we are all chasing after and that is what we as service providers must understand and meet, then what is it?!

The business demand for speed and productivity is not decreasing in any way.  The dictionary definition of “dynamic” is:
  • Always active or changing
  • Having or showing a lot of energy
  • of or relating to energy, motion, or physical force
This would mean that the needs of the business are constantly changing.  We can attest to that in our own experience.  So the question really becomes " How do we quickly adapt to that need?"

Agile

Being agile would mean that we are flexible so that we can adapt to change. We have to start looking at the provisioning of a service as a consumption cycle. Products are produced but a service is consumed.  Once consumed the demand for that service will increase or morph to a slightly different demand for different business needs.

As a service provider we must be “agile” enough not only to see that the dynamic need is shifting but also be able to provision for it fast!. 

In today’s environment we can use frameworks such as “SCRUM” and apply them not only to software development but to all stages of the service lifecycle so that every player in the value stream is playing on the same team with the same agenda and target in mind. SCRUM originated from a rugby term.  All players on the team instinctively know what to do based on where the ball is.  Their role is dynamic.  Each player is not only playing their role or position but they are shifting and changing until all players are working together as one “entity” for a common goal!

Process and Technology

Understanding that we must be “agile” and open to new ways to meet the “dynamic” need of business and services does not infer that we do not have a need for process, technology or the best practice that enables them. We do however need to have a major shift in culture within every stage of the service lifecycle so that we empower through “Process and Technology” to optimize our capability. Doing so will allow the service provider to provision bigger, better, faster, and more services than ever before to meet service requirements and the “dynamic” needs of the business!

Ok, so far this recipe for success includes the power to be “Agile” to meet “Dynamic” business requirements with the support of “Process and Technology”.  There is one more very important ingredient and it is the most important one in the recipe for success. You may have guessed it.  Stay tuned to the ITSM Professor for “The Service Providers Recipe” part 2… The secret ingredient!

.


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…