Skip to main content

The Best of Service Strategy, Part 5


ITIL 2011:  Business Relationship Management
Originally Published on August 16, 2011

With the recent publication of the ITIL 2011 edition, several items within the best practice set have undergone a transformation. One of the goals of the 2011 edition is to bring even more consistency and standardization to the best practices by formally recognizing and organizing several ideas and activities that the 2007 edition had not previously structured as full, formal processes.  While always referenced in the 2007 edition (and ISO/IEC 20000), Business Relationship Management is now an official ITIL process
The newly structured Business Relationship Management process now formalizes the activities and links between the customer or user and the service provider through a central contact point embodied in the Business Relationship Manager role.
The ITIL 2011 edition states that the purposes of Business Relationship Management are twofold:
  • To establish and maintain a business relationship between the service provider and the customer based on understanding the customer and their business needs
  • To identify customer needs and ensure that the service provider is able to meet these needs as business needs change over time and between circumstances. Business Relationship Management ensures the service provider understands these changing needs.
The key to making full use of this valuable process is to see that it focuses on the needs of the customer and the business. The service provider (whether that is IT alone or in conjunction with other internal business functions) needs to have a means of staying in touch and in tune with the entities (the customer and the business). The Business Relationship Management process serves in this capacity. This touchpoint also provides a way of anchoring the service provider to the customer and creating full business-IT alignment and integration so that everyone in the organization focuses on the same outcomes and objectives.

Rather than leave the activities of the Business Relationship Management process up to chance, ITIL 2011 identifies that we can and should manage all activities undertaken as formally documented and mature processes. For Business Relationship Management these include two key activities:
  • Being the voice of the service provider to the customer
  • Being the voice of the customer to the service provider
As the key role in the process, the Business Relationship Manager serves as this voice through ongoing communications and interaction with representatives from the customer and the service provider. Business Relationship Manager could also easily combine with the Service Level Manager role to create a seamless conduit from customer to service provider capabilities used to ensure value.
The Business Relationship Management process is a simple yet powerful tool to ensure value to the customer and the business. Now that the process has a formal structure, it should provide even more benefit to your organization as you work to increase quality and customer satisfaction.

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…