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 th

The ITIL® Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem