DevOps is not an agile framework it is more like strategy or a culture aligning the developer team functions with the operation team. It fits in a lot of Agile frameworks like SAFe and XP and many others are adopting this aproach. In terms of the operation there is more focus on the code repository, the build and finally the release or deployment activities. One of the biggest issues around releasing code base into production is reliability and stability the desire for safe releases are especially high particulary where a level of automation.
DevOps focuses its strategy on remediating the risk allowing software driven activities to test promote code in to a centralised shared source, for example: git hub, control the version and test the build functionality before proceeding with the release and then deployment activities and sharing feedback in the process.
The term DevOps was first introduced in 2009 by the Belgium Patrick Debois and Andrew Shafer from the US. Debois was instrumental towards the DevOps culture we have today. The objective was to introduce more collaboration and transparency with a view of automation between the processes of the devlopment team and IT operations.
DevOps uses these pillars or principles as part of the mindset when taking such an approach.
The three factors that are aligned to sharing are Visibility, transparency and Knowledge. Everyone in the DevOps team works towards a common goal, the visibility allows everyone to be alert to unpredictable activities within DevOps environment. Promotion for knowledge embraces the mindset for continuous improvement.
This model incorporates the activities involved in a Devops culture. The mindset is cyclical with feedback loops embodied into the process.
|Contact Vas Rabani for any comments on the website or queries|