Skip to main content

IT Service Management - Tools

In today’s world where demand for up to date services has grown and the lead times for delivery has continued to be shortened I am often asked, what is the best tool? The answer is, of course, “it depends!” Every organization has different needs, budgets and resources, however the requirements for automated building, testing and delivering new functionality has never been greater.

Every organization must be able to look at the list of requirements for tools from both the operational and development sides of the IT organization as the functions become more and more integrated.

The starting point is a list of generic requirements. An integrated suite is preferable and should include options such as:
  • Service Portfolio
  • Service Catalog
  • Service Design Tools
  • Discovery/Deployment/Licensing Technology
  • Workflow or process engines
  • CMDB’S
  • Configuration Management Systems (CMS)
  • Self Help for Users
  • Remote Control
  • Diagnostic Utilities
  • Reporting Tools/Dashboards
  • Service Knowledge Management System (SKMS)
Depending on your requirements, goals, budget and maturity level, you may need one, several or all of the above technologies. A good suite will offer the flexibility to purchase only those modules that are currently needed by your organization with the option to add more over time.

The next step is to assess your current tools and their use. The assessment may reveal that you are not using existing tools to their fullest capability. Consider the following when evaluating existing tools and possible new purchases:
  • Support for monitoring service levels, data structure, data handling and integration
  • Integration of multi-vendor infrastructure components
  • Conformity to international open standards
  • Flexibility in implementation usage and data sharing
  • Usability
  • Distributed clients with a centralized shared database
  • Conversion requirements
  • Data backup, control and security
  • Support and scalability
The following are useful evaluation techniques:
  • Gather your Requirements. (Use the MoSCoW strategy for evaluating your requirements. Must haves (M), Should haves (S), Could haves (C), and our Won’t haves but would like to have (W)?)
  • From the MoSCoW list, create a Statement of Requirements (SOR).
  • Identify possible products
  • Determine a selection criteria
  • Evaluate products
  • Put together a short list of products
  • Score the final products
  • Rank the products
  • Select the product that meets your needs and budget
Please remember that any tool is NOT a silver bullet. Effective internal processes are critical to gaining efficiencies through tools. Tool success will likely depend on your planning, deployment, management and improvement of process.

While there are many good technologies in the marketplace today, it is important to select the one that meets your specific and unique requirements.

For more information please see ITIL Foundation, ITIL Service Design, ITIL Service Strategy


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 …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility