fixing your org by continually breaking it
TRANSCRIPT
FIXING YOUR ORG
BY CONTINUALLY BREAKING ITJ. PAUL REED
RELEASE ENGINEERING APPROACHESDEVOPS DAYS AUSTIN 2015
J. PAUL REED
AKA “The Sober Build Engineer”
@SoberBuldEng on
Principal at Release Engineering Approaches
Chief Delivery Officer at Praxisflow
15+ years in build/release engineering
ALSO AVAILABLE ON ITUNES
www.theshipshow.com
@ShipShowPodcast
@eciramella@buildscientist
@cheeseplus@sascha_d
@petecheslock@SonOfGarr
@beerops
ALSO: I AM NOT THIS GUY
ALSO NOT THIS GUY
HEARD OF THIS BOOK?
IMPORTANT DETAILS
The Three Ways of DevOps
The Four Types of IT Work
Interviews with The Business™
3 WAYS RECAP
1. Systems Thinking
2.Amplify Feedback Loops
3.Culture of Continuous Experimentation & Learning
http://itrevolution.com/the-three-ways-principles-underpinning-devops/
SYSTEMS THINKING
http://itrevolution.com/the-three-ways-principles-underpinning-devops/
AMPLIFY FEEDBACK LOOPS
http://itrevolution.com/the-three-ways-principles-underpinning-devops/
WE FORGET THE 3RD WAY
http://itrevolution.com/the-three-ways-principles-underpinning-devops/
FEEDBACK “BOOMERANGS”
MIND TOO BLOWN?
MIND TOO BLOWN?
MIND TOO BLOWN?
#DevOps
“BRB, TOO BUSY TO IMPROVE”
“WELL, THAT USED TO BEOUR WEBSITE...”
RARE IN THE WILD
CONTINUOUS...
CONTINUOUS...
Integration
CONTINUOUS...
Integration
Delivery
CONTINUOUS...
Integration
Delivery
Deployment
CONTINUOUS...
Integration
Delivery
Deployment
Improvement?
The evidence of the last 20 years indicates that trying to copy or reproduce another company’s tools, techniques, or principals does little to change an organization’s culture.
— Mike Rother
DevOps
Culture Is Not Important...
ON “COMPANY” “CULTURE”
ON “COMPANY” “CULTURE”
“Move fast, break things.”*
ON “COMPANY” “CULTURE”
ON “COMPANY” “CULTURE”
“Context, not control.”
ON “COMPANY” “CULTURE”
ON “COMPANY” “CULTURE”
“A ‘Have Coffee’ culture”
Culture Is Not Important, but
Cultural Alignmentis critical
EXPERIMENTS, IN JUSTFOUR EASY STEPS!
EXPERIMENTS OVER THE LONG TERM
DETAILS, DETAILS
Target!=
Target Condition
“Let’s doThe DevOps!”
Retrospectives
Continuous Integration
Kanban
ContinuousDeliveryConfiguration
Management
DevelopersCarry the Pagers!
DockerDockerDocker
THE IMPORTANCE OF ATARGET CONDITION
(not your idea versus my idea about what we could do) and brings people’s efforts into alignment.
— Rother
[A] target condition... creates a challenge that depersonalizes a situation
#DevOpsDays @SoberBuildEng
#DevOpsDays @SoberBuildEng
CYNEFIN SIDEBAR
CYNEFIN SIDEBAR
Sample Experiments
MAN ON THE MOON
WEEKLY MEETING OF SUCK
TAKING TIME TOLOOK IN THE MIRROR
GAME ON!
PEBBLE THEORY OF CHANGE
PEBBLE THEORY OF CHANGE
Drain until you can see the rocks, i.e. obstacles; then remove those obstacles
PEBBLE THEORY OF CHANGE
Drain until you can see the rocks, i.e. obstacles; then remove those obstacles
Don’t target the rocks you “know” are there
PEBBLE THEORY OF CHANGE
Drain until you can see the rocks, i.e. obstacles; then remove those obstacles
Don’t target the rocks you “know” are there
Don’t dredge up the whole swamp
[T]he ability of your company to be competitive and survive lies not so much in solutions themselves, but in the capability of the people in your organization to understand a situation and develop solutions.
— Rother
Operability?
InOur
Software
Resilience
Microservices
Maintainability
InOur
Teams
Resilience
Independently Empowered
Teams/Actors
Sustainability
Resilience.
WHY?
Resilience.
WHY?
Code
Systems
Teams
Organizations People
J. Paul Reedsoberbuildengineer.com
@SoberBuildEng
www.release-approaches.comSimply Ship. Every Time.
Anonymous feedback:sayat.me/jpaulreed
Adoption of Agile & DevOps methodologies is a journey, and every person and organization’s journey is going to be different.
-J. Paul Reed
DevOps in Practice
J. Paul Reed
http://www.oreilly.com/webops-perf/free/devops-in-practice.csp