Not formalized in writing the DevOps movement
Posted: Thu Feb 13, 2025 5:39 am
Is generated from practitioner to practitioner, from the set of real experiences that are shared through a community that collaborates in a decentralized and open way. Just check the hashtag #Devops on Twitter to verify the constant participation and flow of ideas on the subject.
With the interaction of Agile, Kanban, Continuous Integration and Cloud Computing concepts, the movement brings together the Development and Infrastructure areas in a global vision of the application life cycle to deliver value to the business. See Figure 1.
Using Agile and other software methodologies
Agile methodologies are characterized by the continuous delivery of small spain phone number data pieces of functional code at a pace and speed. Deliveries that only cover the software life cycle and the Development area, leaving out everything that involves configuration management and preparing components for release to Production.
The pace generated by agile methodologies such as Scrum and Kanban pushes components to the Testing and Integration area so that upon successful completion, they are delivered to Infrastructure in a continuous and rapid manner for installation, which is a problem when Testing or Infrastructure have the habit of releasing in time windows that are already defined and controlled. This creates pressure among all the areas involved; not everyone was prepared to work in an agile manner and now the excess of deliverables breaks with the pre-established work routines.
With the interaction of Agile, Kanban, Continuous Integration and Cloud Computing concepts, the movement brings together the Development and Infrastructure areas in a global vision of the application life cycle to deliver value to the business. See Figure 1.
Using Agile and other software methodologies
Agile methodologies are characterized by the continuous delivery of small spain phone number data pieces of functional code at a pace and speed. Deliveries that only cover the software life cycle and the Development area, leaving out everything that involves configuration management and preparing components for release to Production.
The pace generated by agile methodologies such as Scrum and Kanban pushes components to the Testing and Integration area so that upon successful completion, they are delivered to Infrastructure in a continuous and rapid manner for installation, which is a problem when Testing or Infrastructure have the habit of releasing in time windows that are already defined and controlled. This creates pressure among all the areas involved; not everyone was prepared to work in an agile manner and now the excess of deliverables breaks with the pre-established work routines.