por The DevOps methodology is based on the principles known as The Three Ways, that aim to improvement of value stream or value flow of DevOps practices. These principles are divided into three large blocks, these being: workflow, feedback and experimentation. In this post we will tell you about these fundamentals of DevOps and how they have changed the way development and operations teams work.
The first way: workflow or value stream
The value stream is defined as the actions necessary to design, produce and deliver a good or service to the customer. A successful and technologically valuable workflow It goes from the business proposal to the creation of a service that adds value to the client..
The First Way states that work should flow in a single direction, that no known errors should move to the next point in the flow, and that You should always seek improvement and increase in flow.
To improve this flow, the DevOps methodology suggests make our work visible, This helps identify which part may be slowing down the flow and which limitations may be accumulating work. Similarly, it is proposed limit the work in progress to avoid delaying the time to complete tasks by establishing limits at the column or work team level in a Kanban panel.
Also, it is suggested reduce the scope of tasks as well as dependenciess, since both lengthen waiting times and make it difficult to detect and correct errors. Furthermore, The First Way raises the need for identify and elevate restrictions on our system to improve its performance through continuous code deployment, configuration and execution of automated tests, and coupled architecture that allows safe and autonomous changes.
Finally, this principle proposes avoid difficulties through waste disposal as processes or features too much, etc.
The Second Way: Feedback
The second of the DevOps fundamentals establishes that enable mechanisms of feedback continuous upward in the value stream. It must be fast, frequent and of quality, which helps us detect and correct errors early and facilitate the creation of learning. Its principles propose properly managing complex work in secure systems, as well as studying problems when they happen and then solving problems in swarm mode, mobilizing whoever is necessary. This will prevent the spread of the problem.
Likewise, it is proposed to demand quality in all areas, avoiding inspection steps and approval processes. Finally, it is proposed to optimize work, creating quality at source.
The third way: continuous learning and experimentation
This third foundation suggests that promote experimentation and learning, achieving mastery through practice and learning from both successes and failures. Its principles propose that development and operations teams operate in a learning-based DevOps culture which will be reinforced by leaders. For this, it is necessary to establish the foundations of a generative culture, where blame is not sought when an error occurs, but instead analyze and redesign the system to prevent it from happening again.
It also suggests turning the improvement of daily work into an institutional practice, as well as always going further to the seek to transform local discoveries into global improvements. Finally, it is proposed inject resilience patterns in our daily work.
How to learn more about DevOps?
If you are looking to understand and be able to use the fundamentals of DevOps for the continuous integration of software operators and developers, as well as implement DevOps to accelerate the life cycle of your processes, do not hesitate to enroll in our DevOps & Cloud Computing Full Stack Bootcamp. Discover how in less than 6 months you will completely master this methodology!