1
00:00:00,570 --> 00:00:08,370
So let's think about this portion of a story now that we've talked about the backbone of the user story

2
00:00:08,370 --> 00:00:12,000
map, we have to talk about the body and that's what happens underneath.

3
00:00:12,920 --> 00:00:19,850
Now, the body of the story that describes the details of how to make tasks happen, the body has two

4
00:00:19,850 --> 00:00:24,740
elements user stories and releases now user stories.

5
00:00:24,770 --> 00:00:28,400
These are the details of how the tasks are done to meet the goal.

6
00:00:28,730 --> 00:00:29,990
An example would be.

7
00:00:31,020 --> 00:00:33,420
Let's figure this out and your personal details.

8
00:00:34,050 --> 00:00:42,860
I want so typical, your story would be as a user, I want to do something because of something.

9
00:00:43,140 --> 00:00:50,310
But if I were to write this in a more simple way, let's actually bring down the font size so we have

10
00:00:50,310 --> 00:00:50,910
more room.

11
00:00:51,180 --> 00:00:51,600
So.

12
00:00:53,220 --> 00:01:16,320
As a shopper, I want to be able to enter my name and e-mail address so that the application knows who

13
00:01:16,350 --> 00:01:17,250
I am.

14
00:01:18,120 --> 00:01:19,800
So that's what a user story would be.

15
00:01:20,520 --> 00:01:25,980
Gives us a good insight into the type of features that we need to build for this application, but also

16
00:01:25,980 --> 00:01:27,600
the reasoning behind those features.

17
00:01:27,630 --> 00:01:46,860
Another one could be, as a shopper, I want to be able to enter my address so that I can get relevance

18
00:01:47,280 --> 00:01:51,250
results based off of my location.

19
00:01:51,270 --> 00:01:56,670
I'm not sure if this is actually going to be possible, but it's another way to think about features

20
00:01:56,670 --> 00:02:00,750
in a different way instead of just saying we need to have a sign up form.

21
00:02:01,060 --> 00:02:02,460
I mean, yeah, that makes sense.

22
00:02:02,460 --> 00:02:07,370
But why do we need to have a sign of form to the sign up form, have different aspects to it?

23
00:02:07,380 --> 00:02:13,260
Do we need to create an entire onboarding experience in order to facilitate larger experience for the

24
00:02:13,260 --> 00:02:16,590
users and like finding products and etc.?

25
00:02:17,340 --> 00:02:24,240
So these user stories really help to make us understand, like the different types of steps we need

26
00:02:24,240 --> 00:02:29,460
to do to complete these individual tasks and the reasoning in the user motivation behind it all.

27
00:02:30,300 --> 00:02:36,060
Now let's think about the second part of the body releases the releases.

28
00:02:36,060 --> 00:02:41,300
They helped to describe usable and testable versions of the application that can be released.

29
00:02:41,890 --> 00:02:46,350
Know it's helpful to make these as small as possible, but also as descriptive as possible.

30
00:02:46,350 --> 00:02:54,240
For instance, the first release of this like application that we're building habitual could be just

31
00:02:54,240 --> 00:03:02,220
a way for a user to see all the different products that are relevant to their interests, has no search.

32
00:03:02,430 --> 00:03:06,000
It has no profile necessarily just yet.

33
00:03:06,000 --> 00:03:11,740
But we're only thinking about the little pieces of information that we need to get started.

34
00:03:11,760 --> 00:03:16,290
So if we want to move this release line up over here.

35
00:03:18,160 --> 00:03:24,700
We can start breaking this into different releases, so we have our first release here, an example

36
00:03:24,700 --> 00:03:31,150
for use your story for interest that we want in our first release, which I usually call the MVP release

37
00:03:31,600 --> 00:03:39,600
could be I want to give a list of things I am interested in.

38
00:03:40,090 --> 00:03:43,470
I'm going to save you some time and not right out of the entire year.

39
00:03:43,520 --> 00:03:43,870
Sorry.

40
00:03:44,230 --> 00:03:47,560
A second thing that may make it into the release.

41
00:03:47,980 --> 00:03:56,080
I want to tell you my hobbies, because maybe we can pull from that type of information so that they

42
00:03:56,080 --> 00:03:57,130
make it into the release.

