Skip to main content

DevOps - Cadence vs Velocity

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:

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

Unknown said…
This comment has been removed by a blog administrator.

Popular posts from this blog

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

What Is A Service Offering?

The ITIL4 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 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 than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

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