Playbook for a Product/DevOps transformation
In the late 1970s, the U.S. automotive industry went into a quality crisis and was surpassed by the Japanese, who could assemble a car comparable to theirs with 60 percent of the effort and far less quality problems. Ford and General Motors eventually realized what was going on in Japan and adopted lean principles to help save themselves.
In the last ten years, tech companies went through a similar change through the adoption of cloud computing and DevOps. The DevOps movement started as a better way for operations and development teams to work together. Since then, it has become an umbrella for all sorts of tools and practices to improve business agility and organizational performance in the Age of Software.
This post is a compilation of ideas from the DevOps community, aimed at companies that have adopted DevOps technologies and practices, but not the culture. Typically, such companies have a functional organizational structure, with role-based teams and people working on many projects. They are on the cloud, but struggle with quality, complexity and ownership issues; have difficulty scaling the teams and aligning on priorities. This post suggests what can be done to improve, and further reading material.