Skip to main content

DevOps - Cadence vs Velocity

Image
By
A developer recently asked me “What is the real difference between Cadence and Velocity?   Aren’t they both just talking about speed?”   Hmmm…  Good Questions.

Cadence

Generally thinking cadence can be tied to rhythm.  One thing to remember is that the DevOps value stream is much broader in scope than just Dev and Ops.  So what are we looking at here?  The rhythm of code integration, and how we align with that things like integrated testing?  Yes, but also consider that the code development integration and deployment has to be in rhythm with the demand that is coming from your Customer and Business side.  If we are not in sync or have the same cadence as the business demand all other measurements may not be beneficial.     Alright, now let’s consider that your design and development teams work diligently to implement Agile Software Development principles to align and sync with the business.  If the cadence in test and deployment is not in sync then you have a potential bottleneck and the cadence is off from the business.  It doesn’t matter if Dev is moving more quickly if Ops is not speeding up also. Companies cannot survive in today’s fast paced, competitive, technology driven business environment doing things the way they’ve always done them.  The impacts are too great. Cadence and integration with the business is a must.

Velocity

In Agile we learn that velocity is the measure of work that can be completed in a specified interval. In other words this is the amount of work that your team can absorb in that time box.  Therefore, as IT Service providers we need to measure our velocity in order to ensure that we are in sync or have the same cadence with the business.  Every stakeholder in the value stream that starts from idea to end of life for a product or service must ensure that their velocity does not break others who are working upstream or downstream from them.   In DevOps it’s the first way.  The first way is “the flow of work from left to right” or from business requirements all the way through to end of life. 

Although both cadence and velocity have an element of speed to them they are very different and can and should be measured to ensure alignment with the business and for optimization in a DevOps culture.  Understanding concepts, principles, and practices for DevOps can help to increase your velocity and ensure that your cadence is in sync with business demand. 

For more information please use these links:
http://www.itsmacademy/agile

http://itrevolution.com/2015-state-of-devops-report/
Labels:

Comments

Unknown said…

I simply want to say I am new to weblog and truly savored you’re website. More than likely I’m want to bookmark your blog . You actually have excellent writings. Thanks a bunch for sharing your web site.

Jorcel
www.imarksweb.org

April 14, 2016 at 2:37 AM
Unknown said…
This comment has been removed by a blog administrator.
February 4, 2017 at 7:31 AM
Post a Comment

Popular posts from this blog

Four Service Characteristics

By
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, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...
Post a Comment
Read more

What Is A Service Offering?

By
The ITIL 4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group.   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions 1. Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...
Post a Comment
Read more

What is the difference between Process Owner, Process Manager and Process Practitioner?

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...
Post a Comment
Read more