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

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…