Driving Continuous Delivery Transformation in a Data-Driven Way

Intern © Siemens Healthineers, 2019
Siemens
Healthineers
Digital Health
Dr. Vladyslav Ukis
November 2019
Driving Continuous Delivery
Transformation in a Data-Driven Way

2
© Siemens Healthineers, 2019
In this talk
• How did we introduce Continuous Delivery
at Siemens Healthineers Digital Health?
• How are we driving Continuous Delivery
Transformation?
• Q&A
Dr. Vladyslav Ukis

3
How did we introduce
Continuous Delivery at
SHS Digital Health?
Dr. Vladyslav Ukis

4
teamplay Vision
Dr. Vladyslav Ukis
Scan # 94567
Scan # 2747 Scan # 24375
Scan # 04567 Scan # 53566 Scan # 56469
Scan # 14567
Scan # 27652
Scan # 64364
Scan # 51566
Scan # 24161 Scan # 56785
Scan # 36854
Scan # 52556
Scan # 36469
Scan # 25667
Scan # 44767 Scan # 24543
Scan # 26469Scan # 34565
Scan # 24554
10,000s
Scanners
100,000s
Users
1,000,000s
Exams
Connect, compare, collaborate.

5
teamplay Applications
Constant
update cycles
Dr. Vladyslav Ukis
1) teamplay Protocols supports selected Siemens scanners. Please contact your Siemens representative for more details.
2) The DICOM viewer is not intended for diagnostic display | Due to regulations data exchange between data center regions is restricted. The
products/features/service offerings are not commercially available in all countries. If the services are not marketed in countries due to regulatory or other reasons,
the service offering cannot be guaranteed. Please contact your local Siemens organization for further details.

6
Global availability served from 8 data centers
Availability of teamplay
teamplay Data Center
(MS Azure)

7
Partner Applications
Dr. Vladyslav Ukis

8
Initial teamplay releases
revealed the necessity for a
cutting edge CD approach
Dr. Vladyslav Ukis

9
Target: Always keep the system in a releasable state
• from the product point of view
• from the technical point of view
• from the regulatory point of view
Enable each dev team to release independently at will
Minimize Mean Time To Repair (MTTR)
Cutting edge CD approach

10
What needs to change to enable Continuous Delivery?
Architecture
Deployment Pipeline
Project Management
QM Release Process
Branching
Dev Artefacts
Source Control
Sprint Notion
Test First Approach
Test Cycle: 1h
Office Space
Management Style
Team Structure
Team Roles
Pair Collaboration
Hiring
Feature Inceptions
Estimations
Info Radiation
Communication Tools
Requirements Eng.
Prioritization
Metrics
Code Ownership
Feedback Cycles
Optimization Criteria
Meeting Structure
Dev Effort Allocation
Portfolio Management
…
Dr. Vladyslav Ukis

11
What needs to change to enable Continuous Delivery?
Architecture
Deployment Pipeline
Project Management
QM Release Process
Branching
Dev Artefacts
Source Control
Sprint Notion
Test First Approach
Test Cycle: 1h
Office Space
Management Style
Team Structure
Team Roles
Pair Collaboration
Hiring
Feature Inceptions
Estimations
Info Radiation
Communication Tools
Requirements Eng.
Prioritization
Metrics
Code Ownership
Feedback Cycles
Optimization Criteria
Meeting Structure
Dev Effort Allocation
Portfolio Management
…
Dr. Vladyslav Ukis
We are changing the entire org!

12
How are we driving the Continuous
Delivery Transformation?
Dr. Vladyslav Ukis

13
„Culture eats strategy for breakfast.“
Peter Drucker
Dr. Vladyslav Ukis

14

15
CD Ways of Working: Deliver with stability and speed
Dr. Vladyslav Ukis

16
Dr. Vladyslav Ukis
New Way To
Define The
Product

17
Dr. Vladyslav Ukis
New Way To
Test The
Product

18
Dr. Vladyslav Ukis
New Way To
Deploy The
Product

19
We are scaling
the CD Process
to 17+ teams!
…
Dr. Vladyslav Ukis

