Skip to main content

The Year of Shattering Silos

This is the year to shatter the silos.  Consider any best practice, method or standard that you have or are thinking of implementing.   In any DevOps, ITSM, ISO or Lean initiative the biggest challenge that any CIO or organization as a whole will have to address is how to meet the rate of demand and the dynamic business requirements.  Dynamic business requirements are a norm not an exception and the service provider will need to ensure fluidity throughout the value stream.  Shattering Silo’s will be a prerequisite to achieving end-to-end workflow and agility. 

Functional Silos
When talking about silos most practitioners immediately think of integrating departments or functional teams.  One of the more obvious silos to address here is the division between development and operational teams (DevOps).  While there is a lot of buzz in the industry on how to bridge that great divide, the real chasm that hinders efficiency and optimization is that between the business and IT.  Business performance is directly related to IT performance and the business side of the house must engage IT in all strategic initiatives.  Not only to ensure functional and nonfunctional requirements but I am speaking here of full on consistent support and engagement with IT to ensure an ever evolving service belt.

Technology Silos
Outdated, disparate, and nonintegrated tools and technology are killing the opportunity to achieve real competitive advantage, time to market and business outcomes.  A holistic approach to tool selection to support DevOps, ITSM and Lean will have to be looked at from and integrated tool chain perspective.  Enough already with replicated tools effort and resources.

Process Silos
Ok… now we are really getting to the crux of things. When attempting to bust out of and to shatter silos.  Those organizations that have attempted it will be the first to tell us that we should never have a “Configuration Management Process” project or “” project.  Instead you might have a project to “Record and Track Changes” in order to restore service quickly and reduce business and customer impact.   This initiative would like to look at how to integrate some small increment of integration between Incident, Problem, Change and Configuration Management.  This is very different than having an over worked bureaucratic configuration or change control process that hinders more than it helps. Every process design or improvement initiative that is driven by customer and business needs and requirements would work best to deliver value.  When projects are not driven by the voice of the business or the voice of the customer we tend to end up with process for process sake.  Taking an iterative agile approach to process design and looking at what might be required for a holistic integrated process approach across the software development and service lifecycle is likely to avoid a lot of bureaucracy, bottlenecks and impediments in the velocity and cadence required to meet dynamic business requirements.  Agile Service Management will truly help to shatter the “Process Silos”.

Information Silos
Functional Silos, Technology Silos and Process Silos create data and information silos.  Simply put, if your data and information are siloed, you will always be siloed and perhaps never have the capability to achieve true optimized business performance.

To learn more or to become a Certified Agile Process Owner or Certified Agile Service Manager:


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 th

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for the v