Skip to main content

DevOps Leaders Take Action – Key Takeaways


Education, learning and certifications are necessary. Taking ACTION shapes our world.

Getting certified is certainly valuable for career driven DevOps practitioners and leaders but what is most rewarding is listening to attendees of the course talk about the results and key take aways. Below are examples of key take aways from learners who attended a recent DevOps Leader course from the ITSM Academy’s DevOps Campus. Read through them. Get some tips for your DevOps leadership! Be inspired and take action!

  • I liked the shared practices and discussion in class for the idea of figuring out who the "friends" of DevOps are. What I learned in this class will stay with me forever.
  • Our value stream maps (VSM) are very detailed and complex. Therefore, I plan to go back and simplify our VSM’s so that we are seeing the highest-level view of the value stream. I learned from the VSM activity in this class how powerful that can be. This will allow us to "sell" the improvement opportunity to our organization. Any VSM I've been involved with has been really "in the weeds". We are LEAN certified, and we are doing it all wrong. Creating the high level VSM in class and listening to other shared practices has motivated me to really get VALUE from our Value Stream Maps.
  • Because of this class, I was motivated last night to create a communication using some of the techniques that we learned. I sent it out to the country leaders and the response has been amazing. Establishing DevOps in our culture is going to be very time consuming, but it will be worth it. I created a sign in front of my desk that says “Listen, Acknowledge, Explore and Respond”. The discussion we had around these and many other techniques are all things that we know about at some level. Hearing how others apply them has really inspired me. I've taken so many notes about what the others in the class have said. It's amazing this is the first class I've taken where I understand everything. All the examples and everything you have shared has expanded my mind. I want to thank everybody for a great class.
  • One of the greatest challenges we have is that our organizational structure is not conducive to agile teams and DevOps integrated pipelines. Silo’s are killing us. Learning about the Tribe/Squad model and then listening to others talk about how they are restructuring was amazing. I always thought that I must have upper management driving the structure initiative and the course supports that. That said, I learned from others in the class how they organically started shifting in that direction while they had others working on the upper management buy in. I am committing right now to take action using some of these tips and techniques. I learned that not only can I shape my own career, I can really begin right now, today to shape the direction of this organization for the people that it serves.

DevOps Leadership - Be Inspired! Take Action!



Comments

Popular posts from this blog

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