Skip to main content

The Value of Business Relationship Management

One of the key processes in the ISO/IEC 20000 standard is Business Relationship Management. This process “establishes and maintains a good relationship between the service provider and the customer based on understanding the customer and their business drivers.”


Business Relationship Management (BRM) within ISO/IEC 20000 is one of the Relationship Processes (along with Supplier Management). These processes help to establish the links in what Harvard Professor Michael Porter described as the “value chain”. BRM creates the link between the service provider (including IT, but full delivery may involve other organizational functions) and the customers and users, both internal (“the business”) or external (“the end customer”).


Business Relationship Management is now a formalized process in newest (2011) edition of ITIL. With the newest edition, the authors recognized the importance of having BRM as an extent process, rather than as guidance embedded in other ITIL processes (such as Service Portfolio, Strategy Management and Service Level Management). The formalization of BRM now paints a complete picture of the service lifecycle, one that has slowly emerged since the earliest days of best practice guidance in the form of ITIL.
I sometimes encounter people who had begun their journey with V2 guidance, yet had only been exposed through formal training to the two core books of Service Delivery and Service Support. This narrow exposure gave them a limited perspective of the service lifecycle that had always existed (albeit in a disjointed and disconnected way). Unfortunately, many people did not know about or read the other books in the V2 library. However, best practice guidance had been put forth in V2 as to the importance of engaging the customer and understanding their needs. The last of the V2 books to be published, titled The Business Perspective, focused on this vital idea. In ITIL V3 (2007 edition), the authors brought this idea into the mainstream service lifecycle, yet had not made it a formal process. BRM has now taken its rightful place in the canon of processes in ITIL 2011.
I am very glad to see the full vision of the service lifecycle emerge. BRM is a fundamental process that helps a service begin its own journey to delivering value to customers and users. Although one could (and many have) begun their service delivery journey from IT outward, BRM provides an often misunderstood or forgotten view or perspective from the customer towards the service provider. Following the standards laid forth in ISO/IEC 20000, an organization can begin to build an even stronger linkage to those stakeholders who benefit most from efficient, effective and economical services delivered by service providers. 

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…