43
00:03:57,130 --> 00:04:00,970
And so we just can give them some space.

44
00:04:01,120 --> 00:04:06,370
And as you can tell, we're starting to build out a release of features that we find to be the highest

45
00:04:06,370 --> 00:04:06,890
priority.

46
00:04:07,570 --> 00:04:15,550
So an example here would be I want to list products that I really like.

47
00:04:18,010 --> 00:04:29,950
But something that may be out of scope would be something like, I want to connect a previous shopping

48
00:04:30,790 --> 00:04:37,780
application to show you my purchase history.

49
00:04:43,310 --> 00:04:48,590
Like I said, I'm not sure what exactly is going to be possible from an engineering standpoint, but

50
00:04:48,920 --> 00:04:54,710
as you can tell, this isn't really a high priority in order for us to understand if we can serve up

51
00:04:54,710 --> 00:04:57,220
relevant products to our user just yet.

52
00:04:58,800 --> 00:05:07,230
You know, maybe one thing for education and onboarding, maybe there is I want to see an intro screen

53
00:05:09,690 --> 00:05:10,920
that's probably needed.

54
00:05:14,680 --> 00:05:20,460
I want to see how long I am in the process.

55
00:05:21,790 --> 00:05:26,920
For onboarding, that could be another that we definitely need.

56
00:05:29,050 --> 00:05:32,140
So this is how we start to create releases.

57
00:05:32,170 --> 00:05:35,310
And like I said, these enhancements will come at a later stage.

58
00:05:35,320 --> 00:05:40,330
It's not like we forget about them, but they just aren't as important to us right now.

59
00:05:40,570 --> 00:05:44,980
And in this moment now, people often say, what do you do from here?

60
00:05:45,010 --> 00:05:50,890
Well, I would start designing this release and then the goal would be to validate it.

61
00:05:50,920 --> 00:05:56,890
It's often difficult to know for sure that the activities and tasks listed match, you know, how the

62
00:05:56,890 --> 00:06:00,220
target user performs or thinks about these activities.

63
00:06:00,790 --> 00:06:05,620
The closer the similarities between the activities and the tasks in the story map are to the actual

64
00:06:05,620 --> 00:06:10,180
target users mental model, the more intuitive the application starts to seem.

65
00:06:10,960 --> 00:06:16,090
So that's when we start to bring in things like user testing to really understand your motivations and

66
00:06:16,090 --> 00:06:18,180
the reasons they want to do certain things.

67
00:06:18,580 --> 00:06:23,800
We can also take this prototypes that we build based off of these features that we're building and talk

68
00:06:23,800 --> 00:06:29,950
to our users about them and see if they can use them, see if they want to use them, get their feedback

69
00:06:29,950 --> 00:06:31,000
on those types of things.

70
00:06:31,970 --> 00:06:37,340
Now, this is what my process is like when I start a project, I also use story maps for whenever we

71
00:06:37,340 --> 00:06:39,050
build larger features.

72
00:06:39,380 --> 00:06:47,570
But I'm always, always thinking about ways we can implement the smallest release possible, even on

73
00:06:47,570 --> 00:06:49,850
a smaller scale of enhancements.

74
00:06:50,420 --> 00:06:56,390
We want to make sure that we're not committing to too much because in and of itself, these stories

75
00:06:56,390 --> 00:06:57,200
are risks.

76
00:06:57,410 --> 00:06:59,540
They are assumptions that we're making about the user.

77
00:06:59,690 --> 00:07:04,940
And if we take on too much before we actually validate, it may all be wasted work.

78
00:07:04,940 --> 00:07:06,500
And that's incredibly expensive.

79
00:07:07,720 --> 00:07:13,480
So I say, get out there, try to figure out who your users are and start mapping out the different

80
00:07:13,480 --> 00:07:20,200
types of features you want to build that you think you should build based off of the input from the

81
00:07:20,200 --> 00:07:25,120
subject matter experts that you have in your product alignment canvas from your product team.

82
00:07:25,420 --> 00:07:31,660
Go out there and don't just make assumptions, but make sure that your releases are really planned based

83
00:07:31,660 --> 00:07:38,350
off of different types of feedback and different types of understanding and validation of who your users

84
00:07:38,350 --> 00:07:39,400
are and what their goals are.