Skip to main content

Stability vs Responsiveness

In an earlier blog I spoke to the conflicts that all operational organizations face.  This struggle can be broken down into four general imbalances so that an IT organization can identify that they are experiencing an imbalance by leaning more towards one extreme or the other.  At a high level it can provide the service provider with the opportunity to develop some guidelines on how to resolve these conflicts and move towards a best practice approach in resolving discrepancies.  We talked to the first and most common which was the Internal IT view vs. the External Business view.  Today I would like to speak to the dilemma of Stability vs. Responsiveness.
IT operations must ensure that the IT infrastructure is stable, performs at an agreed and defined levels on a consistent basis and is available with the correct amount of capacity to meet the demands of ever changing patterns of business activity.
These changes can be evolutionary.  Needed changes in functionality, performance and technology can happen over a long period of time.  These types of changes can present the service provider with the opportunity to plan, design, build and test better levels of performance and create greater efficiencies and more effective use of resources.  In these scenarios it is much easier to maintain the desired stability IT is seeking, while enhancing customer satisfaction by delivering the new requirements their customers and users seek.
Although as service providers we would always prefer to have our changes presented and delivered in this manner, we know that in today’s business environment this is not always possible.  Many changes happen very quickly and come with considerable constraints on timescales and resources.  The ability to meet these types of deadlines and not impact the services that are currently live can often be a considerable challenge to any IT organization.
Given this tension between stability and responsiveness there are some actions an organization can take to enhance its ability to meet these challenges.
  • Ensure investment in technologies and processes are adaptive and incorporate the use of change models
  • Build a solid service level management (SLM) process with strong ties to all processes from service design all the way through to continual service improvement (CSI).
  • Through service asset and configuration management (SACM) ensure the proper mapping of IT assets to business services and IT operational activities
  • Initiate the change process as early as possible.  Ensure there are strong ties to the project management office (PMO) and the business change process.

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…