Skip to main content

Roadmap

Most executives understand that a business’ performance is only significant when it is benchmarked against its competitors.  As an accepted business best practice it is expected that the functioning of an individual organization will be measured against other like type organizations. This practice of benchmarking oneself against competitors should be no different for any IT organization.  There can be no better instrument to utilize then benchmarking to insure whether the IT operation is providing a competitive product.  Without this peer to peer comparison it would be difficult at best to define if IT’s performance is weak, competitive or an industry leader.

Of course in order to benchmark you must first determine are my processes mature enough to ensure that I can gather the significant data needed for this undertaking.  If not then your resources would be better utilized in first assessing your processes maturity through tools such as the ITIL Process Maturity Framework (PMF).  An effective approach for conducting a process maturity assessment is to create a process improvement team (PIT) that can assess the level of maturity of your individual processes.

Through the initial activities of the PIT you can begin to define the characteristics of your processes. Once established, documented, defined and agreed, your team can begin to look at what challenges you face and what maybe the transition steps that need to be taken to begin the continual process improvement activities.  Organization and their processes are not usually able to move from an immature state to a world class industry leader status. This is a continuing and repeatable process and will need the appropriate timescale to be accomplished.

Just a couple of thing to remember. You have to start measuring - even if the metrics are imperfect, use them.  They will improve over time.  



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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

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