Skip to main content

Business and IT Strategy – 2016

As the New Year begins, most IT service providers already have their IT strategy in place.   A few decades ago we heard loud and clear… “You must align IT with the business”.  Then we heard in the next decade…  IT...”You must align with the business”.  Notice the focus was on what “IT” must do.  I believe that most IT organizations get that.  The real question when considering a strategy is how this can be achieved.  Or is it?  

I hope that moving forward the new mantra will be “Hello business”… “You must engage IT in order to ensure success.”  If the strategy does not include how the business is going to consistently engage, plan and strategize with the IT organization it is possible that the business strategy will not ensure the type of success that is hoped for and could continue to miss the mark.

A recent BizReport article by Kristina Knight states; "During 2016, the perception that developers are basement-dwelling, socially-awkward techies with no grasp on business reality will continue to be shattered.  As "software eats the world," and as companies change their core competency from "shifting atoms" to using software to delight customers, developers will become distributed across lines of business and into the C-suite as they create business processes in software in real time. As a result, companies will need to publicly change their image, as well as changing their internal thinking.

While you might not be ready to put developers in the board room, at the very least we have to consider representation for all areas of the IT value and delivery stream and how to engage them in the business strategy and process.  This includes Process Owners, Service Owners, Engineers, Developers and most importantly representation for the ongoing operations of any service or product.

IT Strategies should instigate action to bust out of silos.   Not only Silo’s within IT but we should also consider the big chasm between the Business side of the house and that of IT and the technical side of provisioning services.  Also as we look forward we can no longer afford to silo our governance, standards and best practices.    We know that business performance is directly related to IT performance.  It only makes sense to have an integrated strategy.   What is your strategy for 2016 and moving forward?  Does it include an integrated and iterative approach that leverages Agile, Lean and ITSM? 

For more information regarding training and certification for Agile and ITSM: http://itsmacademy.com

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

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 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