Skip to main content

Business Relationship Management (BRM)

Business Relationship Management (BRM) is the process and role that allows us, as a service provider, to establish a strategic and tactical relationship with our customers. This will be based on ensuring we understand the customer and the business outcomes they are trying to create and how and what services are engaged by the business to meet those defined goals and objectives.

A key activity of the BRM process is to ensure that as business needs change over time, we as a service provider, are able to translate these needs into requirements through the use of a Service Level Requirements document (SLR) which then manifests itself into the portfolio in the form of defined services.  The BRM will assist the business in articulating these requirements and the value of these services that the business places on them. In this way the BRM process is executing one of its critical success factors, which is to safeguard that the customer’s expectations do not exceed what they are willing to pay for and that the service provider has the resources and capabilities to deliver these defined services on time and within budget guaranteeing customer satisfaction.

The BRM process is not just concerned with delivery and support of services but also with the design and building which means that it will engage with other ITSM processes across the entire ITIL lifecycle.  As an example, the mapping of business outcomes and services is done in portfolio management.  Service Level Management (SLM) provides information about the levels of service agreed to and achieved.  Service asset and configuration delivers a clear and concise picture of infrastructure, applications, services, service owners and customers. Capacity management supplies information about utilization levels and the potential impacts of new technologies.

Strategic and tactical changes can be initiated by the BRM and raised to improve the existing services, or to introduce new services that will improve the way that IT supports the business, therefore continuing to ensure customer satisfaction. The BRM will often initiate RFC’s in the name of the customer, and represent the customer in the Change Advisory Board (CAB) meetings. In the instances where acceptance testing is needed, the BRM may be engaged by the Service Validation and Testing  process to provide the appropriate individuals for this form of testing to be completed. Much of this activity may be initiated under the banner of Continual Service Improvement CSI.

The BRM should not only monitor incidents after large changes or implemented projects (early life support), but can perform a significant role in keeping the customer informed about the resolution progress during major incidents.  The BRM process should also engage with the SLM process to review service levels along with historical incident and problem records to determine any impacting trends on the level of customer satisfaction. 

To learn more, check out ITSM Academy's BRM elearning course, which leads to BRM Practitioner certificate.


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…