Skip to main content

Business Relationship Management (BRM) Metaphors

The Metaphors for Business Relationship Management (BRM) can be helpful ways to think about and describe the BRM role, discipline and organizational capabilities. There are three metaphors we currently use today.  They are as follows:

BRM as a Connector:

The BRM acts as a connector between the Service Provider organization and its Business Partners – forging productive connections between Provider resources and the Business Partner and among Business Partners.  There are three primary aspects to the BRM’s role as a connector:
  1. Facilitate productive connections and mobilize projects and programs.
  2. Stimulate, surface and shape business demand for the Business Partner while increasing the savviness within the Business Partner regarding the Provider’s services and products.
  3. Influence the Provider to ensure appropriate supply of services and products, both in terms of quality and capacity. (1) 
BRM as an Orchestrator:
The BRM also acts as an orchestrator between the Provider organization and its Business Partners – orchestrating key roles, resources and capabilities to stimulate, surface, shape and harvest business value.  There are three primary aspects to the BRM role as an orchestrator:
  1. Orchestrate capabilities to drive value from Provider services
  2. Coordinate and aggregate business demand for the Business Partner
  3. Orchestrate key Provider roles on behalf of the Business Partner (Enterprise Architecture, Subject Matter Experts, Project Managers and Program Managers) (2)
BRM as a Navigator:
The BRM also acts as a navigator between the Provider organization and its Business Partners, navigating both the Business Partner and the Provider along a path to realized business value.  There are three primary aspects to the BRM’s role as a navigator:
  1. Facilitate convergence between the Provider and the Business Partners.  Convergence breaks down walls and embeds Provider capabilities within the Business Partners so as to increase agility and business value.
  2. Facilitate business strategic planning and road mapping for the Business Partner.
  3. Guide key Provider roles on behalf of the Business Partner such as Enterprise Architecture, Portfolio and Program Management. (3)

Ref: 1,2,3 BRMIBOK

For more information on BRM click here:  http://www.itsmacademy.com/brmp

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…