Skip to main content

BRM, DevOps and Excellence in IT Service Management

To say that digital technology has changed the world is an understatement. Digital transformations are revolutionizing entire industries and reshaping every aspect of business. To stay competitive, businesses must accelerate the delivery of digital products and services. To meet business demand, IT organizations must accelerate the delivery of secure, high-quality and reliable software features and functionality (DevOps).

The thing about any transformation, whether it’s the digital transformation affecting the world, or the DevOps transformation affecting IT organizations and their business partners, is that it’s never only about the technology. A successful transformation requires shifts in peoples’ behaviors, mindsets, vocabulary, roles and reporting relationships. It requires changes to processes and to day-to-day operating procedures.

Perhaps most importantly, the ability to undertake and achieve any transformation is determined by whether, or not, the company’s leadership has articulated a clear business strategy and has fostered a culture that embraces innovation, collaboration, and experimentation, taking risks and learning from failure (The Third Way).

Here’s where Business Relationship Management comes into play. As a discipline, Business Relationship Management embodies a set of competencies (knowledge, skills and behaviors) that foster productive, value-producing relationships between an IT organization and its business partners. As a role, a Business Relationship Manager (BRM) is a link between a provider organization and one or more business units. BRM(s) work with business units to understand their needs and plans and to coordinate the delivery of IT services that meet those needs. Ultimately, BRMS help move the IT organization from being viewed as an order taker into a strategic business partner.
But herein lies the reality. Business unit leaders aren’t going to be willing to discuss strategic plans with BRMs until they can trust that the issues of today and this week (incidents, problems, changes, releases) are being taken care of. The road from service provider to trusted advisor to strategic business partner is built on a foundation of IT service management excellence.

The same can be said for DevOps. You sometimes hear that DevOps and IT service management (ITSM) aren’t compatible (but that’s another blog for another day). The reality is that organizations that are successfully adopting DevOps practices such as continuous integration, continuous delivery and continuous testing are performing ITSM processes. Those processes are just so streamlined and, in many cases, automated that people don’t even realize that they are executing ITSM processes.

Will excellence in ITSM guarantee the elevation of the IT organization to strategic business partner? Not necessarily. But BRMs will never get a seat at the table when strategic conversations are happening without it.


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 …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility