The Top 11 Things You Need to Know About DevOps
(“formerly known “Top 10 Things You Need to Know About DevOps”)
Now more than ever, IT serves as the nervous system of the organization, as well as making up an increasing amount of a company’s muscle mass. Why? Most critical business functions are entirely automated within IT, 50% of all capital spending is technology-related, and 95% of all capital projects depend on IT to get done.
Today, nearly every market initiative or business decision will result in at least one IT change.
And yet, within the IT organization, both Development and IT Operations are locked in tribal warfare, often mired in urgent and unplanned work, starving their ability to execute. Spending countless hours dealing with emergency outages and failures and laboring over needless compliance projects, IT all too often gets stuck with damage control instead of deploying features and changes, and helping the business win.
The term “DevOps” typically refers to the emerging professional movement that advocates a collaborative working relationship between Development and IT Operations, resulting in the fast flow of planned work (i.e., high deploy rates), while simultaneously increasing the reliability, stability, resilience and security of the production environment.
However, as vibrant as the movement is, one valid complaint about DevOps is that it’s difficult to describe. Currently, DevOps is more of a philosophical movement, not yet a precise collection of practices, descriptive or prescriptive (e.g., CMM-I, ITIL, Agile, etc.).
We’ve conducted extensive research in the process of writing the upcoming books “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win” and “DevOps Cookbook.” We’ve put that into this whitepaper, answering the following questions:
- What is DevOps and where did it come from?
- How does DevOps differ from Agile?
- How does DevOps differ from ITIL or ITSM?
- How does DevOps fit with Visible Ops
- What are the unpinning principles of DevOps?
- What are the areas of DevOps patterns?
- What is the value of DevOps?
- How does Infosec and QA integrate into a DevOps work stream?
The white paper also includes my top three favorite DevOps patterns:
- Pattern #1: Making environments available early in Development projects
- Pattern #2: Embedding Development into IT Operations work
- Pattern #3: Standardizing the deployment stories into Development