Whats is #DevOps ?

What is #DevOps?

DevOps isn’t a fixed methodology or process; it’s a community of practice and a set of principles. DevOps advocates Damon Edwards and John Willis described DevOps in 2010 with the acronym CAMS: culture, automation, measurement and sharing. Let’s look at each of these elements.

1. Culture
First and foremost, DevOps is a cultural undertaking; it’s about much more than embracing new tools and practices. It’s about setting expectations and priorities, and the fundamental beliefs that guide these expectations and priorities. The 2015 State of DevOps Report shows there’s a strong link between culture and successful management practices. We recommend you read the report’s deep dive into the characteristics of a successful DevOps culture.

2. Automation
Automation is a given in any team that has embraced DevOps; it’s just the way everything is done. Through automating common and repetitive processes, we aim both to make more time for higher level work and to open up opportunities for innovations that wouldn’t be possible otherwise.

3. Measurement
Integrating feedback into work is a fundamental part of agile and lean practices. For mature DevOps-minded organizations, this means measuring absolutely everything that moves in production, and sharing those measurements with the widest possible audience. When embarking on a DevOps transformation, however, this can feel a long way off. So start with a smaller number of critical measures that map to business outcomes — for example, deployment frequency, lead time for changes, mean time to recovery (MTTR), change fail rates, etc. Metrics from the live service are useful for much more than just keeping the service running: They can show you and your team where there are opportunities for quick wins that will benefit the
organization’s mission.

4. Sharing
Today’s complex organizations and software require teams of people with different skills and specialized knowledge. In order to work efficiently, however, it’s important to work well together. Sharing facilitates this. One way to share more early on is by exposing metrics to everyone, as described above. There are also benefits to sharing outside the organization, whether that be contributing to open source projects, talking about your experiences at conferences, or writing public blog posts. Your team gets to share pride in its work, and you can also open dialogue with people outside whose ideas and experiences can benefit your organization. Sharing tools, skills, information and your successes are all part of building an effective organization.