Post on 12-Apr-2017
ENTERPRISE DEVOPS PATTERNSEnterprise DevOps: Patterns of Organizational Structure & AdoptionApril 2016
1
We are a group of passionate individuals and a software solutions leader with technology at our core. Over time we’ve grown to incorporate an experience design practice and organizational
development capability to help our clients to build solutions loved by their customers, as well as helping to grow and exercise the organizational muscles that embed successful innovation.
Our mission is to better humanity through software and help drive the creation of a socially and economically just world. We bring together the most capable, driven
and passionate people. We call ourselves ‘ThoughtWorkers.’
2
INTRODUCTION TO THOUGHTWORKS
Over 20 years
33offices
14 countries
3000people
#1 in Agile CD
WHO AM I?
Lead Consultant, ThoughtWorks (Software Dev / DevOps)Currently, member of Platform Engineering Team (aka DevOps) for global financial institutionExperience with small, medium, large enterprisesEngineer, PO, PM, Sales Manager, CTO, COO, VP, PresidentDocker, Spring Cloud, MEAN Stack, CI/CD, 12-factor appsFirsthand DevOps experiences
X
CLOUDAUTOMATIONCI AZUREDOCKERPAAS CHEFGOCDJENKINS PUPPETANSIBLECD DEVOPSAWSCULTURES
3
DEVOPSWhat is DevOps?
WHAT IS DEVOPS?
Continuous Integration
Continuous Delivery
Test Automation
Configuration as Code
Infrastructure as Code
Platform as a Service
Infrastructure as a Service
It’s all about the Culture
It’s all about the tools
The Cloud!
Agile IT
It’s just a marketing strategy
4
WHAT IS DEVOPS?
A clipped compound of development and operations.A culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals, while automating the process of software delivery and infrastructure changes.DevOps aims at establishing a culture and environment where building, testing, and releasing software, can happen rapidly, frequently, and more reliably. - wikipedia
5
ORGANIZATIONAL STRUCTUREEnterprise DevOps: Patterns of Organizational Structure
6
ORGANIZATIONAL STRUCTURE PATTERNS
No DevOpsDevOps, formally known as IT/OpsStartup Grows UpSame Journey, Different PathsThe 3rd Wheel
Combined ForcesDrop-In DevOpsThe Ivory Tower
Delivery Teams7
DevOps
IT/Ops
QA
Dev
We got along this far without itMonolithic applications, legacy systemsDev and IT/Operations are separateThrow stuff over the wall to next teamOften involves other teams:RM, NOC, Performance,Security, ARB, Tools Admin
NO DEVOPS
88
IT/Ops
QADev
QADev
Rename IT/Ops to DevOpsRename SysAdmin to DevOps EngineerCommon recruitment trickCalling yourself a Rocket Scientist doesn't get you to the moonUsually an anti-pattern
DEVOPS, FORMALLY KNOWN AS IT/OPS
9
DevOps
IT/Ops
9
STARTUP GROWS UP
With success comes responsibilityInvestors, shareholders, Board of DirectorsIncreased regulations, security, auditable processes
Bootstrapped DevOps doesn't always scaleMature the team or rebuild the teamMix-in experienced resources
10
DevOps
SAME JOURNEY, DIFFERENT PATHS
Dev and IT/Ops both undertake DevOps journey, separatelyBrings both teams closer together if goals are complimentaryAnti-pattern if there is duplication of effort or conflicting goals
11
DevOpsQADev
IT/OpsQA
Dev
THE 3RD WHEEL
DevOps is a separate team from Dev and IT/Ops3 types: Combined Forces, Drop-In DevOps, The Ivory TowerTeam often serves Dev, but replies on IT/OpsReduces the IT/Ops burden from DevOwnership of team can be very challenging
12
DevOps
IT/Ops
QADev
QADev
Formed with resources from Dev and IT/OpsBreaks down walls between Dev and IT/OpsRotate team members to keep fresh and spread knowledgeCulture conflict: agile/proactive vs. support-driven/reactive
THE 3RD WHEEL: COMBINED FORCES
13
IT/Ops
QADev
QADev
You can't buy DevOps (well, yes, you can...)Build with support of experienced resources (i.e. ThoughtWorks)Set clear business objectives and transition planBlended team of DevOps consultants, Dev, and IT/OpsCommon in major transformations (i.e. moving to Cloud)
THE 3RD WHEEL: DROP-IN DEVOPS
14
DevOps IT/Ops
QADev
QADev
Started in isolationQuick start, focused effort, no competing goalsBest for certain types of organizations(highly political, strict budgeting, stalled tech)Anti-pattern if kept in isolation to long
Negative perception by peersNo knowledge transferDon't start without an exit strategy
THE 3RD WHEEL: THE IVORY TOWER
15
DevOps
Ideal in mature, Agile organizationsEmbed DevOps resources (often IT/Ops) on Dev teamsBlended teams own their application into ProductionShared resource, not fully committed to Dev teams
Don't underestimate IT/Opsresource requirementsHelps maintain IT/Ops skills and transfer of knowledge
DELIVERY TEAMS
16
IT/Ops
IT/Ops
QADev
IT/Ops
QADev
IT/Ops
QADev
ADOPTIONEnterprise DevOps: Patterns of Adoption
17
Eating the Elephant, One Bite at a Time
Strangler Pattern
To The Cloud!
DevOps Maturity Model Gap Analysis
DevOps Self-Service
ADOPTION PATTERNS
18
DevOps
EATING THE ELEPHANT, ONE BITE AT A TIME
19
Identify challenges, frustrations, pain pointsStart with small automation effortsFocus on continuous, incremental improvementsContinually chip away at wall between Dev & IT/OpRecognize and promote small successesQuantitatively measure impact on organization
STRANGLER PATTERN
Named for Strangler Application pattern (Martin Fowler TW) universal method of transformation
Choose new application, service, or business acquisition
Continue pattern until the original organization is totally transformed
Cloud-based transitions are often good targets for this pattern
20
From book, Continuous Delivery (Jez Humble TW)Perform Maturity Model Gap Analysis of organizationOr, choose to improve all categories for a single appChoose one category to improve across all apps (i.e. Testing)
Visualization Tool available on GitHub
DEVOPS MATURITY MODEL GAP ANALYSIS
21
Sign of very mature organization (‘unicorns’)
Dev can perform all tasks required to get their app into Production without intervention by IT/OPs
All processes are automated, documented, and readily available to Dev
Continuous Improvement
DEVOPS SELF-SERVICE
22
THANK YOUQuestions or suggestions:
gary.stafford@thoughtworks.comProgrammaticPonderings.com
@GaryStafford | LinkedIninspired by Pipeline Patterns