1
00:00:07,410 --> 00:00:10,930
After watching this video, you will be able
to define DevOps,

2
00:00:10,930 --> 00:00:16,070
identify misconceptions about DevOps, and
recognize the best approach for teams using

3
00:00:16,070 --> 00:00:17,147
DevOps.

4
00:00:17,372 --> 00:00:20,889
The term DevOps is often misunderstood.

5
00:00:20,889 --> 00:00:25,680
For example, this drop-down list that
I saw recently while signing up for a webinar.

6
00:00:25,680 --> 00:00:31,630
It asked for my job function and provided
the options of DevOps/Technical Ops or Software

7
00:00:31,630 --> 00:00:32,630
Developer/Engineer.

8
00:00:32,630 --> 00:00:35,530
I’m a software engineer who practices DevOps.

9
00:00:35,530 --> 00:00:40,120
These job titles don’t reflect DevOps and
frankly, this organization should know better.

10
00:00:40,120 --> 00:00:45,440
Clearly, they did not notice the letters “D-E-V”
in DevOps, which stand for “development.”

11
00:00:45,440 --> 00:00:49,840
Here is a clue, if you’re not doing development,
you’re not doing DevOps, you’re just

12
00:00:49,840 --> 00:00:50,840
doing Ops.

13
00:00:50,840 --> 00:00:53,899
They apparently did not understand this.

14
00:00:53,899 --> 00:00:57,489
There are both Dev and Ops in software development.

15
00:00:57,489 --> 00:01:01,620
For them, DevOps/Technical Ops is something
that the Ops people do.

16
00:01:01,620 --> 00:01:06,650
But DevOps is not something that just Ops
people do.

17
00:01:06,650 --> 00:01:08,710
There are different perspectives of DevOps.

18
00:01:08,710 --> 00:01:12,970
You start with traditional development and
operations that have a wall of confusion between

19
00:01:12,970 --> 00:01:14,430
them.

20
00:01:14,430 --> 00:01:19,539
Many organizations, like this webinar organization
from my example, think that DevOps is something

21
00:01:19,539 --> 00:01:24,500
the Ops people do, and that DevOps is a subset
of operations.

22
00:01:24,500 --> 00:01:28,360
Some organizations think that DevOps is something
developers do.

23
00:01:28,360 --> 00:01:33,180
But most organizations think DevOps is
a separate team that sits between Dev and

24
00:01:33,180 --> 00:01:35,150
Ops and keeps both of them happy.

25
00:01:35,150 --> 00:01:38,050
I’m going to talk more about that in a moment.

26
00:01:38,050 --> 00:01:40,030
None of these perspectives are correct.

27
00:01:40,030 --> 00:01:44,430
DevOps is a mindset that the whole organization
adopts.

28
00:01:44,430 --> 00:01:45,610
You will see this a lot in start-ups.

29
00:01:45,610 --> 00:01:47,850
DevOps is their company culture.

30
00:01:47,850 --> 00:01:54,750
It’s Dev and Ops working together with the
same mindset, preferably on the same team,

31
00:01:54,750 --> 00:01:58,130
using the same goals and measurements.

32
00:01:58,130 --> 00:02:03,360
Jez Humble wrote, “The DevOps movement addresses
the dysfunction that results from organizations

33
00:02:03,360 --> 00:02:05,550
composed of functional silos.

34
00:02:05,550 --> 00:02:10,780
Thus, creating another functional silo that
sits between Dev and Ops is clearly a poor

35
00:02:10,780 --> 00:02:14,050
(and ironic) way to solve these problems.”

36
00:02:14,050 --> 00:02:17,970
Remember, there is no such thing as a DevOps
team.

37
00:02:17,970 --> 00:02:23,030
That is an antipattern; it causes more problems
than it would solve.

38
00:02:23,030 --> 00:02:27,690
You see, DevOps is the recognition that working
in silos doesn’t work.

39
00:02:27,690 --> 00:02:31,470
You may have seen this “wall of confusion”
graphic, made famous by Andrew Clay Shafer.

40
00:02:31,470 --> 00:02:37,340
It depicts the diametrically opposed goals
of development and operations.

41
00:02:37,340 --> 00:02:40,500
Development is measured by how many new features
they can push to production.

42
00:02:40,500 --> 00:02:45,110
Operations, on the other hand, is measured
by how stable production is.

43
00:02:45,110 --> 00:02:50,980
One way to stabilize production is to not
change anything, like adding new features.

44
00:02:50,980 --> 00:02:55,760
If you create a separate DevOps team, you
are just creating another silo that further

45
00:02:55,760 --> 00:02:57,300
separates Dev and Ops.

46
00:02:57,300 --> 00:03:00,390
This doesn’t make any sense when you look
at it this way.

47
00:03:00,390 --> 00:03:04,760
You don’t create a team to make you DevOps
any more than you would create a team to make

48
00:03:04,760 --> 00:03:06,210
you Agile.

49
00:03:06,210 --> 00:03:10,710
No one forms an Agile team and claims that
their organization is suddenly Agile because

50
00:03:10,710 --> 00:03:12,180
of that team over there.

51
00:03:12,180 --> 00:03:16,810
No, the organization must adopt the Agile
mindset, becoming Agile.

52
00:03:16,810 --> 00:03:19,460
DevOps is no different.

53
00:03:19,460 --> 00:03:22,320
The reality is that DevOps is not a job title.

54
00:03:22,320 --> 00:03:25,880
It is not something one person does, or a
team does.

55
00:03:25,880 --> 00:03:29,870
It is a cultural transformation on an organizational
scale.

56
00:03:29,870 --> 00:03:34,880
It is the practice of development and operations
engineers working together during the entire

57
00:03:34,880 --> 00:03:41,290
software lifecycle, preferably on the same
team, following Lean and Agile principles

58
00:03:41,290 --> 00:03:46,410
that allow them to deliver high-quality software
stably and continuously.

59
00:03:46,410 --> 00:03:50,900
It starts with learning how to work differently
and embracing cross-functional teams with

60
00:03:50,900 --> 00:03:54,970
openness, transparency, and trust as pillars.

61
00:03:54,970 --> 00:04:00,770
If that doesn’t sound like your organization,
then you are probably not practicing DevOps.

62
00:04:00,770 --> 00:04:06,240
In this video, you learned that DevOps is
a mindset that the whole organization adopts.

63
00:04:06,240 --> 00:04:09,850
DevOps solves the problems caused by siloed
teams.

64
00:04:09,850 --> 00:04:14,580
DevOps is the practice of development and
operations engineers working together during

65
00:04:14,580 --> 00:04:20,470
the entire software lifecycle, following Lean
and Agile principles that allow them to deliver

66
00:04:20,470 --> 00:04:22,507
high-quality results.