1
00:00:07,680 --> 00:00:12,000
Hi, I’m John Rofrano, Senior Technical Staff
Member, and DevOps Champion at IBM Research,

2
00:00:12,000 --> 00:00:16,000
and I’d like to welcome you
to Introduction to DevOps.

3
00:00:16,000 --> 00:00:21,040
This course will help you understand the
cultural, as well as technological, transformation

4
00:00:21,040 --> 00:00:26,560
that is required to not only make your DevOps
initiative successful but allow it to flourish.

5
00:00:27,760 --> 00:00:34,560
According to a recent DevOps Institute report,
demand for DevOps skills are expected to grow 122%

6
00:00:35,120 --> 00:00:39,200
over the next five years, making it one of
the fastest-growing skills in the workforce.

7
00:00:39,840 --> 00:00:43,440
Unfortunately, having skills
alone won’t ensure success.

8
00:00:43,440 --> 00:00:49,120
Gartner predicts that through 2022, 75%
of DevOps initiatives will fail to meet

9
00:00:49,120 --> 00:00:52,400
expectations due to issues around
organizational learning and change.

10
00:00:53,040 --> 00:00:58,800
I can’t stress enough, the number one reason for
failing to meet expectations is not around skills,

11
00:00:58,800 --> 00:01:04,160
it’s not around tools, but due to issues around
organizational learning and cultural change.

12
00:01:04,720 --> 00:01:09,280
Cultural change can have a significant
positive effect on DevOps's success.

13
00:01:10,320 --> 00:01:13,280
According to George Spafford,
Senior Director Analyst at Gartner,

14
00:01:13,280 --> 00:01:18,240
“People-related factors tend to be the
greatest challenges—not technology.”

15
00:01:18,880 --> 00:01:22,880
You see, DevOps is not a tool.
DevOps is not a job title.

16
00:01:22,880 --> 00:01:27,280
DevOps is the practice of development and
operations engineers working together through

17
00:01:27,280 --> 00:01:30,720
the entire software development
lifecycle, following Lean and

18
00:01:30,720 --> 00:01:36,080
Agile principles that allow them to deliver
software in a rapid and continuous manner.

19
00:01:36,080 --> 00:01:39,200
If you want to do it fast …and you want
to do it continuously, then you need to

20
00:01:39,200 --> 00:01:43,280
adopt a shared mindset that is at
the heart of the DevOps culture.

21
00:01:44,160 --> 00:01:46,480
So, how do you change a culture?

22
00:01:48,080 --> 00:01:51,600
In order to change your culture, you
need to learn new ways of how to think,

23
00:01:52,400 --> 00:01:57,200
how to work, how to organize, and how to measure.

24
00:01:58,160 --> 00:02:02,320
Throughout this course, we will look at how
businesses are being affected by disruption

25
00:02:02,320 --> 00:02:04,560
and how a DevOps culture can help.

26
00:02:05,280 --> 00:02:09,360
We’ll cover thinking differently through social
coding and improving software reuse and sharing.

27
00:02:10,080 --> 00:02:13,280
We will learn about ideas from Lean
manufacturing such as working in small

28
00:02:13,280 --> 00:02:18,320
batches to reduce waste, creating minimum
viable products to gain valuable insight.

29
00:02:19,680 --> 00:02:24,880
We will explore working differently by using
test-driven and behavior-driven development

30
00:02:24,880 --> 00:02:29,040
techniques to ensure repeatable
behavior and high code quality.

31
00:02:29,600 --> 00:02:34,560
You will see how adopting Continuous Integration
and Continuous Delivery practices ensure that

32
00:02:34,560 --> 00:02:38,720
every change contributes to a
potentially shippable feature.

33
00:02:39,600 --> 00:02:43,600
But… “Tools are not the
solution to a cultural problem.”

34
00:02:44,480 --> 00:02:49,360
According to the 2021 Accelerate State
of DevOps Report by the DevOps Research

35
00:02:49,360 --> 00:02:52,000
and Assessment (DORA) team, which, by the way,

36
00:02:52,000 --> 00:02:58,080
represents seven years of research and data
from more than 32,000 professionals worldwide:

37
00:02:59,360 --> 00:03:03,120
“Team culture makes a large
difference to a team’s ability

38
00:03:03,120 --> 00:03:07,280
to deliver software and meet or
exceed their organizational goals.”

39
00:03:08,240 --> 00:03:12,800
In order to change your culture, you’ll need to
organize your teams differently because how you

40
00:03:12,800 --> 00:03:17,840
organize directly impacts the architecture and
design of the products that you produce.

41
00:03:19,200 --> 00:03:23,920
You know, humans have a knack for
figuring out what behavior is rewarded,

42
00:03:23,920 --> 00:03:28,720
and then doing—or at least pretending
to do—that rewarded behavior.

43
00:03:29,760 --> 00:03:34,240
The last cultural change we will
discuss is measuring differently,

44
00:03:34,240 --> 00:03:38,720
and how changing your measurement
system to encourage the correct behavior

45
00:03:38,720 --> 00:03:42,720
is critical for your success
because you get what you measure.

46
00:03:43,600 --> 00:03:47,120
We’ll also look at how to avoid being
fooled by vanity metrics and how you

47
00:03:47,120 --> 00:03:51,440
can use actionable metrics to gain valuable
insight about your product and your customers.

48
00:03:52,400 --> 00:03:57,840
Implementing a DevOps initiative isn’t easy,
but it can be very, very rewarding. In order

49
00:03:57,840 --> 00:04:04,480
to really embrace the DevOps culture, you have
to be willing to make changes… lots of changes.

50
00:04:05,040 --> 00:04:09,840
You must be willing to experiment and
understand that it’s okay if an experiment fails

51
00:04:09,840 --> 00:04:13,440
because “every failure is a learning opportunity.”

52
00:04:13,440 --> 00:04:14,400
So, fail fast.

53
00:04:15,200 --> 00:04:20,640
You need to foster the core values of
teamwork, accountability, and trust.

54
00:04:21,520 --> 00:04:25,520
So, join me in exploring how you can
transform the culture and technology of

55
00:04:25,520 --> 00:04:29,680
your organization so that your DevOps
journey will be a successful one.

56
00:04:29,680 --> 00:04:34,160
Watch the videos, take the quizzes, and
interact with your peers on the forums

57
00:04:34,160 --> 00:04:38,480
because DevOps is a team sport,
and collaboration is encouraged.

58
00:04:39,280 --> 00:04:40,560
I like to say:

59
00:04:40,560 --> 00:04:44,201
We don’t “do” DevOps… we “become” DevOps!