achieving continuous visibility across the devops lifecycle

38
Achieving Continuous Visibility across the DevOps Lifecycle MIK KERSTEN | Founder & CEO, Tasktop @mik_kersten CARMEN DEARDO | Nationwide Technology Director @carmendeardo SESSION 3268

Upload: tasktop

Post on 08-Jan-2017

538 views

Category:

Software


6 download

TRANSCRIPT

Page 1: Achieving Continuous Visibility Across the DevOps Lifecycle

Achieving Continuous Visibility across the DevOps Lifecycle

MIK KERSTEN | Founder & CEO, Tasktop@mik_kersten

CARMEN DEARDO | Nationwide Technology Director@carmendeardo

SESSION 3268

Page 2: Achieving Continuous Visibility Across the DevOps Lifecycle

AGILE OPTIMIZES THE MIDDLE OF THE VALUE STREAM

2

Wait states due to starvation of prioritized work flow into backlogs

Wait states due to contention for downstream environments and

manual processes

Agile DDT

Deploy & Operate Steer Develop & Test

Water-SCRUM-Fall

SPEED

TIME

Teams waiting for workdue to “discrete”

planning processes

Delivery slowed downby manual and high ceremony processes

High Accelerationduring Design, Develop and

Acceptance Testing

0

Page 3: Achieving Continuous Visibility Across the DevOps Lifecycle

FOUNDATIONAL MODEL

3

DEVOPSBusiness Enabling Responsiveness

Reduced Lead Time for Changes

Monitor Everything

Continuous Delivery

Automated Infrastructure

Continuous Integration

Automated Testing

Version Control Everything

PRACTICES

High Trust

Innovative

Performance Oriented

Empowered Associates

Reduce Variation

High Cooperation

CULTUREContinuous Flow & Visibility

Lean & Agile Principles Product Centric

System Flow Amplify Feedback Loops Continuous Experimentation

Page 4: Achieving Continuous Visibility Across the DevOps Lifecycle

THE HIDDEN FACTORY

4

Project  Planning  View

Development  View Release  View    Bus  Portfolio   View

Project  Metrics   Path  to  Production

Business  Needs Production  Implementations

Release  Metrics  

Page 5: Achieving Continuous Visibility Across the DevOps Lifecycle

CURRENT STATE

5

Release  Planning Release  Management(Development  &  Test)

DeploymentAutomation

Custom   BSA  RP  toolsCustom   BSA  Rls  

Planning  tools

Custom  Business  Release  

Planning  tools

Project  &  PortfolioManagement

Custom  Release  

Management  Tooling

Custom  Release  Management  

Tooling

Code  Moves

Test  &  Production  EnvsReports  &  

notifications

Other  DeployTools

Build  Process  

Java.NET

Mobile

• Clarity Used for Project Management and Work Requests• Custom Release Planning Tools and spreadsheets• Tools not Integrated – no Enterprise views• Manual interactions which slow down the process• No automated deployment policies• RTC used for Agile Team Management and not integrated• Disparate views with no model of the delivery work flow or path to production

RTCProject  Plans  &  Work  Requests

Page 6: Achieving Continuous Visibility Across the DevOps Lifecycle

THE HIDDEN FACTORY

6

Project  Planning  View

Release  View    Bus  Portfolio   View

Project  Metrics   Path  to  Production

Business  Needs Production  Implementations

Release  Metrics  

Development  View

Page 7: Achieving Continuous Visibility Across the DevOps Lifecycle

EXPOSING THE FACTORY WITH DEVOPS

7

Business Needs Production Implementations

DEVOPS

Provide  Visibility  Across  the  End  to  End  Delivery  Value  Chain  to  Expose  the  Value  Stream  and  Improve  Delivery

Page 8: Achieving Continuous Visibility Across the DevOps Lifecycle

DELIVERY VALUE STREAM: HIGH LEVEL

8

BUSINESS

WORK REQUEST PROCESS

DEMAND MANAGMENT

RELEASE PLANNING

DESIGN / DEVELOP

QUALITY CERTIFIED DEPLOY

INVENTORY INITIATIVE/ DC BUILDS

Page 9: Achieving Continuous Visibility Across the DevOps Lifecycle

VALUE STREAM MAP

9

BUILDS

DESIGN / DEVELOP

QUALITY CERTIFIED DEPLOY

IDENTIFY ACSCHEDULE

INTO RELEASE

END

RELEASE PLANNING

YES

NOOR

CREATE PLAN

EXECUTE PLAN

REVIEW(PDCA)

DEPLOY TO TEST

ENVIRONMENT

EXECUTE TEST

APPROVED?

CERTIFIED YES ALL CERTS

DONE

NODEFECTS

YES

NO YES

NO

C N/C C CBUSINESS

Page 10: Achieving Continuous Visibility Across the DevOps Lifecycle

AGILE PROVIDES A WINDOW INTO THE FACTORY

10

Standardize “Work” input (e.g. Business Value, Defects, Operations)

