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

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 then 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 Offe

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 the

Search