sd devops meet-up - exploring quadrants of devops maturity
Post on 15-Apr-2017
751 Views
Preview:
TRANSCRIPT
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
1© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
DevOps Connect FourExploring the 4 Quadrants of DevOps Maturity
Brian Dawson, CloudBees Inc@brianvdawsonbrianvdawson@cloudbees.com
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
2
• How big is your Development/IT organization?a) 1 – 50 pplb) 50 – 200 pplc) 200 – 500 ppld) Other or ”Do you know anybody hiring?"
• What is your role?a) Developerb) Operationsc) QAd) All of the abovee) Other
Poll (1/2)
2
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
3
• By show of hands do you practice?a) Continuous Integrationb) Continuous Deliveryc) DevOpsd) None of the above or GDD (Get ‘er Done Development)
• Do you use Jenkins?a) Yes, heavilyb) Starting to or have in the pastc) What is Jenkins?d) Using something else
Poll (2/2)
3
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
4
Hints & Tips
Simplify DevOps
message, communicate
widely & frequently
Define where you
are, identify where you are
going…Go!
Be pragmatic
, not
dogmatic
Leverage enabling tools & technology
to connect people & process across
boundaries (organizational, technical, etc.)
Respect the trinity, people,
process, tools (&
technology)
Continuously measure
& report
Incremental transformatio
n
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
5
Mission• Prologue: Approaching DevOps• Level Map: Simplified framing of an organization’s DevOps
maturity• Strategy Guide: Adoption patterns and cycles• Power Ups: Enabling tools and technology • Leave with new ideas and inspired
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
6
Player Background:• QA, Development, Development ManagementPlayer Strengths:• Software development optimization
– 1990so Graphics pipeline optimizationo Tools and middleware
– Early 2000’so OSS practices
– Late 2000’so Process consultingo CI, CD, and DevOps transformation practice
• Knowledge redistribution
Character Guide: About Me
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
7
DEVSECOPS
SEC
OPS
CONTINUOUS DELIVERY
MICROSERVICESCONTA
INERS
ASCIIDOC
GIT
JEN
KIN
S
JENKINS
GITHUB
GITLABNEXUS
SCRUMCHATOPS
DEV
OPS
CONTINUOUS IMPROVEMENT
MICRO
SERVICES
MICROSE
RVICES
MICROSERVICES
BDD
CLOUDPAAS
SCM
UNIT TEST
GIT
PERFORCE
CIR
CLE
CI
GITORIOUS
PERFECTO MOBILE
ELASTIC PROVISIONING
SCRUM
SCRUM
XPLEA
N
KANBAN
DEVOPS
DEVO
PS
DEVOPS
DEVSEC
OPS
RUGGED
DEVOPS
CO
NTI
NU
OU
S D
ELIV
ERY
CO
NTI
NU
OU
S D
ELIV
ERY
CONTINUOUS DEPLOYMENT
CONTINOUS TESTING
MICROSERVICES
TDD
VM
PAAS
PAAS
PAAS
TEST AUTOMATION
SUBVERSION
GIT
MERCURIAL
JENKINS
BLAZE METER
NEW RELIC
SCALE
LEAN
STOP THE LINE
DevOps Word Soup
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
8
CHATOPS
DEVOPSDE
VOPS
DEVOPS
DEV
OPS
DEVSECOPS
DEVSEC
OPS
SEC
OPS
RUGGED
DEVOPS
CONTINUOUS IMPROVEMENT
CONTINOUS INTEGRATION
CO
NTI
NU
OU
S D
ELIV
ERY
CO
NTI
NU
OU
S D
ELIV
ERY
CONTINUOUS DELIVERY
CONTINUOUS DEPLOYMENT
CONTINOUS TESTING
MICROSERVICESM
ICROSERVICES
MICROSE
RVICES
MICROSERVICES
MICROSERVICES
TDD
BDD
CONTAIN
ERS
VM
CLOUD
PAAS
PAAS
PAAS
PAAS
SCM
TEST AUTOMATION
UNIT TEST
ASCIIDOCSUBVERSION
GITGIT
GIT
MERCURIAL
PERFORCE
JEN
KIN
S
JENKINS
JENKINS
CIR
CLE
CI
GITHUB
GITLABGITORIOUS
PERFECTO MOBILE
BLAZE METER
NEW RELIC
NEXUSSCALE
ELASTIC PROVISIONING
SCRUM
SCRUM
SCRUM
XPLEAN
LEA
N
KANBANSTOP THE LINE
DevOps Word SoupOVERLOAD
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
9
SIMPLE CAN BE HARDER THAN COMPLEX: YOU HAVE TO WORK HARD TO GET YOUR THINKING
CLEAN TO MAKE IT SIMPLE. BUT IT’S WORTH IT IN THE END
BECAUSE ONCE YOU GET THERE, YOU CAN MOVE MOUNTAINS.
-Steve Jobs
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
10
WHERE ARE WE?
WHERE ARE WE GOING? HOW DO WE
GET THERE?
SIMPLIFY
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
11
WHERE ARE WE?
WHERE ARE WE GOING? HOW DO WE
GET THERE?
DevOps
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
12
WHERE ARE WE?
WHERE ARE WE GOING? HOW DO WE
GET THERE?
DevOps (according to me ;^)
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
1313© 2015 SOASTA Inc.- All rights reserved.
Fundamentally we are talking about...
13
DeliveringBetter
SoftwareFaster
Concept-to-Customer
High Quality• Performance• Feature• Function
RapidlyEliminating WasteMarket Innovation
High Value
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
14
How Do You Deliver Better Software Faster?
14
ProdDev
RapidlyRepeatedly
Reliably
ProdDev
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
15
How Do You Deliver Better Software Faster?
15
RapidlyRepeatedly
Reliably
ProdDev
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
16
How Do You Deliver Better Software Faster?
16
“DevOps is a software development method that stresses communication, collaboration and
integration between software developers and information
technology (IT) professionals.”[1]
[1] http://en.wikipedia.org/wiki/DevOps
DevOps
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
17
How Do You Deliver Better Software Faster?
17
“DevOps is a software development method that stresses communication, collaboration and
integration between software developers and information
technology (IT) professionals.”[1]
[1] http://en.wikipedia.org/wiki/DevOps
DevOps
But You Can’t “Do” DevOps. DevOps an outcome.
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
18
Continuous delivery (CD) is…
18
• …the practice of automatically and continuously building, testing and deploying software to ensure it CAN be released at any time.
• …an extension of continuous integration (CI) and enables DevOps
• …NOT Continuous Deployment
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
19
Continuous delivery (CD) is…
19
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
20
X-Axis: SDLC Phases
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report
Agile Upstream
33%
Agile Downstream
13%
Define Plan Code Build Integrate Test Release Deploy Operate
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
21
Y-Axis: Levels of adoption
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report
Agile Upstream 33%
Agile Downstream 13%
EnterpriseAgile Upstream 22%
EnterpriseDevOps 10%
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
22
Y-Axis: Levels of adoption
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report
Agile Upstream 33%
Agile Downstream 13%
EnterpriseAgile Upstream 22%
EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Gain competitive advantage
• Innovate faster
• Respond to market
• Increased productivity
• Employee satisfaction and retention
$$
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
23
The Chasms
Source: February 5, 2014, “How Can You Scale Your Agile Adoption?” Forrester report
Agile Upstream
Agile Downstream
EnterpriseAgile Upstream
EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
EnterpriseDevOps
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
24
The Quadrants
Quadrant 1:Team-level
Agile
Quadrant 2:Team-level
CD
Quadrant 3:Enterprise
Agile
Quadrant 4:EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
EnterpriseDevOps
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
25
The Characteristics EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Enterprise support for cloud with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
• Business and customers aligned with iterative agile definition and delivery
• Tools integration to common platform supporting reporting and metrics, security, governance and traceability
• Culture of learning and innovation
• Standard enterprise-wide iterative/agile development practices
• Business aligned with agile specification• Common PM and dev process• Team-level tools and delivery process
• Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
• Team CI extended to CD• Team-level tools integration w/delivery tools• Ops alignment with PM and dev process as team specific
“one-offs”
• Team(s) adopt iterative/agile development practices• Development team(s) independently leverage CI• Team-level tools integration• Team specific PM and dev process• Water-Scrum-fall approach
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
26
Quadrant 1: Team-Level Agile EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
• Business and customers aligned with iterative agile definition and delivery
• Tools integration to common platform supporting reporting and metrics, security, governance, and traceability
• Culture of learning and innovation
• Standard enterprise-wide iterative/Agile development practices
• Business aligned with agile specification• Common PM and Dev process• Team-level tools and delivery process
• Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
• Team CI extended to CD• Team-level tools integration w/Delivery tools• Ops alignment with PM and Dev process as team specific
“one-off”
• Team(s) adopt iterative/Agile development practices• Development team(s) independently leverage CI• Team-level tools integration• Team specific PM and Dev process• Water-scrum-fall approach
Team(s) adopt iterative/agile development practices
Development team(s) independently leverage CI
Team-level tools integration
Team specific PM and dev processes
Water-Scrum-fall approach
+
-
+
-
-
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
27
Quadrant 2: Team-Level CD EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
• Business and customers aligned with iterative agile definition and delivery
• Tools integration to common platform supporting reporting and metrics, security, governance, and traceability
• Culture of learning and innovation
• Standard enterprise-wide iterative/Agile development practices
• Business aligned with agile specification• Common PM and Dev process• Team-level tools and delivery process
• Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
• Team CI extended to CD• Team-level tools integration w/Delivery tools• Ops alignment with PM and Dev process as team specific
“one-off”
• Team(s) adopt iterative/Agile development practices• Development team(s) independently leverage CI• Team-level tools integration• Team specific PM and Dev process• Water-scrum-fall approach
Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
Team CI extended to CD
Team-level tools integration w/delivery tools
Ops alignment with PM and dev process as team specific “one-offs”
+
+
-
+
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
28
Quadrant 3: Enterprise Agile CD EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
• Business and customers aligned with iterative agile definition and delivery
• Tools integration to common platform supporting reporting and metrics, security, governance, and traceability
• Culture of learning and innovation
• Standard enterprise-wide iterative/Agile development practices
• Business aligned with agile specification• Common PM and Dev process• Team-level tools and delivery process
• Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
• Team CI extended to CD• Team-level tools integration w/Delivery tools• Ops alignment with PM and Dev process as team specific
“one-off”
• Team(s) adopt iterative/Agile development practices• Development team(s) independently leverage CI• Team-level tools integration• Team specific PM and Dev process• Water-scrum-fall approach
Standard enterprise-wide iterative/agile development practices
Business aligned with agile specification
Common PM and dev process
Team-level tools delivery process
Team-level tools integration
+
+
-
+
-
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
29
Quadrant 4: Enterprise DevOps EnterpriseDevOps
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build Integrate Test Release Deploy Operate
• Enterprise support for “cloud” with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
• Business and customers aligned with iterative agile definition and delivery
• Tools integration to common platform supporting reporting and metrics, security, governance, and traceability
• Culture of learning and innovation
• Standard enterprise-wide iterative/Agile development practices
• Business aligned with agile specification• Common PM and Dev process• Team-level tools and delivery process
• Specific applications supported by automated test, dynamically provision environments, immutable infrastructure or IaC…
• Team CI extended to CD• Team-level tools integration w/Delivery tools• Ops alignment with PM and Dev process as team specific
“one-off”
• Team(s) adopt iterative/Agile development practices• Development team(s) independently leverage CI• Team-level tools integration• Team specific PM and Dev process• Water-scrum-fall approach
Enterprise support for cloud with standard tools and process for automated test, dynamically provisioned environments, immutable infrastructure, IaC…
Business and customers aligned with iterative agile definition and delivery
Tools integration to common platform supporting reporting and metrics, security, governance and traceability
Culture of learning and innovation
+
+
+
+
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
30
CI-> Agile -> Ent. Agile -> Ent. DevOps1. Team(s) start with CI
2. Team(s) adopt Scrum/agile planning and project management
3. Organization implements Scrum/agile definition planning and project management
4. Organization aligns on DevOps strategy with teams using common CI/CD process and tools
Adoption Pattern #1:
Team
Wor
kgro
upE
nter
pris
e
Define Plan Code Build/CI Test Release/Deploy Operate
EnterpriseDevOps
2
3 4
1
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
31
Adoption Pattern #2Team Agile -> Ent. Agile -> Ent. DevOps1. Team(s) adopt Scrum/agile planning
and project management 2. Organization implements
Scrum/agile definition, planning and project management
3. Organization aligns on DevOps strategy with teams using common CI/CD process and tools
Team
Wor
kgro
upE
nter
pris
e
EnterpriseDevOps
1
2 3
Define Plan Code Build/CI Test Release/Deploy Operate
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
32
Adoption Pattern #3Team Agile -> Team CD -> Ent. Agile -> DevOps1. Team(s) adopt Scrum/agile project
planning and management2. Team(s) extend CI to Continuous
Delivery
3. Organization implements Scrum/agile
4. Organization aligns on DevOps strategy with teams using common CI/CD process and tools
Team
Wor
kgro
upE
nter
pris
e
EnterpriseDevOps
1
3 4
2
Define Plan Code Build/CI Test Release/Deploy Operate
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
33
Adoption Cycles: Bottom-UpTe
amW
orkg
roup
Exe
cutiv
e
Time
1
64
3
VisibilityAdoption
Team Level
Initiation
Executive Support
Team Successes
Workgroup Success
Scale Across Workgroups
Executive Support2 5
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
34
Adoption Cycles: Top-DownTe
amW
orkg
roup
Exe
cutiv
e
Time
VisibilityAdoption
Executive Initiative
Team Successes
Workgroup Success
Scale Across Workgroups
1
2
6
4
3
WorkgroupInitiative
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
35
Tools & Technologies enable “crossing the chasm”
Normalized Language and
practice agnostic
Not Dev or Ops specific
Distributed
Rich Integration
Support Tools as
microservices Modular
Automated Repeatability Reportability Flexibility
Increase Confidence
In Downstream Deliverables
Support supply-chain
Traceability Immutability Measure and
report
Scale To Enterprise
Cross-domain visibility metrics
Security and governance
Supported
35
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
36
Click to add titleTe
amW
orkg
roup
Exe
cutiv
e
CloudBees
Jenkins OSS
Rally
Jira
Misc Point Solutions
ChefPuppet
HP OO
SVNGit
NolioMiscellaneous ALM Solutions
HP ALI
TestLink
Helpdesk
Selenium
PPM
XL Release
Nexus
ChatLDAP
APM
Docker
Define Plan Code Build Integrate Test Release Deploy Operate
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
37
Team
Wor
kgro
upE
xecu
tive
Define Plan Code Build Integrate Test Release Deploy Operate
Mis
c P
oint
S
olut
ions
Jira
, Te
amFo
rge.
.
Ecl
ipse
, In
telli
J, S
VN
, G
it
Jenk
ins,
M
ake,
M
aven
..
Jenk
ins,
CI
Sol
utio
ns
Sel
eniu
m,
Test
Link
…
XL
Rel
ease
, H
P O
O…
XL
Rel
ease
, H
P O
O…
Cha
t, Lo
ggin
g,
Mon
itorin
g
LDAP, SAML
Product Portfolio
Application Performance Mgt
Service Desk
Click to add title
© 2
016
Clou
dBee
s, In
c. A
ll Ri
ghts
Re
serv
ed
38
Team
Wor
kgro
upE
xecu
tive
Define Plan Code Build Integrate Test Release Deploy Operate
Mis
c P
oint
S
olut
ions
JIR
A,
Team
Forg
e..
Ecl
ipse
, In
telli
J, S
VN
, G
it
Jenk
ins,
M
ake,
M
aven
..
Jenk
ins,
CI
Sol
utio
ns
Sel
eniu
m,
Test
Link
…
XL
Rel
ease
, H
P O
O…
XL
Rel
ease
, H
P O
O…
Cha
t, Lo
ggin
g,
Mon
itorin
g
Click to add title
Integrate and Automate
Security and Access Controls
Reporting and Analytics
Supply Chain Managment
Shared Infrastructure – Containers or IaC
EnterpriseDevOps
top related