20
Monthly CD Team Self-Assessment
• Challenge: how to keep up the ongoing application of CD Methods in a growing dev org new to CD?
• Monthly CD Team Self-Assessments was initially used to help establish a broad application of CD Methods
Dr. Vladyslav Ukis

21
Monthly CD Team Self-Assessment: up to 100 points for 10 topics
0 points if: … 10 points if:
Topic 1 User Story
Map
- no user story map available … - each user story is available in a user story map
- no user story contains implem. or UI details
- entire team is involved in story mapping process
Topic 2 BDD
Scenarios
- no user story is broken down into
scenarios
… - each user story is broken down into scenarios;
- contributors of scenarios are PO, AR, BA, Dev, Ops
- no scenario contains implement. or UI details
Topic 3 DSL - no scenario starts being
implemented with a DSL
… - each scenario starts being implemented with a DSL
- DSL does not contain implem. or UI entities, only domain
entities
Topic 4 Acceptance
Tests
- no scenario is tested first using
DSL and Acceptance Test before
Product Code is created
… - each scenario is tested first using DSL and Acceptance
Test before Product Code is created
Topic 5 TDD - no scenario is tested second
using Unit Tests before Product
Code is created
… - each scenario is tested second using Unit Tests before
Product Code is created

22
Monthly CD Team Self-Assessment: up to 100 points for 10 topics
0 points if: … 10 points if:
Topic 6 Commit - the way of working in the team is never: Red
UT → Green UT → Refactor UT + Product
Code → Commit
… - the way of working in the team is
always: Red UT → Green UT → Refactor
UT + Product Code → Commit
Topic 7 Pairing - developers never work in pairs … - developers always work in pairs for any
kind of work and rotate pairs regularly
Topic 8 Pipeline Build +
UT Execution
- feedback cycle from Build + UT is > 10 mins
wait time for devs
… - feedback cycle from Build + UT is <= 5
mins wait time for devs
Topic 9 Pipeline
Acceptance Test
Execution
- feedback cycle from Acceptance Tests is > 90
mins wait time for devs
… - feedback cycle from Acceptance Tests
is <= 60 mins wait time for devs
Topic 10 Information
Radiator
- flow of commits through pipeline
environments is not visible on Inf. Radiators
neither in BLR / BRA nor in ERL
… - flow of commits through pipeline
environments is clearly visible on Inf.
Radiators in BLR / BRA and in ERL

23
Monthly CD Team Self-Assessment Results
34 35 36 37
39
43
47 47 47
49
53
56 56
0
10
20
30
40
50
60
Dez 17 Jan 18 Feb 18 Mrz 18 Apr 18 Mai 18 Jun 18 Jul 18 Aug 18 Sep 18 Okt 18 Nov 18 Dez 18
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Org
Average
Totals across all teams and methods
Self-assessed methods: User Story Mapping, BDD, DSL, Acceptance Tests, TDD, Commit, Pairing, UT Exec, Acceptance Test Exec, Info Radiator

24
Monthly CD Team Self-Assessment Results Evaluation
0
1
2
3
4
5
6
7
User Story
Map
BDD Scenarios
DSL
Acceptance
Tests
TDD
Commit
Pairing
Pipeline UT
Execution
Pipeline Acceptance
Test Execution
Information
Radiator
Org Average Nov-18
Org Average Dec-18
Most adopted Least adopted
User Story Map TDD
BDD Scenarios Pipeline Accept.
Test Exec.
Pipeline UT Exec. Info Radiators

25
How to drive the Continuous
Delivery Transformation further?
Dr. Vladyslav Ukis

26
How to drive the Continuous Delivery Transformation further?
Switch from
„are we doing this practice?“
towards
„what is the outcome of our current practice?“

27
The Theory of Constraints
Dr. Vladyslav Ukis

28
Continuous Delivery and the Theory of Constraints
• Systematically identify bottlenecks in value flow through the organization and eliminate them
• The Theory of Constraints changed manufacturing before, changing software delivery now with CD
Dr. Vladyslav Ukis

29
But what is the value flow in
software delivery?
Dr. Vladyslav Ukis

30
Dr. Vladyslav Ukis
Code DeployBuild

