WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.100 --> 00:00:10.300
In this video, we will go over devops principles and how they can guide

1
00:00:10.300 --> 00:00:12.700
 you when implementing devops culture and process.

2
00:00:13.900 --> 00:00:16.100
Devops has guidelines or you

3
00:00:16.100 --> 00:00:19.800
 can call it principles that Define the philosophy of delivering software.

4
00:00:19.800 --> 00:00:22.400
 The five principles are represented in an

5
00:00:22.400 --> 00:00:26.300
 easy to understand acronym called comms com stands

6
00:00:25.300 --> 00:00:29.500
 for culture automation lean measurement

7
00:00:28.500 --> 00:00:30.400
 and sharing.

8
00:00:31.100 --> 00:00:34.400
While these principles are going to be in the context of software development and delivery.

9
00:00:34.400 --> 00:00:37.100
 You could apply them across many aspects of your business.

10
00:00:38.200 --> 00:00:40.200
Let's go over each of the five in more detail.

11
00:00:41.200 --> 00:00:44.300
C stands for culture culture is greater than

12
00:00:44.300 --> 00:00:47.300
 strategy if culture does not come from the top down

13
00:00:47.300 --> 00:00:50.500
 then using devops principles will fail. There must

14
00:00:50.500 --> 00:00:53.500
 be a buy-in from all corners of your organization. For example,

15
00:00:53.500 --> 00:00:56.700
 your culture may include aspects like shared

16
00:00:56.700 --> 00:00:59.300
 ownership or safe work environment to discuss ideas

17
00:00:59.300 --> 00:00:59.900
 openly.

18
00:01:00.700 --> 00:01:03.300
Remember, you cannot duplicate a culture

19
00:01:03.300 --> 00:01:06.600
 from another business and shoehorn it into yours. It has

20
00:01:06.600 --> 00:01:09.300
 to grow from within and be natural to your environment.

21
00:01:10.100 --> 00:01:11.600
a represents automation

22
00:01:12.300 --> 00:01:15.400
Automation is your power move. If a lot of build a

23
00:01:15.400 --> 00:01:19.000
 time is spent doing manual work to deliver software to customers. Then

24
00:01:18.300 --> 00:01:21.400
 that is time not spend on adding features or

25
00:01:21.400 --> 00:01:24.400
 fixing bugs to have a continuous flow from left

26
00:01:24.400 --> 00:01:27.800
 to right development to deployment then automation

27
00:01:27.800 --> 00:01:30.100
 is key L stands for lean.

28
00:01:30.700 --> 00:01:32.900
Lean is the focus on the flow of your system.

29
00:01:33.700 --> 00:01:36.000
Teams should be able to work autonomously and use

30
00:01:36.300 --> 00:01:39.200
 data to drive decision engineering's main goal is

31
00:01:39.200 --> 00:01:43.000
 to frequently release small changes to flush out bugs and bottlenecks.

32
00:01:43.800 --> 00:01:46.300
Being lean is never done. It is a continuous

33
00:01:46.300 --> 00:01:48.400
 process of measuring and making changes.

34
00:01:49.500 --> 00:01:50.500
M is for measurement

35
00:01:51.300 --> 00:01:54.400
you can't change anything if you did not measure it as I

36
00:01:54.400 --> 00:01:57.900
 said the culture in your organization must be a data-driven

37
00:01:57.900 --> 00:01:58.000
 one.

38
00:01:58.600 --> 00:02:01.300
There is no time for guessing or gut feelings when making

39
00:02:01.300 --> 00:02:04.200
 flow decisions metrics should tell a narrative

40
00:02:04.200 --> 00:02:06.000
 of the state of your system at any given time.

41
00:02:07.600 --> 00:02:10.800
S stands for sharing and we all know sharing is

42
00:02:10.800 --> 00:02:13.800
 caring there should be openness and transparency across

43
00:02:13.800 --> 00:02:16.000
 your whole organization, especially in the

44
00:02:16.600 --> 00:02:18.800
 flow path left to right and right to left.

45
00:02:19.600 --> 00:02:22.600
each team that is responsible for the delivery of code should have

46
00:02:22.600 --> 00:02:25.500
 the same goals and objectives this makes sure everyone

47
00:02:25.500 --> 00:02:28.600
 is doing the right thing for the right reason in other

48
00:02:28.600 --> 00:02:31.500
 words everyone in your organization should understand

49
00:02:31.500 --> 00:02:32.400
 the why

50
00:02:33.700 --> 00:02:36.500
In this video we learned about DeVos principles

51
00:02:36.500 --> 00:02:40.400
 described in a handy to use acronym called comms culture

52
00:02:39.400 --> 00:02:42.300
 automation lean measurement and

53
00:02:42.300 --> 00:02:42.800
 sharing.

54
00:02:43.300 --> 00:02:46.600
These guiding philosophies and power organizations to create a foundation

55
00:02:46.600 --> 00:02:50.100
 that Fosters collaboration empowerment and

56
00:02:49.100 --> 00:02:51.600
 shared goals and objectives.

57
00:02:52.200 --> 00:02:55.400
Devops principles are roadmap that use a

58
00:02:55.400 --> 00:02:57.000
 professional can inject into your environment.

59
00:02:57.800 --> 00:03:00.300
Remember the goal is to apply these principles in

60
00:03:00.300 --> 00:03:03.600
 other devops philosophies to your system and business only

61
00:03:03.600 --> 00:03:06.100
 where they make sense do not force it.

62
00:03:06.900 --> 00:03:09.400
And if all else fails just stay

63
00:03:09.400 --> 00:03:10.500
 calms and carry on.

64
00:03:12.200 --> 00:03:15.700
In the next video, I will go over some common devops terminology

65
00:03:15.700 --> 00:03:17.100
 you will counter on your journey.
