devops beyond the tools
TRANSCRIPT
Johann, Mayflower
We do agile stuff, too.
(a lot, like no budgets, open books, no job titles, team selected roles,
reverse accountability, peer feedback, slacktime, (mostly) open salaries,
peer salaries, sociocracy, stuff)
Accenture, 2014
No longer can applications be ‚built‘ as one distinctive activity and ‚maintained‘ as another. Engineering Innovations such as Agile and DevOps enable software to be continuously delivered and evolve as business needs change.
Cap Gemini, 2014
Development to Operations (DevOps) implementations will increase significantly during 2015-2016.
Gartner Group, 2015
Gartner Says By 2016, DevOps Will Evolve From a Niche to a Mainstream Strategy Employed by 25 Percent of Global 2000 Organizations.
Puppet Labs, 2015
It’s their use of DevOps practices that sets these top performers apart from the pack.
How often do you deploy?
1
2
3
4
5
>= 1 time daily
multiple times a week
at the end of each sprint
once a month?
every 3/6 months
New features into production
1
2
3
4
5
> 1 per day
>2 per week
7-12 each sprint
1-5 per month
some each year
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
CEO
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
Specialization Effective Control Efficiency Economy Expansion
CEO
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
Strategy Company Goals Department Goals Individual Goals & KPIs
CEO
DevOps … deals with silo effects between
• Requirements engineering • Development • Quality • Deployment • Maintenance • Operations
Vice President Product
CEO
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
Product Development
Shared Topics
• requirements • business metrics • release pipeline • technical resources • architecture
Shared Responsibility
• Responsibility for the product, not department objectives
• documentation & ticketing is a tool, not a contract
• no handovers
Shared Goals
• focus on • product • overall process
• shared metrics • user metrics • platform metrics • quality metrics
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
CEO
Team
You built it, you run it.
Autonomous Cross- Functional Teams
• all skills needed are part of the team • no external dependencies • authority for decisions • no handover needed
Inverse Conway Maneuver
„Product Design builds the right product“ „Dev builds the product the right way.“ „Ops delivers the right support.“
Respect & Trust (a.k.a. the hard part)
DevOpsCultureDirect cooperation
Autonomous Teams
Shared Responsability
Shared Goals
Automation
Trust & Respect
Contradictions
Organisation DevOps
individual accountability
shared accountability
department goals & objectives
shared objectives
individual objectives & bonuses
shared objectives
local efficiency global efficiency
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
CEO
Vice President DevOps
Database DevOps
Enterprise DevOps
Junior DevOps
„DevOps is a new department focussing on infrastructure & deployment automation“
CEO
Devops
Vice President Development
Software Developer
Frontend Developer
DevOps Engineer
CEO
Development- only DevOps
Puppet Vagrant
SaltStack Testing & CI … but not in Production
Product Developer
Software Development
Quality Assurance
Operations
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
SLES based SLES based
Vagrant BoxesQA uses Ubuntu
Product Development
WTF WTF
DevOps vs ManagementAutomation is expensive
Incompatible with functional orgs
Incompatible with MbO
Incompatible with command & control
Cooperation is harder than it seems
No more „stupid sales droids“ No more „stupid frontend devs“ No more „stupid customers“ No more „stupid management“ No more „stupid features“ No more „my department is great, but (other department) is not“
Vice President Product
Vice President Development
Vice President Quality
Vice President Maintenance
Product Developer
Software Developer
Quality Assurance
Operator
Product OwnerFrontend
DeveloperTester
NetSecConsultant
Product Designer
BackendDeveloper
Test Infrastructure
Performance Consultant
CEO
MicroService-Team
Inverse Conway Maneuver FTW?!
Inverse Conway Maneuver FTW?!
Corporate Culture does not change fast.
Functional
Org DevOps
True for 20 years
True for 6 months
Loops
2 Amplify Feedback
Product Development
Software Development
Deployment
Business Analytics
Management
2 Amplify Feedback
Product Development
Software Development
Deployment
Business Analytics
Management 1 months
3 months
1 week
1 Sprint1 day
143 days!
2 Amplify Feedback
Product Development
Software Development
Deployment
Business Analytics
1 week
1 day
1 sprint1 day
23 days
Management
3Ways of DevOpsSystems Thinking
Amplify Feedback Loops Culture of Continual Experientation
DevOps culture is the delayed outcome
3Ways of DevOpsEnable Your teams to
understand the business , cooperate and learn together.
It’s not about change management
DevOpsCultureDirect cooperation
Autonomous Teams
Shared Responsability
Shared Goals
Automation
Trust & Respect