Top Banner
The Invisible, Intangible bottom of the DevOps Iceberg Agile India Conference Bangalore, Mar 2016 Vishu Hegde vishu@pm-powerconsulting.com
24

DevOps Iceberg agileindiaconf2016

Jan 11, 2017

Download

Software

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
  • The Invisible, Intangible

    bottom of the DevOps Iceberg

    Agile India Conference

    Bangalore, Mar 2016

    Vishu Hegde vishu@pm-powerconsulting.com

  • The DevOps cycle

    2 Image source : blogs.msdn.com

    People Process

    Technology

  • What moves the iceberg?

    Wind

    Currents

    10% Visible part

    90% Invisible part

    3

  • What makes DevOps successful?

    Hard aspects

    Soft aspects

    10% Visible part

    90% Invisible part

    Processes

    Ceremonies Artifacts

    Tools .

    . Values

    Principles Self-organizing teams

    Cross-functional collaboration

    Communication

    Shared-Vision, Motivation 4

  • DevOps Challenge : Horizontal Integration

    5

    CIO

    Head Apps

    Head I&O

    Biz

    Prod Mgmt

    Dev Test Infra Ops Prod Mgmt

    Cust

    Organizations are designed vertically, but work flows horizontally and Customers experience the organization horizontally

  • DevOps Critical Success Factors

    6

    CIO

    Head Apps

    Head I&O

    Biz

    Prod Mgmt

    Dev Test Infra Ops Prod Mgmt

    Cust Infra

    Scrum Kanban

    Self-organizing Teams

    Servant Leadership

    Cross-Functional Collaboration

    DevOps

  • CROSS-FUNCTIONAL COLLABORATION

    7

  • When there is no cross-functional collaboration

    8

    http://www.energizedwork.com/weblog/2007/11/theres-a-hole-in-your-side-of-the-boat

  • Challenge of Horizontal Integration: Cross-functional Alignment

    How to make everybody see the full elephant?

    9

  • Seeing the full elephant example

    10

  • Before ..

    After

    Green Whats going well Amber What needs to improve/change Yellow Action items

    11

  • Cross-Functional Collaboration: A Critical Success Factor for DevOps

    No single Function creates business value for Customer

    Business value is created only by the contribution of all the Functions

    12

    PM

    BA

    Ux

    Dev

    QA

    Infra

    Ops

    QA

    Dev

    BA

    DBA

    Infra

    Ops

    Goal Biz Value

    Cooperation to Collaboration

    Industrial-era thinking Knowledge-era thinking

  • Making of Cross-Functional Collaborating Teams Sandwich Approach

    Top-down

    Enablement to work in cross-functional teams

    Goal alignment across Functions (Strategy, Roadmaps, Priorities,)

    Common Protocols (Processes & Tools) across Functions

    Push factor

    Bottom-up

    Self-organizing cross-functional team

    Pull factor

    13

  • SELF-ORGANIZING TEAMS

    14

  • When teams are not self-organizing

    15

  • What makes self-organizing teams?

    Internal factors (team level):

    Self-managed individuals taking Responsibility

    Mutual Respect in team members, Trust

    Appreciating differences, diversity

    External factors (outside of team)

    Facilitative Leadership than command-control leadership

    Ask (70%) more than tell (30%)

    Empowerment of team

    Facilitating shared vision in the team

    Team rewards & recognitions

    16

  • Making of Self-organizing Teams

    Letting go by the manager(s) and Taking up by the team should happen synchronously

    17

    Command-control Self-organizing

    When teams become self-organizing, Managers need new job Coaching/mentoring, developing people

    Strategic organizational initiatives, improvements Enterprise Agility

  • SERVANT LEADERSHIP

    18

  • Servant Leadership Antithesis

    19

  • Leadership

    20

    Command-Control to

    Facilitative leadership

    Change in Governance & Measurements

    Structural changes

    Change in people practices

    Leadership: Can make or break self-organizing teams and cross-functional collaboration

  • DevOps Transforamtion

    10% Visible part

    90% Invisible part

    21

    Mindset

    Change

    Thinking

    Change

    Behavior

    Change

    Usage of practices,

    tools in right spirit

    Culture

    Change

  • 22

    Agile values and principles

    Transformation Dynamics

    Result pyramid - Tom Smith and Roger Connors

    In order to transform, break the cycle

    10% Visible part

    90% Invisible part

  • The invisible, intangible bottom of DevOps iceberg

    23

    Questions?

    Mindset > Toolset

    Self-organizing teams Cross-functional collaboration Servant Leadership

  • Thank You

    24