David Hernan Tardini

What Is DevOps? DevOps (a clipped compound of development and operations ) is a term used to refer to a set of practices that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals while automating the process of software delivery and infrastructure changes. It aims at establishing a culture and environment where building, testing, and releasing software can happen rapidly, frequently, and more reliably Where Did DevOps Come From? DevOps is the offspring of agile software development – born from the need to keep up with the increased software velocity and throughput  agile methods  have achieved. Advancements in agile culture and methods over the last decade exposed the need for a more holistic approach to the end-to-end software delivery lifecycle. The DevOps ideals extend agile development practices by further streamlining the movement of software change thru the build, validate, and deploy and delivery stages,

COBIT and ITIL,  Differences and connections  ITIL ( Information Technology Infrastructure Library )  ITIL could be seen as the way to manage the IT services across their lifecycle, ITIL describes in more detail the parts of enterprise IT that are the service management enablers (process activities, organizational structures, etc.). COBIT ( Control Objectives for Information and Related Technology )  COBIT is about how to Govern the Enterpise IT in order to generate the maximum creation of value by the business, enabled by IT investments, while optimizing the risks and the resources. The distinction between the two is sometimes described as “COBIT provides the ‘why’; ITIL provides the ‘how.’” While catchy, that view is simplistic and seems to force a false “one or the other” choice. COBIT is based on five principles : 1. Meeting Stakeholder Needs 2. Covering the Enterprise End-to-End 3. Applying a Single, Integrated Framework 4. Enabling a Holistic Approach 5. Separating Governance fro

The Scrum Master role Scrum Masters are those who fully understand Scrum, and help the Scrum Team by coaching them, and ensuring that all Scrum processes are implemented correctly. The Scrum Master is a management position, which manages the Scrum process, rather than the Scrum Team. Is a servant-leader for the Scrum Team. Besides ensuring that the Development Team understands and uses Scrum correctly, the Scrum Master also tries to remove impediments to the Development Team, facilitates their events, and trains and coaches them. The Scrum Masters help the Product Owners too, by helping or consulting them on finding techniques, communicating information, and facilitating related events. The responsibilities of the Scrum Masters are not limited to the Scrum Team. They should also help those outside the Scrum Team understand the appropriate interactions with the Scrum Team to maximize the value created by the Scrum Team. The Scrum Master usually leads the organization in its effort to