31
Dr. Vladyslav Ukis
Code DeployBuild
How to identify bottlenecks in this value flow?

32
The what, why, and how of measuring Continuous Delivery
Measuring Continuous Delivery
Dr. Vladyslav Ukis
By Steve Smith

33
Continuous Delivery Indicators: Stability and Throughput
CD Indicators help uncover bottlenecks in the team‘s value stream: Code  Build  Deploy
• Code Throughput
• Build Stability and Throughput
• Deployment Stability and Throughput
Use the biggest bottlenecks to drive prioritization of measures to remove them
Dr. Vladyslav Ukis

34
What are possible bottlenecks in the „Code  Build  Deploy“
value flow?
Dr. Vladyslav Ukis

35
How to find bottlenecks using CD Stability and Throughput
Indicators?
CD Indicators help uncover bottlenecks in the
team‘s value stream: Code  Build  Deploy
• Code Throughput
• Build Stability and Throughput
• Deployment Stability and Throughput
Dr. Vladyslav Ukis
 Low Values Are Good!

36
Early Prototype for Stability and
Throughput Indicators
Dr. Vladyslav Ukis

37

38
Analysis:
- Instable Builds
Action:
- Drive down build failure rate
- Drive down build failure rate variation

39

40
Analysis:
- Short-term build failure rate impr. in March
Action:
- Keep build failure rate & variation low
- Look for another constraint

41

42
Analysis:
- Short-term build failure rate impr. end of March
- Build failure rate variation is high end of March
Action:

43

44
Analysis:
- Rollercoaster pattern 
- High variation of build failure rate
Action:

45
time

46
time
Analysis:
- High variation of build throughput
Action:
- Drive down build throughput variation

47
time

48
time
Analysis:
- High build throughput variation
Action:
- Drive down build throughput variation
- Increase build throughput

49

50
Analysis:
- Great deploym. stability improvem. in Feb
- Low deploym. stability variation in March
Action:
- Keep deploym. failure rate low
- Look for another constraint

51

52
Action:
- Drive down depl. throughput variation
Action:
- Drive down depl. failure variation
Action:
- Drive down depl. failure rate
Action:
- Drive down depl. failure recovery time

53

54
Goal
Enable a dev team to see their value stream Code  Build  Deploy and bottlenecks at a glance using:
• Code Throughput Indicator
• Build Stability and Throughput Indicators
• Deployment Stability and Throughput Indicators
Use the bottlenecks to drive prioritization decisions systematically
• Automatically suggest a prioritization of the bottlenecks in case there are many
• Automatically suggest action items to be taken
We want a smooth and frequent delivery
• Low CD indicators values to strive for
Dr. Vladyslav Ukis

55
In Summary
Establishing a cutting edge CD approach means changing the entire organization, especially the culture!
Monthly CD Team Self-Assessments initially helped establish a broad application of CD methods
CD Indicators of Stability and Speed help
• identify bottlenecks in the teams‘ value streams
• drive prioritization of measures to remove the bottlenecks
• provide data-driven insight into teams‘ sw delivery process for continous improvement
Dr. Vladyslav Ukis

56

57
Q&A
Dr. Vladyslav Ukis

58
More on InfoQ
https://www.infoq.com/articles/continuous-delivery-teamplay/

59
Thank you
for your enthusiasm!
Dr. Vladyslav Ukis
Software Development Lead
Mobile: +49 173 6885413
vladyslav.ukis@siemens-healthineers.com
Siemens Healthineers
Digital Services,
Data Architecture and Technology, Platform
Siemens Healthcare GmbH
Hartmannstr. 16
91052 Erlangen, Germany
www.siemens-healthineers.com
Dr. Vladyslav Ukis

Driving Continuous Delivery Transformation in a Data-Driven Way

Recomendados

Recomendados

Mais conteúdo relacionado

Mais procurados

Mais procurados (20)

Semelhante a Driving Continuous Delivery Transformation in a Data-Driven Way

Semelhante a Driving Continuous Delivery Transformation in a Data-Driven Way (20)

Último

Último (20)

Driving Continuous Delivery Transformation in a Data-Driven Way