Skip to main content

The Business Relationship Maturity Model

The Business Relationship Maturity Model (BRMM) is a way to help surface and understand the maturity of the relationship between a Provider (internal IT organization) and their Business Partner. This is not about the maturity of the BRM role or process.  This is about the maturity of the Provider/Business Partner relationship and therefore must take into account the perspectives of each party. The BRMM is made up of 5 levels, each with a descriptive tag, and represents a relationship maturity continuum. Level 5 is the highest and described as strategic partnering, Level 4 is trusted advisor, Level 3 is service provider, Level 2 is order taker and Level 1 being the lowest or ad hoc.

Level 1 Ad Hoc: From the Business Perspective (BP) it’s, can’t even get my providers attention, results cost too much, delivers too little and takes too long.   From the Provider’s Perspective (PP) it’s: I’m too busy to think about anything other than I’m too busy.   Characteristics of relationship (COR) are: unmanaged demand, unclear rules of engagement and no clear sense of value. To move to the next level the Business must embrace the reality of the existing capabilities and the Provider must establish demand management principles.

Level 2 Order Taker:  (BP) I engage my provider when I need something so they stay out of my way when I don’t need them. (PP) We are asked to be predictable but there is no way to forecast demand so we know we disappoint our business partners more often than not.  (COR) Frequent misperceptions build distrust and reactive course changes.  Prioritized demand based upon weak data, we/they relationship (antagonistic) and provider is completely reactive.  To move to the next level Business must embrace the BRM role and Service MGMT.  The provider must establish BRM and Service MGMT excellence.

Level 3 Service Provider: (BP) My provider prevents me from making big mistakes but I’m not always sure which direction we are heading. (PP) Our business partners help set priorities, but we are always behind. (COR): The routine is routine but innovation is a challenge, services are stable but major project deliverables are inconsistent, costs are transparent but value is subjective. To move to the next level the business must engage the provider in strategic thinking.  The provider must pursue Portfolio and Transition MGMT excellence.

Level 4 Trusted Advisor: (BP) My Provider is helpful and reliable. (PP) Our business partners understand our capabilities, works with them and helps to improve them.  (COR) Mutual understanding of capabilities and needs, portfolio is aligned to business needs and sense of value from investments. To move to the next level the business must embrace business value realization.  The provider must embrace continuous improvement.

Level 5 Strategic Partner: (BP) My provider is integral to business success and growth and helps me succeed.  (PP) We work together with our business partners to survive and prosper.  (COR) Shared goals for maximizing value, shared risks and rewards, quality data is being produced, innovation is cultural, complete convergence.

There are several ways to engage this model in helping your organization build a more agile business. It can be used to assess the current maturity level of your business/provider relationship and create and established an agreed baseline.  You can then incorporate this baseline to establish a strategic plan to identify improvement opportunities and create a timeline for maturing your organization through the 5 levels of the model. It provides the information to educate your BRM team and provider leaders on what the current state is and how they can engage to elevate business relationship maturity. It can also help to shape your approach on how the business & the provider can become strategic partners and move the organization forward and thrive.

For more information: 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…