Provide impact analysis, Dashboard views and multi-application continuous delivery

Provide direct, automated control & traceability over deployment activity.

UCR(UrbanCode

Release)

UCD(UrbanCode

Deploy)

RTC(Rational

Team Concert)

Release Dashboard

Release Scheduling

Deploy

Page 11: Achieving Continuous Visibility Across the DevOps Lifecycle

BUSINESS WORK SOURCE

OPERATIONALWORK SOURCE

DEFECTS

BUSINESS INITIATIVE A

BUSINESS INITIATIVE B

AC

AC AC

OPERATIONAL INITIATIVE B

OC OC

SYSTEM RELEASE

AC

AC

OC

AC

AC

OC

SCM CIIT / ST /PT / UAT

CODE STATION

BUSINESS VALUE

OPERATIONS

MONITORING & FEEDBACK

TEST RESULTS / PT / SECURITY

READY FOR PRODUCTIONDEFECT

CONTINUOUS DELIVERY WORKFLOW

Page 12: Achieving Continuous Visibility Across the DevOps Lifecycle

WHY DOES REALITY LOOKING SO DIFFERENT?

Best-­‐of-­‐breed  DevOps  &  Agile  

tool  chains  are  the  norm

Page 13: Achieving Continuous Visibility Across the DevOps Lifecycle

Developers Designers

DIFFERENT POINTS OF VIEW ON SOFTWARE DELIVERY

Developerssee

Designerssee

Managerssee

Managers

Page 14: Achieving Continuous Visibility Across the DevOps Lifecycle

HETEROGENEITY ACROSS LINES OF BUINSESS

Page 15: Achieving Continuous Visibility Across the DevOps Lifecycle

RESULT: LOCAL OPTIMIZATOINS & MANUAL PROCESSES

15

Page 16: Achieving Continuous Visibility Across the DevOps Lifecycle

WE NEED A NEW KIND OF INFRASTRUCTURE

16

DEVOPSBusiness Enabling Responsiveness

Reduced Lead Time for Changes

Monitor Everything

Continuous Delivery

Automated Infrastructure

Continuous Integration

Automated Testing

Version Control Everything

PRACTICES

High Trust

Innovative

Performance Oriented

Empowered Associates

Reduce Variation

High Cooperation

CULTUREContinuous Flow & Visibility

Lean & Agile Principles Product Centric

System Flow Amplify Feedback Loops Continuous Experimentation

Page 17: Achieving Continuous Visibility Across the DevOps Lifecycle

DevOps Integration

Agile ITILWaterfall / SAFe

Project Requirement User Story Defect Ticket Alert

Continuous Integration Continuous Delivery

Executives Business Analysts Project Managers Developers IT Operations Support Desk

INTEGRATION INFRASTUCTURE FOR DEVOPS

Page 18: Achieving Continuous Visibility Across the DevOps Lifecycle

PATTERN LANGUAGES

18

1977 1998

Page 19: Achieving Continuous Visibility Across the DevOps Lifecycle

PATTERN LANGAUGE FOR DEVOPS & AGILE INTEGRATION

19

Integration Infrastructure

Integration Patterns

Process Frameworks

Value Stream

Lifecycle Tools

Page 20: Achieving Continuous Visibility Across the DevOps Lifecycle

PROCESS FRAMEWORKS: PMBOK + SAFe + DEVOPS + ITIL

20

Page 21: Achieving Continuous Visibility Across the DevOps Lifecycle

Pattern Applies to ExampleDefect  Unification

• Agile  development• Waterfall development• Separate  Dev  &  QA  teams  &  tools

Requirements  Traceability

• Agile  development• Traditional Requirements  Management• Traditional  Quality  Management• Dev  and  Agile  PM  using  different  tools

Agile  Plan  Orchestration

• Traditional or  Agile  development• Separate  PMO  organization• Separate  Agile  Dev  and  PPM  tools

Service  Desk  Escalation

• DevOps  deployment• Agile  or  waterfall  development• Support  organization  separate  from  the  

development  teams

Supply Chain  Integration

• In-­‐house  requirements  and    QA  mgmt• Development  outsourcing• QA  outsourcing

Dev QA

BAAgile  PM

QA

QA  ..ALM

PMOAgile  2

ITSMDev

QA

ITSMDefect Ticket

DevEpic

QA  1

Dev  ..

Dev  1

Agile  1

Rqrmnt Defect

INTEGRATION PATTERNS

Page 22: Achieving Continuous Visibility Across the DevOps Lifecycle

AGILE INTEGRATION PATTERNS

22

CA Clarity

Atlassian JIRA

HP ALM

IBM DNG

MicrosoftTFS

SLI Pattern #1: Executive Planning to Project Definition

SLI Pattern #3: Supply Chain Connections SLI Pattern #2: Project Definition to Execution

SLI Pattern #4: Requirements to Test Visibility SLI Pattern #5: Defect UnificationSLI

Pat

tern

#6:

Res

ourc

e A

lloca

tion

IBM RTC

ServiceNow

