9 ways to tell if you’re really a DevOps organization
Many people believe that their organizations use a DevOps approach, but the “best practices” they’ve adopted aren’t consistent with a DevOps methodology. You can call what you do at your organization “DevOps,” but if you don’t follow the basic software methodology principles, it’s not DevOps. Period.
Here’s a set of objective criteria you can use to determine whether what you’re doing is truly DevOps. You’re really doing DevOps if…
1. You have frequent, rapid release cycles.
2. Deployment to production is fully automated, and you can automatically roll back.
3. You do continuous integration with automated testing at every check-in.
4. You have far more resources devoted to automated testing than manual testing.
5. Your developers, testers, and operations engineers work together.
6. Your developers, testers, and operations engineers have common, business-oriented goals that cover the whole value chain.
7. You’re paying back your technical debt.
8. Management gives the team the authority to make the changes it needs to make—and the team makes those changes.
9. You have feedback mechanisms in place to ensure continuous assessment—and act on that feedback to ensure continuous improvement.