DevOps Culture Myths and Antipatterns

DASA – the leading DASA organizational culture provider – shared a set of antipatterns, based on myths, which strongly oppose DevOps adoption and adaption. In my practice I often meet “devops engineers” and “we implemented devops, because we have ci/cd”. Let’s understand, what’s difference, and why DevOps culture first and precedes any technical tools, and why tools cannot create devops (rather they can be helpful locally).

DevOps Antipatterns: However, in practice, DevOps has different meanings for different people. Due to this confusion, organizations don’t realize the benefits of DevOps. Here are some antipatterns.

Agile is for development teams, and DevOps is for the downstream teams: Wrong. DevOps is about building end-to-end product teams, who own the product and are responsible for it throughout its lifecycle. These are the teams Amazon and Spotify popularized: the two pizza teams with build-and-run responsibilities.

The DASA DevOps team competency model  illustrates the skills and knowledge areas of an end-to-end responsible DevOps team.

DevOps is a CI/CD pipeline: Another common antipattern is to confuse a CI/CD pipeline with DevOps. DevOps is more than implementing a CI/CD pipeline. It is about embracing the technical and cultural practices that enable the smooth flow of small batches of work from development to operations, getting continuous feedback across the delivery pipeline, including from operations, and continually improving the process and the product based on feedback. 

The mythical DevOps engineers: This antipattern is widely prevalent and perhaps the most stressful for the unlucky person. Instead of the entire organization owning the improvement of software delivery performance, a person is responsible for it. Predictably, this doesn’t work. Instead of DevOps breaking silos, organizations create another silo and a bottleneck – the stressed-out DevOps engineer.”

Roles in DevOps team

What Are the Different Roles in DevOps? – DevOps Agile Skills Association (DASA) – We recommend the perfect – clear, concise and transparent article by DevOps Agile Skills Association (DASA) about main roles in a DevOps team. It breaks the fake about a single role – “team member” – for “Agile frameworks”.

The direct link is given above.

The main text is here –

The DevOps team plays a crucial role in the success of DevOps initiatives. The structure of this team can vary based on the organization’s size, project goals, and other factors, but it should always be designed to foster collaboration and cross-functional collaboration. This typically involves bringing together individuals from different departments, such as development, operations, and quality assurance, to work towards the common goal of delivering software quickly and reliably.

The DevOps team plays a crucial role in driving the success of DevOps initiatives. The team responsible for operations performs regular checks to ensure that new products are functioning effectively and smoothly, while development teams focus on designing, developing, and updating products to keep the company current. The collaboration between these departments allows for the rapid creation of applications and easier maintenance of current deployments.

Its structure is determined by the organization, its size, and the project goals.

In DevOps Fundamentals, we refer to:

“DevOps requires organizing the teams in a new way. It requires understanding the three factors or aspects (listed in the preceding figure) as follows:

  1. The value that customers derive from the different types of services
  2. The extent of the technology stack that is necessary to deliver the service
  3. Knowledge and skills required in the team considering the defined value and the service(s)”

In order to achieve this goal, a DevOps team typically consists of a number of different roles that work together to design, build, test, deploy, and maintain software applications. In this post, we will take a look at the different roles that make up a DevOps team and how they work together to deliver value to customers.

TEST AUTOMATION ENGINEER

test automation engineer is responsible for automating tests that can be used to validate software applications and infrastructure components. These tests ensure that any new changes are not introducing unexpected bugs or regressions into the system. What is more, they help quickly identify any problems and fix them before they cause any serious issues.

PLATFORM ENGINEER

platform engineer‘s role is to build and maintain the platform on which the organization’s software is developed and deployed. Its tasks may include setting up and managing networks, developing custom scripts to automate tasks, troubleshooting system failures and performance problems, overseeing server patching, monitoring system health and utilization metrics, etc. This role requires a strong technical background in hardware and software engineering, as well as knowledge of data center operations.

SECURITY ENGINEER

The role of a security engineer is to ensure the security and privacy of all applications, systems, and networks. It typically includes tasks such as conducting security assessments, by identifying threats and vulnerabilities, implementing security controls, and monitoring the security of the organization’s systems and networks. They may also be responsible for developing and maintaining security policies and procedures

