Why take a Continuous Delivery approach in your organisatiion

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

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

17
Improve Engagement &
Retain Talent

20
Improve customer satisfaction

22
Keep the lights on
& don’t screw up

24
Case Study 1:
Online Accounting Software

37
Assemble the team, and
brainstorm the problems

38
Create a Value-Stream-Map
for our delivery process and
identify constraints

39
Agree a model based on:
Common KPIs
Clear 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
132
146
160
173
S O N D J F M A M
# of Scenarios

44
4. Introduced TDD and CI
60
65 65 65
80
83
93 94 94
S O N D J F M A M
% Coverage

45
5. Automated our deployment scripts
Deployment duration (mins)
S O N D J F M
130
98

47
Improved our predictability and delivery times
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
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
High
Performance/
Hewitt
Best Employer
Zone
30%
100%0%
65%40%

51
Relieved the pressure on the
backlog

52
Case Study 2:
SAP Service Delivery

54
Core platform for HR and
Finance

56
Demand for new functionality

57
Two major stakeholders
(with differing priorities)

60
Assemble the team,
and train them on Kanban

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

62
of the delivery pipeline.

63
of the delivery pipeline,
and build a Kanban wall for
their work

65
Month 1
Consultation
/Envisaging
Triage/
Prioritisatio
n
Investigate/
Analyse
Solution
Design
Implement/
Build
Test UAT
CR Approval
/ CAB
Deploy/
Close out
Waiting Doing

66
Month 2
Consultation
/Envisaging
Triage/
Prioritisatio
n
Investigate/
Analyse
Solution
Design
Implement/
Build
Test UAT
CR Approval
/ CAB
Deploy/
Close out
Waiting Doing
FinanceHR

67
Month 3
Consultation
/Envisaging
Triage/
Prioritisatio
n
Investigate/
Analyse
Solution
Design
Implement/
Build
Test UAT
CR Approval
/ CAB
Deploy/
Close out
Waiting Doing
FinanceHR

69
Improved communications
between the team

70
Better visibility of priorities
and progress for the
stakeholders

74
Why would you adopt
Continuous Delivery?

76
Pull from the
Agile/Lean/Kanban/DevOps
toolkits

77
Maintain a mindset of
Continuous Delivery of value
for the customers

Why take a Continuous Delivery approach in your organisatiion

More Related Content

What's hot

Similar to Why take a Continuous Delivery approach in your organisatiion

More from Nish Mahanty

Recently uploaded

Why take a Continuous Delivery approach in your organisatiion

Editor's Notes