Mapping and Measuring Your Journey to DevOps

Download Mapping and Measuring Your Journey to DevOps

Post on 13-Feb-2017

215 views

Category:

Documents

0 download

TRANSCRIPT

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    1

    2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    Mapping and Measuring Your Journey to DevOps

    Brian Dawson, CloudBees DevOps Evangelist and Jenkins PMM @brianvdawson bdawson@cloudbees.com

    DevOps Quadrants Webinar Series - Part #2:

    Tom McGonagle, CloudBees Sr. DevOps Consultant @mcgonagle tmcgonagle@cloudbees.com

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    2

    Review Quadrants Model

    Measuring and Mapping Example

    Discover Define Map

    Transformation Strategies

    Next in the Series

    Gain inspiration on how to drive your DevOps transformation

    Agenda

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    3

    Introduction Background:

    QA, Development, Sys Admin, Development Management, etc Software development optimization

    1990s o Graphics pipeline optimization o Tools and middleware

    Early 2000s o OSS practices

    Late 2000s o Process consulting o CI, CD, and DevOps transformation practice

    Knowledge redistribution = IT Socialist

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    4

    What do you consider your role to be?

    Poll Question #1

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    5 5

    Review of the DevOps Maturity

    Quadrants

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    6

    Simplified model for assessing, and discussing DevOps transformations

    Derived from and applied in real-world DevOps transformations

    Flexible vs rigid, allows for subjective definition of maturity

    Extensible as method of driving, monitoring and measuring transformation

    The Quadrants Model

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    7

    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

    Res

    erve

    d

    8

    Y-Axis: Levels of adoption

    Source: February 5, 2014, How Can You Scale Your Agile Adoption? Forrester report

    Agile Upstream 33% Agile Downstream 13%

    Enterprise Agile Upstream 22% Enterprise DevOps 10%

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    9

    The Destination

    Agile Upstream 33% Agile Downstream 13%

    Enterprise Agile Upstream 22%

    Enterprise DevOps

    Innovate faster

    Respond to market

    Gain competitive advantage

    Increased productivity

    Employee satisfaction and retention

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    10

    The Chasms

    Upstream Downstream

    People & Culture

    Process & Practices

    Tools & Technology

    , , , ,

    ,,

    , ,

    , . ,

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    11

    The Quadrants

    Quadrant 1: Team-level

    Agile

    Quadrant 2: Team-level

    CD

    Quadrant 3: Enterprise

    Agile

    Quadrant 4: Enterprise DevOps

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    12

    Which quadrant are you in?

    Poll Question #2

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    13

    Poll Results

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    14 14

    Measuring and Mapping Example

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    15

    Large accounting platform, 65% and growing SaaS business Practiced Scrum in Development (2 week sprints) Practiced waterfall in Operations and QA teams 6 month releases with monthly maintenance releases Virtual machine farm, gated by Operations and requested via

    help desk

    Development, QA, and Operations have dedicated non-integrated tools

    Excessive firefighting and burnout in Operations High number of Severity 1 production issues

    Example: Financial Services Company

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    16

    Discover: Determine current state and maturity

    Define: Establish objectives

    Map: Journey through the quadrants

    Cross chasms, connect quadrants, continuously

    improve

    Order of Operations WHERE ARE

    WE?

    WHERE ARE WE GOING?

    HOW DO WE GET THERE?

    Involve and align key stakeholders at start of transformation and communicate with them frequently.

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    17

    Discover: Q1 Team-Level Agile

    Do one or more team practice agile? Yes

    Do teams practice Continuous Integration? No

    Are end-user needs defined and planned using agile? Partially, use water-scrum-fall

    Tea

    m

    Wor

    kgro

    up

    Ente

    rpris

    e

    Define Plan Code Build Integrate Test Release Deploy Operate

    WHERE ARE WE?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    18

    Discover: Q2 Team-Level CD

    Are one or more teams able to dynamically provision prod-like environments? Yes

    Are environments and infrastructure versioned and/or code? No

    Is operations involved in the planning process? No

    Are development, delivery and deployment tools integrated? No

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

    WHERE ARE WE?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    19

    Discover: Q3 Enterprise Agile

    Do all teams follow shared agile practices? Yes

    Do teams use common integrated definition, planning and development tools? Yes

    Is the business aligned with agile planning? No

    Can you measure and report on development status across projects? No

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

    WHERE ARE WE?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    20

    Discover: Q4 Enterprise DevOps

    Does the organization provide elastic infrastructure as a service? No

    Does the organization provide CI/CD as a Service? No

    Are the business and customers aligned with agile and continuous delivery of changes? No

    Is there a culture of collaboration, learning and experiementation? No

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

    WHERE ARE WE?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    21

    Discover: Current State by Quadrant Maturity

    Quadrant 1: Maturity = High

    Quadrant 2: Maturity = Low

    Quadrant 3: Maturity = Med

    Quadrant 4: Maturity = Very Low

    YOU ARE HERE

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

    Modern DevOps practices can be applied to Hybrid or Bi-modal organizations which have a mix of legacy systems of records and modern systems of innovation. i.e Accounting vs Mobile.

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    22

    Long term/Strategic:

    All applications released every 2 weeks

    Reduce Severity 1 defects by 100%

    Reduce all defects by >50%

    Reduce operations and developer overtime by 80%

    Reduce IT costs

    Increase responsiveness to customer

    Define: Establish Objectives WHERE ARE WE GOING?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    23

    Define: Establish Objectives

    Short term/Tactical:

    Establish shared Continuous Delivery as a Service platform

    Implement automated testing for all applications

    Form cross-functional teams

    Foster collaborative culture

    WHERE ARE WE GOING?

    Objectives should be based on Shared Priorities, those which can be translated to benefits to all stakeholders, to encourage buy-in

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    24

    Map: Journey through Quadrants Quadrant 1 to Quadrant 2

    Establish team-level CD Shared platform, dynamic provisioning, automated testing

    Form cross-functional team Open communication, shared knowledge

    Quadrant 1:Maturity = High

    Quadrant 2:Maturity = High

    Quadrant 3:Maturity = Med

    Quadrant 4:Maturity = Very Low

    Team

    Wor

    kgro

    upEn

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

    HOW DO WE GET THERE?

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    25

    Map: Journey through Quadrants Quadrant 2 to 3* and 4

    Establish shared project management and development tools and process Have common, connecting process parts but support deviation outside of those

    Adopt enterprise infrastructure and CD as a Service strategy Connect common development tools to enterprise solution

    HOW DO WE GET THERE?

    Quadrant 1:Maturity = High

    Quadrant 2:Maturity = High

    Quadrant 3:Maturity = Med

    Quadrant 4:Maturity = Med

    Team

    Wor

    kgro

    upEn

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    26

    Map: Journey through Quadrants Quadrant 2 to 3 and 4*

    Build DevOps Center of Excellence based on lessons from red team Central, cross-functional team. Service oriented but with authority

    Onboard new teams and extend common tools and processes Continuously, pragmatically refine to balance team needs with enterprise needs

    HOW DO WE GET THERE?

    Quadrant 1:Maturity = High

    Quadrant 2:Maturity = High

    Quadrant 3:Maturity = Med

    Quadrant 4:Maturity = Med

    Team

    Wor

    kgro

    upEn

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    27

    Where did/would you start with your DevOps transformation?:

    1. Culture

    2. Process

    3. Tools and Technology

    4. None of the Above

    Poll Question #3

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    28

    Identify pilot project

    Form cross-functional red team

    Adopt unifying technologies

    Establish plan with measurable KPIs and milestones

    Go!

    Measure, document report, refine

    Transformation Strategies

    A red team is a group that explicitly challenges a company's strategy, products, and preconceived notions is motivated by innovation ...and can lead other teams

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    29

    Part 1: Introduction to the 4 Quadrants of DevOps Maturity

    May 4th, 2016 - Watch at: https://goo.gl/9KsAvt

    Part 2: Mapping and Measuring Your Journey to DevOps

    Today - Recording to follow

    Part 3: Crossing the DevOps Chasms with Tools & Technology

    July 7th, 2016 Register at: https://goo.gl/mk7y4r

    Next in the Series

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    30 30

    Questions?

    DM: @brianvdawson Email: bdawson@cloudbees.com Or: info@cloudbees.com

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    31

    2

    015

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    31

    Thank You

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    32

    2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    33

    Quadrant 1: Team-Level Agile

    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 agile development practices

    Development team(s) independently leverage CI

    Team-level tools integration

    Team specific project mgmt. and dev. processes

    Water-Scrum-Fall approach

    +

    -

    +

    -

    -

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    34

    Quadrant 2: Team-Level CD

    Standard enterprise-wide iterative/Agile development practices

    Business aligned with agile specification Common PM and Dev process Team-level tools and delivery process

    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

    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 provisioned environments, configuration mgmt, containers

    Team CI extended to CD

    Team-level dev. tools integration to delivery tools

    Ops alignment with project mgmt. and dev. process as team specific one-offs

    +

    +

    -

    +

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate

  • 2

    016

    Clou

    dBee

    s, In

    c. A

    ll Ri

    ghts

    Res

    erve

    d

    35

    Quadrant 3: Enterprise Agile

    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 agile development practices

    Business aligned with agile specification

    Common project mgmt. and dev. process

    Team-level dev tools supporting delivery process

    Team-level tools integration

    +

    +

    -

    +

    -

    Team

    W

    orkg

    roup

    En

    terp

    rise

    Define Plan Code Build Integrate Test Release Deploy Operate