Dr Nish Mahanty

@nishmahanty

Why would you take a Continuous Delivery approach?

The path to successfully transforming your IT Services.

2

https://puppetlabs.com/sites/default/files/2014-state-of-devops-report.pdf

3

http://continuousdelivery.com/

4

Two case studies of how I’ve applied CD in different

enterprises

5

Continuous Delivery is a method of getting features to our customers fast and often.

http://productblog.seek.com.au/continuous-delivery

6

Continuous Delivery is a method of getting features to our customers fast and often.

And then incrementing on those features based on metrics

and customer feedback

http://productblog.seek.com.au/continuous-delivery

7

Warning!

8

CD often starts as a “tools” conversation

9

Then you realise that your processes need to change

10

Then you realise that your structures aren’t quite right

11

Finally you notice (if you are successful)

that your culture has changed

12

13

Common set of challenges

14

External Disruption

15

Internal Imperatives

16

Do more with less

17

Improve Engagement &Retain Talent

18

Be more predictable

19

Improve quality

20

Improve customer satisfaction

21

Keep the lights on

22

Keep the lights on & don’t screw up

23

Continuous Delivery!

24

Case Study 1:

Online Accounting Software

25

Product in market

26

Paid subscribers 24/7

27

Strong distributed team

28

Good stakeholder support

29

Challenges

30

New functionality

31

Improve performance

32

UX improvements

33

Improve stability

34

Defect reduction

35

Faster turn-around times

36

Approach

37

Assemble the team, and brainstorm the problems

38

Create a Value-Stream-Mapfor our delivery process and

identify constraints

39

Agree a model based on:

Common KPIsClear communications

Trust

40

Agreed a list of incremental improvements

41

1. Agreed proportions of capacity for each class-of-service and stakeholder

42

2. Improved communications between the teams

43

3. Introduced Functional automation tests

Automated functional tests

0

21

56

79

110

132146

160173

S O N D J F M A M

# of Scenarios

44

4. Introduced TDD and CI

Automated functional tests

6065 65 65

8083

93 94 94

S O N D J F M A M

% Coverage

45

5. Automated our deployment scripts

Automated functional tests

Deployment duration (mins)

S O N D J F M

13098

46

Outcomes

47

Improved our predictability and delivery times

Automated functional tests

Cycle Time for Defects and Features (days)

Cycle Time (Features and Defects)

S O N D J F M

30

9.8

48

Reduced our environment constraints

Automated functional tests

Time spent preparing an environment for a deployment (days)

Cycle Time (Features and Defects)

Delivery

Duration

87%faster release

11

1

49

Shifted the customer NPS by 70 points!

50

Improved Team Engagement

HighPerformance/

Hewitt Best Employer

Zone

30%

100%0%

65%40%

51

Relieved the pressure on the backlog

52

Case Study 2:

SAP Service Delivery

53

Large Academic Institution

54

Core platform for HR and Finance

55

Challenges

56

Demand for new functionality

57

Two major stakeholders (with differing priorities)

58

Visibility on progress

59

Approach

60

Assemble the team, and train them on Kanban

61

Assemble the team, and train them on Kanban(in particular, Kaizen, and

Flow)

62

Create a Value-Stream-Mapof the delivery pipeline.

63

Create a Value-Stream-Mapof the delivery pipeline,

and build a Kanban wall for their work

64

SAP Team Kanban wall

65

Month 1

Consultation/Envisaging

Triage/ Prioritisatio

n

Investigate/ Analyse

Solution Design

Implement/ Build

Test UATCR Approval

/ CAB

Deploy/ Close out

Waiting Doing

66

Month 2

Consultation/Envisaging

Triage/ Prioritisatio

n

Investigate/ Analyse

Solution Design

Implement/ Build

Test UATCR Approval

/ CAB

Deploy/ Close out

Waiting Doing

Fin

ance

HR

67

Month 3

Consultation/Envisaging

Triage/ Prioritisatio

n

Investigate/ Analyse

Solution Design

Implement/ Build

Test UATCR Approval

/ CAB

Deploy/ Close out

Waiting Doing

Fin

ance

HR

68

Outcomes

69

Improved communications between the team

70

Better visibility of priorities and progress for the

stakeholders

71

Increased throughput

72

Much happier team

73

In Summary

74

Why would you adopt Continuous Delivery?

75

Take team driven approach

76

Pull from the Agile/Lean/Kanban/DevOps

toolkits

77

Maintain a mindset of Continuous Delivery of value

for the customers

78

Thank you, and good luck

79

Questions?