DevOps can be traced back to the 1980s when it was introduced to the traditional enterprises then In 2010 Damon Edwards coined the acronym CAMS (Culture, Automation, Measurement and Sharing) which set the core values of the DevOps movement. Then, Jez Humble added Lean to the mix, giving us CALMS.
Culture: Effective teams are essential for the delivery of reliable software and business benefits.
Automation: This at the core of development to build, test and continuous deployment. Bringing a high level of automation to development cycles will provide enormous benefits.
Lean: Inbuildingand controlling of systems, agile techniques and Lean practices come into play. Lean testing cycles allow frequent and effective testing which is core for performance.
Metrics: Measuring success is an important aspect of the feedback process. A successful DevOps implementation should measure performance, process and even people metrics.
Sharing: Collaboration and optimisation of ideas, stories of problems and success is essential and also the realisation for the teams to treat the problem as an enemy and not each other. Sharing of ideas opens the channels of feedback and so leads to improvement.
DevOps is a process, a journey that organizations will move through at varying speeds and levels of adoption but the evolution depends on rapid adoption, leveraging and internalization of the CALMS concepts. This approach will give the organisation the ability to change to the demands of the business.
Topics to be covered:
- How ARA ( Application Release Automation) makes DevOps possible
- DevOps starts with mutual collaboration
- Creating a fast feedback loop with the right metrics
- Making DevOps fit with governance and regulation
- Bringing development, testing and operations together
- Continuous delivery
- Case study: Lean application delivery
- Case study: DevOps in the enterprise
- Agile, DevOps and ITIL: Implementing enterprise release management