Page 23: Achieving Continuous Visibility Across the DevOps Lifecycle

Investment Theme

Business Epics

Program  Prism Team  Prism

Features

SLI  Pattern  #2:  Resource  Allocation

Features

Business Epics

Work Logs

Tasks

User Stories

Portfolio  Prism

Timesheets

Developer,  Project  ManagerWork Logs

CC

FROM PMO TO DEVOPS

Page 24: Achieving Continuous Visibility Across the DevOps Lifecycle

INTEGRATION PATTERNS

• Project  Portfolio  Management– Time  tracking  propagation– Agile  plan  orchestration

• Requirements  Management– Requirement  traceability

• Enterprise  Agile– Backlog  unification– Build  traceability

• Development– Build  automation– Change  set  traceability– Code  review  traceability

• Quality  Management– Defect  unification– Test  traceability

• Service  Management– Incident  escalation– Known  issue  propagation– Feature  request  traceability

• Security– Vulnerability  escalation

• Operations– Deployment  automation– Alert  escalation

Page 25: Achieving Continuous Visibility Across the DevOps Lifecycle

CONNECTING THE VALUE STREAM

25

CA PPM

Requirements Traceability

PMBOK SAFe DevOps

Continuous Visiblity

DNG RTC HP QC uDeploy ServiceNow

ProcessFrameworks

IntegrationPatterns

IntegrationTechnologies

Value stream

ITIL

Synchronization Linking OSLCWeb

Hooks

Defect Unification …

LifecycleTools

Page 26: Achieving Continuous Visibility Across the DevOps Lifecycle

VALUE STREAM FLOW

26

JIRAHP QC ALM

Bluemix

BMC Remedy

CA CLARITY

INVESTMENT THEMES

BUSINESS EPIC

$

BUSINESS EPIC

IBM DNG/RRC

Feature

USER STORY

USER STORY

DEFECT DEFECT

TEST CASE

USER STORY

BUSINESS EPIC

Feature

Feature

BUSINESS EPIC

Feature

Feature

IBM RTCFeature

USER STORY

USER STORY

DEFECT

DEFECT

TEST CASE

DEFECT

USER STORY

USER STORY

DEFECT

Test case link

Test case link

Test case link

FEATURE

INCIDENT

PROBLEM

Feature

Feature

Feature

Feature

USER STORY

USER STORY

USER STORY

USER STORY

Feature

Page 27: Achieving Continuous Visibility Across the DevOps Lifecycle

DEVOPS INTEGRATION PATTERNS

27

Page 28: Achieving Continuous Visibility Across the DevOps Lifecycle

PUTTING IT ALL TOGETHER

28

Page 29: Achieving Continuous Visibility Across the DevOps Lifecycle

CONTINUOUS VISIBLITY

Page 30: Achieving Continuous Visibility Across the DevOps Lifecycle

PATTERN LANGAUGE FOR DEVOPS & AGILE INTEGRATION

30

Integration Infrastructure

Integration Patterns

Process Frameworks

Value Stream

Lifecycle Tools

Page 31: Achieving Continuous Visibility Across the DevOps Lifecycle

VISABILITY VIA REAL TIME INFORMATION

31

UrbanCode Integration

Tasktop UrbanCode Plug-in

Schedulefor Release

Monitor Release Gate Environments

Orchestrate Deployment

Automate Deployment

PRODUCT MANAGER

Work Request

QA

Tasktop

DELIVERY OPPORTUNITIES

ENTERPRISE AND SYSTEM VIEWS

DEPENDENCIES AND IMPACTS

QUALITY, SECURITY & TEST STATUS

AUTOMATION

DEPLOYMENT STATUS

MORE AUTOMATION LESS VARIANCE

RTC UCR UCD

Page 32: Achieving Continuous Visibility Across the DevOps Lifecycle

32

Page 33: Achieving Continuous Visibility Across the DevOps Lifecycle

“YOU HAVE TO THINK HORIZONTALLY.”

32

Page 34: Achieving Continuous Visibility Across the DevOps Lifecycle

“LOCAL OPTIMIZATION IS THE ENEMY OF

LEAN DELIVERY.”

33

Page 35: Achieving Continuous Visibility Across the DevOps Lifecycle

“AUTOMATIONREQUIRES PATTERNS,

PATTERNS REQUIRES ELIMINATING VARIANCE.”

34

Page 36: Achieving Continuous Visibility Across the DevOps Lifecycle

“TECHNOLOGY IS THE FUN PART,

CULTURE IS THE CHALLENGE.”

36

Page 37: Achieving Continuous Visibility Across the DevOps Lifecycle

“HARD TO MANAGE WHAT YOU CAN'T SEE…OR MEASURE.”

35

Page 38: Achieving Continuous Visibility Across the DevOps Lifecycle

Achieving Continuous Visibility across the DevOps Lifecycle

MIK KERSTEN | CEO, Tasktop@mik_kersten

CARMEN DEARDO | Nationwide Technology Director@carmendeardo

SESSION 3268