Skip to main content

Velocity

Velocity, it’s just such a cool word!  When I type it, it just has to be italicized.   When I say it, I think of a speeding red Ferrari, a fighter jet or Superman zooming through the air to save Louis Lane from certain doom.  It’s one of my favorite TV channels.  In the world of Dev-Ops, Scrum and Agile it’s the rate at which a team converts items to “DONE” in a single Sprint, usually calculated in Story Points and is really one of the pillars of the DevOps.

DevOps is a response to the symbiotic relationship of software development and IT Service Management and the historical disconnect that has usually separated these two very critical and interdependent functions.  This divide has often manifested itself as conflict and inefficiency. The purpose being to help an organization rapidly produce software products and services while ensuring communication, collaboration and integration between these diverse professional groups.
Development is usually of the mindset where change is the thing that they are supposed to accomplish. We must respond to changing business needs rapidly and therefore are encouraged to create as much change as possible. With “Velocity”.
Operations views change as the enemy.   Keeping the lights on and delivering the services that that ensure utility and warranty, resisting change as it negatively impacts stability and reliability is where our focus is and should be. How many times have we heard the statistic that 80% of all downtime is due to those self-inflicted wounds known as changes? Believe me, I have lived that reality.
Let’s face it; in the world of ITSM, the current standards and frameworks that are employed, well Velocity isn’t really at the top of our priority list.  One of largest single points of frustration for our customers and the development side of the organization is this lack of Velocity!
In life and business everything changes.  Today’s reality is that in order to just stay even with the competition, we in the operational side of the organization are going to have to embrace this thing called Velocity.


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