Skip to main content

10 Types of People Who Need to Understand DevOps

If your organization hasn’t adopted DevOps approaches yet, it probably will soon.

In the InteropITX 2018 State of DevOps Report, only 9 percent of the business technology decision-makers surveyed said that their organizations had no DevOps plans. A third said their organizations had already adopted DevOps principles and another 46 percent had plans to do so within the next two years.

As DevOps spreads, many IT leaders have questions about which types of employees should get basic training on the fundamentals of the approach. We recommend that at least the following ten types of people get a foundational education about DevOps:

1. Developers
In many organizations, DevOps begins with the application development team adopting Agile methodologies. DevOps begins to spread as those in the operations team start to follow some of the same principles.

2. IT operations professionals
DevOps is all about closer integration between development and operations, so it stands to reason that the people involved in deploying, configuring and maintaining your applications and infrastructure will need to understand what DevOps is all about.

3. QA/testing professionals
The testing team plays a critical role in continuous integration and continuous delivery, and having this group on board is one of the keys to successful DevOps adoption.

4. Project managers
The switch from waterfall development to agile processes means PMs need to radically rethink the way they put together schedules and workflow plans.

5. IT managers
No DevOps implementation can succeed unless managers are actively championing the approach and encouraging staff to use DevOps principles on a day-to-day basis.

6. IT executives
Some of the most successful DevOps teams are those with CIOs, CTOs, and directors of IT who are advocating for the adoption of the approach.

7. Business stakeholders
DevOps affects those on the business side who work regularly with IT just as much as it affects IT professionals. If everyone can speak the same language, it will make the entire company more productive.

8. IT security professionals
Many organizations aren’t just adopting DevOps; they are adopting DevSecOps, which brings security into the mix and requires everyone in the IT organizations to be responsible for security.

9. Consultants
If your clients are going to be adopting DevOps approaches, you need to understand how that changes their culture, technology and processes — even if your consulting practice doesn’t directly concern DevOps, lean, Agile or IT service management.

10. IT vendors
Ditto for technology suppliers. If you want organizations to choose your tools and solutions, you need to demonstrate that your products and services are designed for the way work gets done in DevOps environments.

Of course, many experts would tell you that anyone who works in IT or with IT could benefit from learning the basics of the DevOps approach. While it’s become something of a cliché, it is true that DevOps requires a cultural transformation. When everyone on the team has the same shared knowledge and shared vocabulary, it makes it that much easier to implement the cultural change.

Attending that training together, whether it occurs virtually or in a physical classroom, offers the additional benefit of a shared experience. It also gives team members the opportunity to learn from each other and begin to make some of the changes that will be necessary for their cultural transformation.

If you have team members who could benefit from a basic understanding of DevOps, we encourage you to consider a DevOps Foundation certification. It’s a 16-hour class that usually takes just two days of time but yields lasting benefits for the organization.

Originally posted by the DevOps Institute 

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…