continuous delivery in a large bankdownload.microsoft.com/download/a/4/b/a4b8872e-5ff...one delivery...

CONTINUOUS DELIVERY IN A LARGE BANK EXPERIENCE REPORT FROM IMPLEMENTING CONTINUOUS DELIVERY IN A LARGE BANK

Image Source: http://www.forbes.com/sites/benkerschberg/2015/02/04/why-devops-integration-and-continuous-delivery-hold-the-key-to-enterprise-mobile-app-dev/

1

ABOUT ME

3

@shri2201

ING COMMERCIAL BANKING – CHANNELS AND PAYMENTS

4

CD STEP BY STEP

1. Why Continuous Delivery

2. Organize the teams

3. Organize the product management

4. Set up standard deployment pipelines

5. Set up automated measurements

6. Enable DevOps culture

5

1. Why continuous delivery(CD) in a large bank?

6

WHAT IS DRIVING CD ADOPTION IN THE BANKS?

Time to market

Challengers entering the banking market

Inefficiency of traditional IT processes

Lack of agility

Natural extension of Scrum to DevOps

7

8

DEVOPS COVERS THE ENTIRE APPLICATION LIFECYCLE

Scrum

Scrum + XP

Practices

Scrum + XP

+ AD + OPS

Solution Delivery Service

Delivery

Image Source: http://www.collab.net/solutions/devops

9

FOUR PILLARS OF DEVOPS

DevOps

Culture Automation Measurement Sharing

10

DEVOPS AS A CHANGE IN A BANK

People

• Focus

• Shared goal

• Collaboration

• Team work

• Multi skilled team

• Self organizing

• Setting high standards

• Multi disciplinary team

Process

• Optimize the whole

• Regular and same heartbeat for the team

• Visibility in the entire value chain

• Feedback

• Short work cycles (2-3 weeks)

Technology

• Automation of deployment tasks

• Automation of testing tasks

• Experimentation with new tools

• Automated code review

11

2. Organize the teams

12

CHALLENGES OF DEVOPS IMPLEMENTATION IN A LARGE BANK

Complex IT Landscape

Architecture of Applications

Culture of Compliance and Control

Alignment of IT with business

Alignment of IT with IT

https://devcentral.f5.com/articles/devops-is-not-all-about-automation

13

We deliver business value, change and stable systems.

Product Owner Development Team Operations Team

DEVOPS

14

DEVOPS TEAM COMPOSITION S

CR

UM

TEA

M Dev Engineers

Ops Engineers

Scrum Master

Product Owner

KEY CHARACTERISTICS OF A DEVOPS TEAM

1. One Team

2. One Product Backlog

3. One Goal

4. One Delivery Cycle (User story to live in One Sprint!!)

5. Self Organizing

6. Focus upon both change and stability

DevOps

Team

(9 People Max)

15

3. Organize the product management

16

PRODUCT BACKLOG

• Functional changes or features

• Incidents

• Bugs

• Risk Findings

• Monitoring requirements

• Technical Improvements

• Architectural Constraints

Sprint planning will be done by

the whole Scrum team together.

Every sprint will deliver functional changes and

non-functional changes

Every sprint delivers features that are in

production

17

PROGRAM TRACKING

Program

Features

Epics

User Stories

1 *

1 *

1 *

18

JIRA STRUCTURE *****

19

20

4. Set up standard deployment pipelines

21

TECHNOLOGY

Complex set of applications

Mix of the latest systems to legacy systems

Each feature triggers a series of changes in diverse applications

Changes have to be deployed in a synchronized manner

Both existing features on old stack and new stack have to be tested

22

ARCHITECTURE – BUILDING BLOCKS

Channel Order Manager

Payment Hub

Gateway

Account

Management

Billing

Cash

Management

Reporting

2 1

3 4

5

6

Channel Channel

23

TEST OFTEN & AUTOMATED

Feature Regression Tests

Feature Acceptance Tests

Smoke tests

(E2E Test Team)

User acceptance test at Feature Level

Exploratory test

(UAT Team)

Bila tests

BB Regression tests

System Acceptance tests

Unit tests

(DevOps Team)

Performance Test

Load Test

Resilience Test

(DevOps Team)

Business / Feature facing

Technology / Building Block facing

Build

ing

the t

hin

g ri

ght

Build

ing

the r

ight

thin

g

Manual

Automated Automated

Automated

24

COMPLEX PLAYGROUND

Technology : Java, Mainframe COBOL, .NET, Tibco BW, Android Java, Objective-C,

Home Made, COTS, Configured and Customized COTS

Batches and Messaging based Integration

40+ Scrum Teams

Multiple programs requiring changes

DTAP Environments

Distributed teams - Onsite and Offshore

Image Source:

http://tonysneed.com/images/commoninstancefactory/instance-factory.jpeg 25

STANDARD DEPLOYMENT PIPELINE

Continuous Integration Deployment Automation

Automated Infra Provisioning

Automated Monitoring

26

DEPLOYMENT PIPELINE JAVA

ALM SCM Build Contin.

Integr. Analyze Reposit. Test Deploy Monitor

TBSM

ITCAM

STASH

27

DEPLOYMENT PIPELINE .NET

ALM SCM Build Contin.

Integr. Analyze Reposit. Test Deploy Monitor

TBSM

ITCAM

TFS TFS TFS/VS VS/TFS TFS SCOM TFS TFS

Sharepoint

28

WORKFLOW IN CD PIPELINE

29

2

1

3

4

5

6 7

9

8

Toll Gate

5. Set up automated measurements

30

QUALITY & COMPLIANCE DASHBOARDS

What do we publish on dashboards

Code Quality, Test Coverage

Chain Testing

Problem and Incident Management

Compliance at toll gates

31

SONAR

32

FEATURE TESTING

33

FEATURE TESTING

34

TOLLGATES CHECKLIST

35

6. Enable DevOps Culture

36

CULTURE

Communities of Practices and Events

Guilds

Continuous Delivery Open Evening

Agile Event

Engineering Culture Event

Hackathons

Mindset and behaviour training

37

PHASES OF DEVOPS IMPLEMENTATION

Scrum Dev+Ops DevOps

< 1 year, 40+ DevOps teams

38

CRITICAL SUCCESS FACTORS

Technology

Standardization of development

and deployment tools

Automated infra provisioning

Organization & Behavior

Senior Executive Sponsorship

Visual Management

Walk the Talk

Coaching & Training

External consultants

Knowledge sharing

Formal Classroom Training

Training KPI

39

CAN WE DECLARE OUR VICTORY?

Easy Hard

Set up Continuous Delivery Pipeline Making team members use it

Making dashboards available Making people act upon matrices

Conducting events to bolster culture Making managers and engineers live up the culture

Making a single product backlog Setting the priorities

Standardizing Definition of Done Making sure that teams follow it

Setting up release automation Achieving continuous delivery

Presentation in TechDays Getting things done

40

OUTCOME

SPEED QUALITY CRAFTSMANSHIP

41

THANK YOU

Anurag Shrivastava

shri2201@gmail.com

42