The founding era of DevOps — from the term's coinage to its emergence as a movement with mass audience reach.
The two founding events. Two events in 2009 crystallized the movement. In June, john-allspaw and Paul Hammond presented "ten-deploys-per-day-talk" at O'Reilly's Velocity Conference, demonstrating dev-ops-cooperation at Flickr through shared tools, shared metrics, and a culture that removed blame as a barrier to moving fast. In October, patrick-debois organized the first first-devopsdays-ghent-2009 in Ghent, Belgium. The Twitter hashtag shortened "DevOpsDays" to "DevOps" — and the term stuck. These two events gave the nascent movement both proof and identity.
Community formation. The early DevOps community was small, practitioner-driven, and concentrated in web-native companies. john-willis was the only American at the first Ghent conference. The first-us-devopsdays-2010 in Mountain View brought the movement to the US practitioner community. At that event, Willis and damon-edwards coined the cams-framework — Culture, Automation, Measurement, Sharing — the first systematic attempt to define what DevOps meant beyond specific tools.
Conceptual development. gene-kim and others developed the three-ways framework: flow (left to right through the value stream), feedback (right to left), and continuous learning. This provided a theoretical backbone derived from lean manufacturing principles. The DevOps Cafe podcast (2010), co-hosted by Willis and Edwards, became a key venue for developing and disseminating ideas.
Mass audience. the-phoenix-project (2013, Kim, Behr, and Spafford) was the pivotal popularization moment. The business novel format — modeled on Goldratt's The Goal — reached IT managers and executives who would never read a technical manual. It dramatized the dysfunction of traditional dev-ops separation and the transformative potential of DevOps principles. The State of DevOps Reports also began in 2013, starting the empirical research program.
Who DevOps was, then. Early DevOps was a community of people who felt the pain of the dev-ops divide acutely and had figured out locally how to bridge it. Web companies, SaaS shops, organizations deploying continuously. Traditional enterprise IT was largely absent from these conversations. The Phoenix Project changed that.