1
00:00:06,691 --> 00:00:09,374
- The section name "Shift
Your Mindset" might seem

2
00:00:09,374 --> 00:00:12,146
a little odd, but by
the end of this lesson,

3
00:00:12,146 --> 00:00:14,779
you'll have a good
understanding of what we mean.

4
00:00:14,779 --> 00:00:16,931
There's nothing wrong
with the old mindset,

5
00:00:16,931 --> 00:00:20,648
but to work on an Agile team,
you need a different one.

6
00:00:20,648 --> 00:00:23,442
There is no one right way to go.

7
00:00:23,442 --> 00:00:25,328
The train tracks signal that we can

8
00:00:25,328 --> 00:00:27,688
take many different paths.

9
00:00:27,688 --> 00:00:29,515
We're going to introduce a
different way to approach

10
00:00:29,515 --> 00:00:32,396
testing in our product development.

11
00:00:32,396 --> 00:00:34,674
We need an Agile mindset to be open,

12
00:00:34,674 --> 00:00:37,837
to assess progress, and
to make corrections.

13
00:00:37,837 --> 00:00:40,273
To build in quality, we
need to be continually

14
00:00:40,273 --> 00:00:44,440
retrospecting, setting goals,
experimenting, and improving.

15
00:00:46,433 --> 00:00:50,319
When I hire testers, or I talk to testers,

16
00:00:50,319 --> 00:00:52,102
and I ask what their job is,

17
00:00:52,102 --> 00:00:54,221
or what they think their job is,

18
00:00:54,221 --> 00:00:58,609
they'll often say, "Well,
we need to find defects

19
00:00:58,609 --> 00:01:00,862
or perhaps go looking at the requirements

20
00:01:00,862 --> 00:01:02,431
and making sure they're all met."

21
00:01:02,431 --> 00:01:06,518
Or maybe even, my least favorite,
"To break the software."

22
00:01:06,518 --> 00:01:09,408
There gets to be a lot of finger-pointing.

23
00:01:09,408 --> 00:01:11,691
It's an attitude not appropriate for Agile

24
00:01:11,691 --> 00:01:14,187
because instead of collaborating,

25
00:01:14,187 --> 00:01:16,289
we get a hostile relationship,

26
00:01:16,289 --> 00:01:19,682
so we're asking people
to think differently.

27
00:01:19,682 --> 00:01:21,374
Ask "How can we help?"

28
00:01:21,374 --> 00:01:25,762
It makes a huge difference in
the collaboration of the team.

29
00:01:25,762 --> 00:01:27,603
We still have to do that other stuff,

30
00:01:27,603 --> 00:01:30,697
but the emphasis is
different, others on your team

31
00:01:30,697 --> 00:01:34,086
are not the opposing team,
the team works together

32
00:01:34,086 --> 00:01:36,409
to make the product successful.

33
00:01:36,409 --> 00:01:37,870
This sometimes is a new attitude

34
00:01:37,870 --> 00:01:41,828
to some testers, but a
lot of testers have been

35
00:01:41,828 --> 00:01:46,464
doing this for years, so keep
asking "How can we help?"

36
00:01:46,464 --> 00:01:49,293
It's not only testers that
have to change their mindset.

37
00:01:49,293 --> 00:01:52,410
The rest of the team,
including the programmers,

38
00:01:52,410 --> 00:01:56,576
they need to be thinking,
instead of taking my code

39
00:01:56,576 --> 00:01:58,855
and giving it to somebody else to test,

40
00:01:58,855 --> 00:02:00,881
they need to think a
little bit differently.

41
00:02:00,881 --> 00:02:02,817
A lot of times, programmers
test their own code

42
00:02:02,817 --> 00:02:04,784
and they do it really, really well,

43
00:02:04,784 --> 00:02:07,227
but sometimes, they have a cognitive bias

44
00:02:07,227 --> 00:02:09,281
that might blind them to some risks.

45
00:02:09,281 --> 00:02:11,360
They're focused on the small chunks,

46
00:02:11,360 --> 00:02:13,519
not seeing the big picture.

47
00:02:13,519 --> 00:02:16,436
If the programmers can
start to think about testing

48
00:02:16,436 --> 00:02:19,387
all the time, in fact, if the
whole team starts to think

49
00:02:19,387 --> 00:02:23,699
about testing all the time,
they work better together,

50
00:02:23,699 --> 00:02:27,814
and that makes for a much
more collaborative team.