1
00:00:06,920 --> 00:00:09,157
- Many times when I go in to see teams,

2
00:00:09,157 --> 00:00:12,388
we have a discussion about
obstacles to automation.

3
00:00:12,388 --> 00:00:15,545
There are so many that
are similar across teams

4
00:00:15,545 --> 00:00:17,986
and those are some of the ones
that we'll talk about today.

5
00:00:17,986 --> 00:00:19,920
One of the first ones I hear is,

6
00:00:19,920 --> 00:00:22,758
"How can I get the rest
of my team to help?"

7
00:00:22,758 --> 00:00:26,491
So they are really missing
that whole team approach.

8
00:00:26,491 --> 00:00:29,200
- Right, they maybe expect the testers

9
00:00:29,200 --> 00:00:31,283
to do all the automation.

10
00:00:35,381 --> 00:00:38,741
Another problem I see in
a lot of new Agile teams

11
00:00:38,741 --> 00:00:39,811
is they're missing out

12
00:00:39,811 --> 00:00:43,189
on those core Agile development practices,

13
00:00:43,189 --> 00:00:44,821
like test-driven developments,

14
00:00:44,821 --> 00:00:47,181
so they don't even have
automated unit tests.

15
00:00:47,181 --> 00:00:50,061
So it makes it very hard to even start

16
00:00:50,061 --> 00:00:52,468
because they're missing those skills.

17
00:00:52,468 --> 00:00:55,132
I often find that sometimes
they don't even want

18
00:00:55,132 --> 00:00:59,049
to know or they don't
know what skills to have.

19
00:01:00,451 --> 00:01:02,321
It's a lack of knowledge almost, right?

20
00:01:02,321 --> 00:01:03,738
- Right, exactly.

21
00:01:03,738 --> 00:01:06,672
- The other thing we see is

22
00:01:06,672 --> 00:01:08,788
we have too much to do,

23
00:01:08,788 --> 00:01:12,832
so much work we don't
have time for learning.

24
00:01:12,832 --> 00:01:14,683
It's like getting stuck
on that hamster wheel,

25
00:01:14,683 --> 00:01:16,907
as I like to call it.
- Right, yeah.

26
00:01:16,907 --> 00:01:18,472
- So, you just get too busy.

27
00:01:18,472 --> 00:01:19,305
- Right.

28
00:01:20,669 --> 00:01:22,340
Worrying about those deadlines.

29
00:01:22,340 --> 00:01:23,173
- Yes.

30
00:01:24,270 --> 00:01:27,430
- And one I hear so often is,

31
00:01:27,430 --> 00:01:29,541
"We don't have time, we don't have money

32
00:01:29,541 --> 00:01:31,883
for the tools we need," right?

33
00:01:31,883 --> 00:01:35,483
- Yeah, it's kind of that
whole pay me now, pay me later,

34
00:01:35,483 --> 00:01:38,892
that's kind of what we'll
talk about a little bit.

35
00:01:38,892 --> 00:01:41,489
The last one that I see really often

36
00:01:41,489 --> 00:01:45,853
is that the user interface is
changing all the way through.

37
00:01:45,853 --> 00:01:48,443
You've got these small stories
that changes every time,

38
00:01:48,443 --> 00:01:50,352
how can we possibly automate?

39
00:01:50,352 --> 00:01:52,701
- Right, especially
because so many new teams

40
00:01:52,701 --> 00:01:55,670
are trying to do all their
automation through the UI

41
00:01:55,670 --> 00:01:58,181
and wondering why they
can't succeed with it.

42
00:01:58,181 --> 00:01:59,221
- Right.

43
00:01:59,221 --> 00:02:00,967
- This is just a few of the obstacles

44
00:02:00,967 --> 00:02:02,922
that your team might face

45
00:02:02,922 --> 00:02:04,434
and we're going to talk

46
00:02:04,434 --> 00:02:08,184
about how we can change
the approach to automation

47
00:02:08,184 --> 00:02:11,267
to help you overcome these obstacles.