Skip to main content

DevOps Leaders Take Action – Key Takeaways

Image
By

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!



Labels:

Comments

Post a Comment

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

By
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
Post a Comment
Read more

What Is A Service Offering?

By
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
Post a Comment
Read more

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

By
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
Post a Comment
Read more