Skip to main content

DevOps – Skills For The Future – Am I ready?


Currently, 68% of organizations have begun to adopt, or plan to adopt #DevOps within the next two years.
If you are reading this because you want to embrace DevOps certification, knowledge and skills be sure to visit the DevOps Campus

This is all about DevOps skills? Are you ready?
DevOps Institute recently generated a very unique and interesting report title “UPSKILLING: Enterprise DevOps Skills Report”. Below are a few excerpts with some thoughts added.

Soft skills and technical skills “There is an equal balance between those who look for soft skills and those who seek technical skills when hiring externally or internally. About 30% of survey respondents said they look for soft skills first, as they believe they can always train or educate on the process and technical skills. And 32% looked first for technical skills to get benefits from the new hire.

Thoughts: It’s easy to become absorbed in a need for technical knowledge. Although that is required it is really the people skills are all too vital for DevOps success. We need - and MUST HAVE - DevOps leaders!

Jayne Groll, DevOps Institute, says, “The day of the specialist is gone as the future requires human capital which is “T-shaped.” This is a human with disciplinary depth, in the cloud for example, but with the ability, or arms, to reach out to other disciplines. Let’s work together to help people fill the top of their T.

IT Operations is a key functional skill ... but security comes in second.“The conversation around DevOps and its makeup is 10 years old this year. The combination of the terms Dev and Ops are perfect to reflect the key functional areas involved. IT operations knowledge received the most “must-have” votes (52% of respondents) as a functional skill. However, security incidents and breaches still happen far too often. Our survey respondents told us that security is the second must-have skill (47%). Additional must-have functional skills are IT infrastructure (44%), application design and development (42%), quality assurance (34%) and testing (31%).”

Thoughts: Infrastructure as Code is becoming a norm for a DevOps Continuous Delivery Pipeline. I believe that it is not until we recognize and understand the depth and breadth of … As Code … will we see the real value and cost savings that most hope for. This means things like “Security as Code”, “Policy as Code”, and oh yes, when it comes to IT Operations what about Availability and Capacity as code?
… Educate & Inspire with DevOps Test Engineering!

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…