History of DevOps

Patrick Debois

ops

2007

When working for Belgium government, is frustrated by bad communications between developpers and operators.

2008

Agile 2008 Toronto: Andrew Shafer « Agile Infrastructure »

Patrick Debois is the only one present.

Even Andrew Shafer won’t do their own talk

Patrick catch Andrew and they created « Agile Systems Administration Group ».

2009

During velocity O’Reilly, John Allspaw et Paul Hammond:

“10+ Deploys a Day: Dev and Ops Cooperation at Flickr”

Patrick Debois can’t be there.

Drooling over #velocityconf09, I decided to organize a 2d devops OpenSpace in Belgium around October. Care to help/come? http://bit.ly/v5vVB
— Patrick Debois - #thinktogether (@patrickdebois) June 25, 2009

@nasrat indeed maybe we need to broaden the scope to Europe. Openspace or conference? Ops in generic terms or a focussed devops one
— Patrick Debois - #thinktogether (@patrickdebois) June 25, 2009

“Agile Administration System” is too long “There never was a grand plan for DevOps as a word.”

“DevOps” is known worldwide

Silos

Grain Silos

https://pxhere.com/fr/photo/543146

Oops I’m traped

Grain Silo Trap

Worked fine in Dev; Ops problem now

Platform Works fine; Dev problem now

CAMS

Culture
Automation
Measurement
Sharing

Culture

CAMS culture

Automation

Do not repeat same mistakes (again!)

Measurement

What can we improve?

Did we succeed?

Sharing

An End rather than a Means

DevOps is about eliminating technical, process, and cultural barriers between idea and execution - using software

Velocity

Bonus

What it isn’t

X tool

A job

A team

Agile

12 Values

Customer satisfaction by early and continuous delivery of valuable software.
Welcome changing requirements, even in late development.
Deliver working software frequently (weeks rather than months)
Close, daily cooperation between business people and developers

Projects are built around motivated individuals, who should be trusted
Face-to-face conversation is the best form of communication (co-location)
Working software is the primary measure of progress
Sustainable development, able to maintain a constant pace

Continuous attention to technical excellence and good design
Simplicity—the art of maximizing the amount of work not done—is essential
Best architectures, requirements, and designs emerge from self-organizing teams
Regularly, the team reflects on how to become more effective, and adjusts accordingly

Scrum

3 Roles

Product owner

Customer Representative

not a manager
not a project leader

Development team

self-organizing
same work

Scrum master

facilitator
coach
not opinion(ated)

Artifacts

User Stories

from the perspective of an end user

As a role I can capability, so that receive benefit

Product Backlog

Ordered list of US that should be done

Sprint backlog

Workflow

Sprint

iteration

Sprint planning

Daily scrum

Sprint review

Sprint retrospective

Backlog refinement (Grooming)

10%

Do not answer the waterfall problem

End

History of DevOps