1 00:00:00,000 --> 00:00:04,518 [MUSIC] 2 00:00:04,518 --> 00:00:08,003 Now that we've covered the who, what, when and 3 00:00:08,003 --> 00:00:12,944 where of Scrum, we just have a few details left, the why and the how. 4 00:00:12,944 --> 00:00:16,792 We'll learn about how the product backlog and user stories, 5 00:00:16,792 --> 00:00:20,795 help the team understand why they are doing what they are doing. 6 00:00:20,795 --> 00:00:25,510 We'll also learn about other tools used by the team in the sprint. 7 00:00:25,510 --> 00:00:29,190 These tools are sometimes referred to as Scrum artifacts, 8 00:00:29,190 --> 00:00:33,420 because they are visible to the team and people outside the team as well. 9 00:00:33,420 --> 00:00:38,260 So far, you may have noticed that we've used the terms user story and 10 00:00:38,260 --> 00:00:43,030 product backlog item in ways that have seemed almost interchangeable. 11 00:00:43,030 --> 00:00:45,447 The truth is there is a distinction. 12 00:00:45,447 --> 00:00:49,881 The term product backlog item is a general term to refer to anything in 13 00:00:49,881 --> 00:00:51,342 the product backlog. 14 00:00:51,342 --> 00:00:56,735 A product backlog item can refer to a bug or a defect, a piece of technical work, 15 00:00:56,735 --> 00:01:01,406 a feature request or even large, poorly defined items that need to be 16 00:01:01,406 --> 00:01:05,449 broken down into smaller items, sometimes called epics. 17 00:01:05,449 --> 00:01:09,726 User stories, on the other hand are special product backlog items. 18 00:01:09,726 --> 00:01:12,627 They don't simply describe a feature or a bug. 19 00:01:12,627 --> 00:01:16,657 They are called stories, because they tell you about more than just about how 20 00:01:16,657 --> 00:01:19,827 a feature behaves, but also what is happening for the user. 21 00:01:19,827 --> 00:01:21,477 The value is always clear and 22 00:01:21,477 --> 00:01:24,861 it's always described from the point of view of the user. 23 00:01:24,861 --> 00:01:28,488 Here's a template that is very helpful in constructing a user's story. 24 00:01:28,488 --> 00:01:30,600 It consists of three parts. 25 00:01:30,600 --> 00:01:36,430 As a blank, I need blank, so that blank. 26 00:01:36,430 --> 00:01:41,414 The value of the user story is defined by who the user is, what they need, 27 00:01:41,414 --> 00:01:42,900 and why they need it. 28 00:01:42,900 --> 00:01:46,457 For example, if we were constructing an interactive lesson, 29 00:01:46,457 --> 00:01:49,822 we might write a user story for English language learners. 30 00:01:49,822 --> 00:01:54,926 As an English language learner, I need to see the definition of a word 31 00:01:54,926 --> 00:02:00,380 when I tap on it, so that I can understand new vocabulary words. 32 00:02:00,380 --> 00:02:05,670 Crafting a user story that effectively conveys these three parts, takes practice. 33 00:02:05,670 --> 00:02:06,810 So here are some tips. 34 00:02:07,820 --> 00:02:12,588 To really focus on why you are writing this user story rather than just on 35 00:02:12,588 --> 00:02:17,118 a feature or requirement, start with the so that part of the story, 36 00:02:17,118 --> 00:02:22,227 then you can fill in the details of who the user is and what exactly they need. 37 00:02:22,227 --> 00:02:25,300 As you fill in the additional detail, you can check to 38 00:02:25,300 --> 00:02:29,550 make sure you are still describing a single story and that it makes sense. 39 00:02:30,790 --> 00:02:32,490 Here's another example. 40 00:02:32,490 --> 00:02:33,199 Let's say, 41 00:02:33,199 --> 00:02:37,265 we have a survey tool and we find that users aren't completing the survey. 42 00:02:37,265 --> 00:02:38,678 By talking to the users, 43 00:02:38,678 --> 00:02:42,394 we find out that many only get part of the way through the process. 44 00:02:42,394 --> 00:02:47,088 But then they give up, because they don't know how much longer it will take. 45 00:02:47,088 --> 00:02:52,430 We want to help with that, so we write a user story starting with the so that. 46 00:02:52,430 --> 00:02:54,960 So that I know I'm almost done and 47 00:02:54,960 --> 00:02:59,570 I don't give up is a clear statement of the value of the user story. 48 00:02:59,570 --> 00:03:04,925 We want a user taking a survey to be able to see where they are in the survey and 49 00:03:04,925 --> 00:03:06,712 be motivated to finish. 50 00:03:06,712 --> 00:03:09,613 Now, I can think about what the user needs. 51 00:03:09,613 --> 00:03:13,913 I need a progress indicator for the survey. 52 00:03:13,913 --> 00:03:15,927 And finally, who needs it? 53 00:03:15,927 --> 00:03:18,509 As a survey-taker. 54 00:03:18,509 --> 00:03:23,244 As you can see, user stories are different from other types of backlog items, 55 00:03:23,244 --> 00:03:25,912 because they focus on the value to the user. 56 00:03:25,912 --> 00:03:30,253 It is intentional for user story to steer clear of detailing a solution. 57 00:03:30,253 --> 00:03:33,669 In Scrum, the team has flexibility in finding a solution, so 58 00:03:33,669 --> 00:03:37,600 long as it meets the described need in the user story. 59 00:03:37,600 --> 00:03:42,410 A user story is simply describes the need the user has and who the user is. 60 00:03:42,410 --> 00:03:45,020 Let's review the three parts of the user story. 61 00:03:45,020 --> 00:03:49,150 As a blank, I need blank, so that blank. 62 00:03:50,300 --> 00:03:54,060 If you're a product owner, you'll have a lot of practice crafting and 63 00:03:54,060 --> 00:03:55,180 defining user stories. 64 00:03:56,220 --> 00:04:00,820 If you're a development team member, you'll learn to decompose stories and 65 00:04:00,820 --> 00:04:05,210 ask clarifying questions to ensure that your team has a shared understanding 66 00:04:05,210 --> 00:04:07,240 of what value you will deliver and why.