ARCHITECT

The architect plays a critical role, as they are responsible for creating blueprints for the systems, designing the architecture, selecting the appropriate technologies, and ensuring that all components work together harmoniously. Moreover, an architect needs to be able to identify issues quickly and implement solutions accordingly. They should adhere to the “keep it simple” concept by keeping everything straightforward.

RELIABILITY ENGINEER

The reliability engineer’s primary responsibility is to ensure that the organization’s systems and services support the business in the most efficient and flexible way. This involves designing and implementing high-availability solutions, monitoring system performance metrics, scaling up servers or databases, and resolving configuration problems.

PRODUCT ENGINEER

product engineer plays a crucial role in product development, as they design and build the features of the product, along with ensuring it meets the customer’s requirements. This role requires strong technical skills such as coding, debugging, and troubleshooting, in addition to knowledge of engineering best practices. A product engineer must be able to write code quickly while also adhering to quality and security standards. They must have a deep understanding of the underlying technology that powers the product in order to ensure its stability and performance.

DATA SPECIALIST

data specialist is responsible for collecting, managing, and analyzing data from various sources to support the organization’s goals and objectives. They must be able to quickly identify patterns and relationships within large sets of data and develop insights that will help the organization make informed decisions. This includes using analytical techniques such as machine learning and predictive modeling to uncover trends or anomalies that can be used to optimize performance or resources.

TRANSFORMATION LEADER

transformation leader is responsible for driving organizational change in order to implement DevOps practices and principles. This can include tasks such as creating a vision and strategy for the transformation, aligning teams and resources, and supporting the implementation of new processes and tools. This role requires strong leadership skills such as strategic thinking, decision-making, and communication.

CIO/DIRECTOR OF IT

The CIO is the most senior technology executive in an organization. They are responsible for setting the technical strategy, driving the innovation, and ensuring alignment with the company’s overall business objectives. They must also have a deep understanding of emerging technology trends to ensure their organization’s competitiveness in a market. This role requires excellent interpersonal and organizational skills, strategic thinking, decision-making abilities, and people management knowledge.

PORTFOLIO MANAGER

portfolio manager ensures that the company’s investments are aligned with its strategic goals. They work with teams across the organization to identify and assess potential opportunities, develop and execute investment plans, and track progress against targets. They must possess excellent analytical skills as well as strong decision-making abilities. Financial background is very beneficial for anyone in this job role.

PRODUCT OWNER/MANAGER

product owner manages the product development process, sets strategic direction and priorities in addition to target outcomes. They work with engineering teams to ensure products meet customers’ requirements and expectations while staying within budget. Product Owners must have a deep understanding of the product lifecycle, market trends, and customer needs to effectively drive innovation and facilitate rapid product development.

BUSINESS & DATA ANALYST

business & data analyst is responsible for collecting, analyzing, and reporting on data to assist an organization to make informed decisions. They must be able to understand complex data sets and extract the most important information to present it in a clear and concise manner. Moreover, they must be able to analyze this data to identify trends and patterns which may impact the organization.

UX/UI SPECIALIST & CUSTOMER JOURNEY SPECIALIST

UX/UI Specialists and Customer Journey Specialists are responsible for creating experiences that are both visually appealing and engaging while making sure they meet users’ needs and the organization’s goals. They are focused on optimizing the customer journey from start to finish. Consequently, they should possess an understanding of user interface design principles, usability testing techniques, and accessibility best practices.

SERVICE MANAGER

service manager ensures that all products and services meet customers’ needs and expectations. They work closely with DevOps team members to ensure that projects stay on track and deliver desired results. Service Managers must possess a broad understanding of the development process, including software engineering principles, release cycles, quality assurance processes, and system deployments.

SCRUM / FLOW MASTER

Scrum Master is responsible for overseeing the entire product development process using Agile methodology. They must know its core principles and best practices, such as iterative development, cross-functional teams, and continual improvement. This requires the ability to evaluate and analyze project needs in order to create effective plans that meet organizational objectives.

