1
00:00:00,460 --> 00:00:01,160
Welcome back.

2
00:00:01,180 --> 00:00:06,250
So as you can see, we're back in this little canvas that we've been working on, we have a journey

3
00:00:06,250 --> 00:00:07,390
that we've been creating.

4
00:00:07,690 --> 00:00:11,200
We have an assumptions grid stakeholders and users.

5
00:00:11,200 --> 00:00:12,160
We have project goals.

6
00:00:12,610 --> 00:00:16,390
And what I like to do is I like to create a story map.

7
00:00:16,390 --> 00:00:22,060
As you can tell, as I was building on this journey map over here, I started thinking about all the

8
00:00:22,060 --> 00:00:26,530
different requirements that are happening along the way of the different things we're asking users.

9
00:00:26,860 --> 00:00:29,320
And it's starting to look like a user story map.

10
00:00:29,440 --> 00:00:31,870
And you may be thinking, what is a user storing map?

11
00:00:31,880 --> 00:00:33,000
What's a user story?

12
00:00:33,160 --> 00:00:34,510
Why does it need to be mapped?

13
00:00:34,780 --> 00:00:39,490
Well, this really helps a prioritization and figuring out releases.

14
00:00:40,330 --> 00:00:45,610
Now, as a designer, I feel like this is super helpful even for myself when I need to think about the

15
00:00:45,610 --> 00:00:48,640
types of things I need to actually design for.

16
00:00:49,780 --> 00:00:53,530
So what I'm going to do is I'm going to run you through how we can do this for ourselves.

17
00:00:53,740 --> 00:01:01,480
So I'm going to just steal this journey map and we can start breaking that out a bit.

18
00:01:01,480 --> 00:01:01,990
We can.

19
00:01:01,990 --> 00:01:03,430
I'm going to just copy it here.

20
00:01:06,580 --> 00:01:13,030
OK, so what is it you just joined up, so you just do a mapping is how we consistently help either

21
00:01:13,030 --> 00:01:20,770
clients or our product team to release small incremental portions of value with the ability to release

22
00:01:20,770 --> 00:01:24,460
at any time and know when the product is viable.

23
00:01:25,060 --> 00:01:32,380
It is a product planning method that really helps the product owner and the team focus on end user business

24
00:01:32,380 --> 00:01:36,330
outcomes when planning what to build and to build it.

25
00:01:36,820 --> 00:01:41,810
So these story maps complement the traditional flat backlog.

26
00:01:41,830 --> 00:01:46,390
So if we think about the type of work that we're trying to build here, it's broken into a bunch of

27
00:01:46,390 --> 00:01:49,900
different pieces and those types of things live in the thing called the backlog.

28
00:01:49,900 --> 00:01:53,500
And a backlog is essentially just a long list of different types of features.

29
00:01:53,740 --> 00:02:00,580
If we're thinking about like a traditional spec now by adding the context of the user's activities and

30
00:02:00,580 --> 00:02:08,410
tasks to help design releases that address immediate priorities through a regular cadence of enhancements.

31
00:02:09,930 --> 00:02:16,320
Flat backlogs really make it difficult to understand the different types of features and how these features

32
00:02:16,320 --> 00:02:20,260
relate to each other and how do they create value for the customer.

33
00:02:20,700 --> 00:02:25,480
So if I'm thinking more traditional aspects, they don't really mention any of that.

34
00:02:26,250 --> 00:02:32,640
The user story map really helps us focus on the activity that needs to be completed first and adds just

35
00:02:32,640 --> 00:02:39,600
enough stories to allow the activity to happen in the first release, then follow up with enhancements

36
00:02:39,600 --> 00:02:41,370
in subsequent releases.

37
00:02:43,170 --> 00:02:47,140
So what is a story map and what is it made up of?

38
00:02:47,930 --> 00:02:49,800
Now let's take a look at this.

39
00:02:50,720 --> 00:02:52,860
This is essentially a starting up in a way.

40
00:02:54,510 --> 00:03:01,950
But if we want to think about it a little bit more in depth, starting up has several different things.

41
00:03:02,790 --> 00:03:03,900
It has the persona.

42
00:03:05,350 --> 00:03:12,230
And it has a backbone, so we're just going to copy this line, bring it up here.

43
00:03:12,730 --> 00:03:18,900
So this is the backbone and the backbone is made up of high level activities.

44
00:03:18,940 --> 00:03:22,800
The app will facilitate in order of priority.

45
00:03:23,110 --> 00:03:27,310
It's made up of two elements, your main activities and tasks.

46
00:03:28,450 --> 00:03:36,700
Now, the main activity could be something like onboarding and the task could be something like let's

47
00:03:36,700 --> 00:03:38,260
think about tasks and onboarding

48
00:03:42,010 --> 00:03:44,980
into personal details.

49
00:03:47,580 --> 00:03:54,310
OK, now the activities, this is the highest portion of this backbone.

50
00:03:55,290 --> 00:04:02,160
These are usually thought of as like these large epics that is usually like an agile term to house all

51
00:04:02,160 --> 00:04:04,530
the different features within like a category.

52
00:04:05,420 --> 00:04:11,000
But these represent an activity the user has in relation to this application, so like I said.

53
00:04:11,860 --> 00:04:12,520
Unbury.

54
00:04:13,480 --> 00:04:19,450
Tasks describe the events that need to happen in order for the user to complete this larger activity.

55
00:04:20,360 --> 00:04:23,310
You know, an example is like entering personal details.

56
00:04:26,350 --> 00:04:32,710
Let's throw that in there, another one could be enter interests.

57
00:04:39,740 --> 00:04:45,740
Add products that I am interested in.

58
00:04:51,030 --> 00:05:01,020
Maybe there's an education portion of education around on boarding process, so these are all the different

59
00:05:01,020 --> 00:05:06,100
types of tasks that need to be completed in order for somebody to complete this activity.

60
00:05:07,110 --> 00:05:09,630
So, as you can see, we're starting to build that backbone.

61
00:05:10,410 --> 00:05:12,630
Now, there may be more activities.

62
00:05:14,210 --> 00:05:16,250
Like I said, there may be another one.

63
00:05:17,900 --> 00:05:26,000
That is like what's an example of an activity I want to be able to find a product that's a high level

64
00:05:26,000 --> 00:05:29,210
activity and some tasks could be search.

65
00:05:31,570 --> 00:05:35,350
I want to be able to see the results.

66
00:05:39,480 --> 00:05:44,480
So you can start to see how we are building this kind of narrative in this backbone.

67
00:05:47,300 --> 00:05:54,470
Now, in the next video, we're going to be focusing on the bottom portion of a story map and what a

68
00:05:54,470 --> 00:05:55,460
user story is.