DevOps, a mashup of “development” and “operations,” describes the organizational structure, practices and culture required to enable rapid agile development and scalable operations. DevOps automates software assembly, leveraging continuous integration, development and deployment, to improve customer experiences, respond faster to business needs, and ensure that innovation is balanced with security and operational needs.
12 best practices for implementing DevOps
- Align DevOps strategy with the business. IT and business strategy alignment is a common refrain among CIOs but it’s just as important for DevOps, which will fall down if IT and the business aren’t on the same page.
- Bolt into existing programs. Don’t approach DevOps as a science project; rather, bolt it into existing programs so that it is beholden to the typical delivery deadlines.
- Go broad. Culture is essential. Be as inclusive as possible so you can “change hearts and minds.”
- Focus on what makes you unique. Choose projects that add value that will differentiate the business.
- Choose proven platforms. Tools are another essential component. From configuration management to continuous delivery platforms, pick tools that have known networks.
- Look for homegrown skillsets. There isn’t enough talent on the market so you should appeal to experienced talent across the organization. Loop them in to contribute to projects.
- Avoid “classes of citizenship” problem. Many organizations feature risk-taking engineers working on emerging technologies and engineers maintaining legacy technologies, such as ERP systems.
- Time is always a factor. Don’t underestimate the importance of time, especially for public companies that report quarterly financials. …
This article originally appeared in cio.com. To read the full article, click here.
To learn how DevOps teams can get operational intelligence from logs, metrics and transactions without building their own applications, click here.