GOVERNANCE SPECIALIST

governance specialist ensures that all products, services, and processes adhere to industry standards and regulations. They need a deep understanding of data security protocols, best practices, along with knowledge of the latest compliance standards and laws so that they can identify issues before they become major problems.

To conclude, there is no single “DevOps person”, instead we have different roles, each with specialized skills. By working together and leveraging automation and other tools, these teams can deliver high-quality software quickly and efficiently, supporting continuous integration and delivery. As the demand for faster and more reliable software continues to grow, the importance of effective DevOps teams will only increase, making these roles progressively valuable in the IT industry.”

New types of competency profile to boost your careers

I -, Dash, T- competency profiles became very popular for the last 5-7 years due to their value in Agile teams forming, and also building career tracks for professionals in the VUCA world.

AXELOS – the leading methodological vendor for ITIL, PRONCE, MoR and other popular methodologies and frameworks – presented its extended concept for teams and team members on emergent areas and markets.

Below is an excerpt of this article about newly designed M-, E-, ans X- shaped competency profiles.

M-shaped people have evolved from being Pi-shaped into those who possess multiple specialties (the vertical part of the M). From a resource management perspective, a person with one or more specialties are more adaptable than someone with a single speciality (I-shaped person) or even Pi-shaped. As such, each additional speciality changes the letter “M” to a comb. That is, where a person possesses more than three specialties to resemble a comb shape.

E-employee-200x200.jpg

E-shaped is a new paradigm shift, where people actively demonstrate a combination of four characteristics – Experience, Expertise, Exploration and Execution to form the letter E. E-shaped people who demonstrate the breadth and depth of knowledge have expanded their knowledge to include tangible (execution i.e. proven ability to deliver) and intangible (exploration i.e. proven ability towards continuous improvement) specialities. This implies the person has both vision and granular detail to make a discernible difference to the organization reminiscent of being a best practice practitioner in whatever domain or competency.

X-shaped people have a higher degree of self-awareness, adaptive capacity and the competencies to thrive in the future. Similar to the self-actualisation in Maslow’s Hierarchy of Needs, this employee type refers to the pinnacle of individual capability and competency. That is, X-shaped people demonstrate uniquely human skills that are grounded in empathy and purpose. They move from domains of knowledge to a constant state of learning, continually adapting to the environment. People with X-shaped skills have deep expertise in specialities (or knowledge area) as well as strong leadership skills and credibility.”

Managing volunteers in startup projects

Involving volunteers is a winning strategy for a startup. But a big question arises – what are specific management and motivation activities for volunteers’.

First, the basic recommendation is that you manage volunteers as employees. If a volunteer takes responsibility for a project (its part) she or he is responsible

Second, motivate with giving transparent perspective of the project and potential volunteer’s involvement. It helps a volunteer to align his/her plans with your project. And for startup founders it provides more predictability – if a volunteer goes to leave a project he/she can notify in advance.

Third, agree on schedule in advance, at least a month ahead. For example, a volunteer is ready to be involved 10 hours per week.

Supporting Next-Generation Entrepreneurs

G-Accelerator is one of the next generation accelerators, which combines the incubator and accelerator studies for students’ and alumni’s startups.

Read the full AACSB article, how does it work.

And learn about 6 principles of selecting a startup with a good potential:

  • potential (20 percent),
  • innovativeness (25 percent),
  • possibility of creating triple impact (25 percent),
  • scalability (20 percent),
  • strength of the team (5 percent),
  • and achievement (5 percent).

DevOps culture – join our new virtual course

DevOps – which stands for Development and Operations – becomes well-known and even fashionable rapidly.

DevOps had been introduced as an organizational culture first. And we – as developers, engineers, support agents and consumers – can gain the most value by applying DevOps organizational and cultural practices for team building, organizing collaboration and work processes.

DevOps stands for united teams with full responsibility for a product/service from the very beginning to the end of its operational phase.

In the given course you learn what DevOps culture is, and what is the value of applying it.

You can join our course now for only $12.99 as early birds! Join us!