The Best of the Professor: The Second Way

The “Best of the Professor” blogs will focus on one unique individual topic and will be followed by links to papers with more in depth information.

DevOps initiatives are supported by three basic principles. In his book “The Phoenix Project“, Gene Kim leverages the Theory of Constraints and the knowledge learned in production environments to describe the underlying principles of the DevOps movement in three ways. These principals are referred to as The First Way, The Second Way and The Third Way. This segment of “Best of the Professor” will focus on “The Second Way”.

The Second Way

In an earlier “Best of the Professor” paper we discussed “The First Way” and how this DevOps principle was all about the flow of work from left to right. “The Second Way in contrast is all about the flow of work from right to left. It is reciprocal.

How do we take all of the knowledge and learnings acquired and create feedback loops to the previous stage and ultimately back to development? If we think of this from a “Lean” perspective, we know that understanding and responding to users is important. As important is the communication and amplification of feedback to the next stage in the delivery stream. We have to respond to the needs of both internal and external customers via feedback. Ensuring the communication loops back to the starting point is critical to meeting dynamic needs. We must create and embed knowledge where needed.

The premise of a feedback loop is simple: Provide people with information about their actions in real time, then give them a chance to change those actions, pushing them toward better behaviors. The goal in “The Second Way” is to shorten and amplify feedback loops.

Be sure to search for other “Best of the Professor” topics for DevOps principles including “The First Way” and “The Third Way. Below are resources for practices that support “The Second Way”; feedback loops and the flow of work from right to left.

Monitor Control Loops : http://www.itsmprofessor.net/2012/02/monitor-control-loops.html

We’ve Gone Loopy (part 1): http://www.itsmprofessor.net/2013/08/itsm-weve-gone-loopy-part-1-of-2_20.html

We’ve Gone Loopy (part 2) http://www.itsmprofessor.net/2013/08/itsm-weve-gone-loopy-part-2-of-2.html

For information regarding training and certification:

DevOps Courses: http://itsmacademy.com/devops/
Agile ITSM Courses: http://itsmacademy.com/agile

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