DevOps Metrics – Time vs. Cost

There are three main principles that will help to optimize your DevOps initiative. You may have heard them referred to as The Three Ways.

All three of the principles will have a role to play but for the purpose of Time vs. Cost, I would like to focus on the first way which is “The Flow of Work from Left to Right”. When considering this flow of work think of the value stream from left to right as being from the time the request is made until the time that value is realized.

Using LEAN methods and applying techniques like the Theory of Constraints we can increase velocity to apply just the right cadence to meet the evolving business demand.

These practices along with our DevOps integration, Continuous Delivery Pipelines and automation will radically increase the time to value for products and services. Time is a key metric. DevOps organizations use “time” as the primary measurement tool.

Why time is a better metric than cost:

Time is used to set goals beyond lead time and cycle time
Time is used to design how work is organized
Time is measured at the physical activity level
Time is used to diagnose problems (early in the pipeline, NOT in production)
Time metrics used will force IT to look at the overall process, policies, and governance of the overall process
Time metrics enable for improvements that really matter

Most importantly time impacts both quality and cost. Therefore, if you were thinking “What about quality or what about cost”, consider the impact that the time to perform all delivery, test, compliance and support will have on both of those.

For every quartering of the total completion time, productivity will double, and cost will be reduced by 20%.

More than ever business must compete. We are competing against time!

Inspire & educate…

Resources!

Comments

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

What Is A Service Offering?

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

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

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

Search