What it had to solve
In 2007, Belgian consultant Patrick Debois was doing certification and readiness testing on a data center migration for a Belgian government ministry, straddling application developers on one side and server, database and network operators on the other. The wall between the two groups - separate methods, separate schedules, mutual blame - convinced him there had to be a better way to run IT.
The idea
Name the movement by naming a conference: Debois branded his Ghent gathering 'Devopsdays,' and the portmanteau stuck as the industry's own word for the whole truce.
How it works
At the 2008 Agile Conference in Toronto, Andrew Schafer posted a birds-of-a-feather session on 'agile infrastructure'; the only person who showed up was Debois. They formed an 'agile systems administrators' Google group with limited success. The break came in 2009: unable to attend O'Reilly Velocity, Debois watched John Allspaw and Paul Hammond's now-legendary Flickr talk '10+ Deploys per Day: Dev and Ops Cooperation' by video stream. Inspired - and nudged by people on social media - he organized his own event in Ghent that year and called it Devopsdays.
What it did
The name did what the Google group could not: it gave a scattered set of practices a single identity. Devopsdays spread to Mountain View in 2010 and to more than 30 cities by 2018; the word 'DevOps' migrated into job titles, team names, conference tracks, The Phoenix Project (2013) and Puppet's State of DevOps reports (from 2012) - the portmanteau is now how the industry describes itself.
Background
In 2007, Patrick Debois - Belgian consultant, project manager and agile practitioner - was embedded in a data center migration for a Belgian government ministry, running certification and readiness testing between two tribes: application developers pushing rapid iterative change, and operations teams guarding server, database and network stability. The walls of separation and the mutual finger-pointing planted a discontent that he carried out of the project.
At the 2008 Agile Conference in Toronto, Andrew Schafer convened an ad hoc birds-of-a-feather session on 'agile infrastructure.' Exactly one person showed up: Debois. The two kept talking, formed an agile systems administrators group on Google, and got limited traction - the ideas were right, but nobody had a flag to rally around.
The flag arrived in 2009. From the O'Reilly Velocity Conference, John Allspaw and Paul Hammond of Flickr delivered '10+ Deploys per Day: Dev and Ops Cooperation at Flickr,' role-playing the 'it's not my code, it's your machines' standoff and arguing that development and operations had to become seamless, transparent and integrated. Debois watched the stream, was galvanized, and - at the prompting of others on social media - founded his own conference in Ghent, Belgium, and named it Devopsdays. The word 'DevOps' had officially landed.
Why a conference name became history's word for it: the portmanteau put both warring parties inside a single term, and Debois, a neutral practitioner with no product to sell, handed the name to a community rather than a vendor. Devopsdays reached the United States in 2010 and thirty-plus cities by 2018, and the word now labels everything from team structures to the State of DevOps research reports.
Why it lands
The practices existed before the word - CI tools, agile methods, cloud automation, Flickr's deployment story - but without a name they stayed scattered; naming made them legible as one movement.
The portmanteau itself was the compromise: neither side had to surrender identity because both words sat in the term, which made it easy to adopt in hostile org charts.
Debois was a connector rather than a vendor, so the name stayed neutral property - no company owned it, and no competitor had a reason to fight it.
The conference format gave the word an annual home where practitioners could meet, which let the community, not a marketing department, define what DevOps meant.
What you can take
Name the thing and the thing becomes real: the practices had circulated for years, but movements coalesce around a word - and one practitioner with a conference room can supply it.
Since then
Devopsdays became a traveling institution: a first US edition in Mountain View in 2010 on the heels of Velocity, and more than 30 conferences scheduled worldwide by 2018. The vocabulary Debois coined carried a whole literature - Gene Kim's novel The Phoenix Project (2013), Puppet Labs' State of DevOps reports (from 2012), and eventually the DORA metrics - while 'DevOps engineer' became one of the most common job titles in software. Debois is still introduced as the movement's godfather, for a word he coined almost as a side effect of organizing a meetup.
FOLLOW THE EVIDENCE