“DevOps” is a new methodology combining development and operations. You may think you understand what it means, but do you really? Even experienced DevOps practitioners may have holes in their knowledge. Here is a list of ten items that may help to fill such holes.
1. The term “DevOps” means combining development and operations.
2. While adopted by tech companies, “DevOps” isn’t about technology, but is more an aspect of corporate culture, and requires continual optimization.
3. Most agree about what a DevOps toolchain consists of. Those links are: to Plan, to Create, to Verify, to Package, to Release, to Configure and to Monitor. Teams should start from there and customize to their needs.
4. The fiction work The Phoenix Project is a foundational work in DevOps.
5. The term “DevOps Engineer” is not universally understood to mean the same thing. Some think that DevOps can be implemented with a team, others that it must be pervasive through the organization.
6. Yet, “DevOps Engineer” is a high-paying job, and many opportunities exist.
7. Although as a culture it may seem ethereal, DevOps can be measured empirically and should be for effective implementation. It can be measured through deployment frequency, how much change is implemented with each release, deployment lead time, the prevalence of failed deployments, and through Mean Time To Recovery (MTTR).
8. DevOps need not be restricted to startups but can help even large, established companies.
9. DevOps isn’t just good for IT departments but possesses benefits throughout an organization.
10. And, DevOps techniques need not be limited to IT companies, but are useful to many other industries.
Suggested ways to use DevOps techniques in your corporation: centralized communications, flexible roles, automation, focus on improvement, and identifying problems before production.