Skip to main content

You too can Take Action! – Key Takeaways from DevOps Foundation Certified Professionals

Taking action is one of the most necessary steps in effectuating life changes. However, as most of us know, sometimes it is very difficult to take that first step and commit to a desired achievement. When delivering DevOps/Agile/ITSM certification classes, I like to stress that as leaders we must inspire. And this is true because Inspiration leads to motivation and motivation triggers ACTION!

Although this is true, a recent Forbes article opened my mind to another way of looking at this. In this article Svetlana Whitener states that: “You don’t need to wait to feel inspired before you implement a new behavior. You can immediately begin by gathering your willpower (a strong self-control determination that allows you to do something difficult) and stop procrastinating.”

So whether you dig deep into your inner self and use will power or you are inspired by others, take action! Both motivation and will power are necessary. The bottom line is this: Digital Transformation is real and IT service providers must act.

All certification courses from the DevOps Campus at ITSM Academy strive to educate and at the same time inspire learners to use what they learn in very real and practical ways. Below are some examples of some very “Key Takeaways” that Engineers, Architects, and Business Leaders and ITSM professionals glean from DevOps Foundation Certification and training classes that motivated them to – Take Action!
  • I am a DevOps Leader in our company and I did not really know what DevOps was until I took this class. Before, it was all about the automation for me. Now I know it is so much more about shattering the silo’s and the Continuous Integration. Integrated teams, integrated testing, integrated QA & Test and more. DevOps is a professional and cultural movement and now I really am a part. I will take these tools and start looking at how we can shift left with Security, Availability, Resilience and Integrated Testing. I will stay CALM with my DevOps values, Culture, Automation, Lean, Measurable, and most of all Sharing (CALMS).
  • Continuous Delivery and Continuous Deployment were always the same thing to me. After this class I can see that we say we are doing Continuous Deployment but we really are automating for Continuous Delivery. I can now use the knowledge from this class to leverage where we are and start looking at how we can move into a true Continuous Deployment pipeline. No more deception. 
  • Getting my team level set on the terms and concepts was very key. DevOps and what it is really comprised of was subjective. It is difficult to drive a digital transformation when everybody has a subjective viewpoint of what it is we are striving for. Getting level set with DevOps FND certification and training allows us to set, drive and communicate a vision and a strategy that is real and doable. 

DevOps Certification Courses

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…