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 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

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

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

What Is A Service Offering?

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

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