1 00:00:00,580 --> 00:00:02,990 So now we have a bunch of user stories and 2 00:00:02,990 --> 00:00:06,090 other product backlog items that the team will work on. 3 00:00:06,090 --> 00:00:07,380 Where do they go? 4 00:00:07,380 --> 00:00:09,090 How do we organize them? 5 00:00:09,090 --> 00:00:11,100 We keep these items in the product backlog. 6 00:00:12,220 --> 00:00:16,810 The product backlog is an ordered list of all the items the team might work on. 7 00:00:16,810 --> 00:00:19,530 The highest priority items are at the top, and 8 00:00:19,530 --> 00:00:22,150 the lower priority items are further down the list. 9 00:00:23,190 --> 00:00:26,870 There are many digital tools that allow you to maintain an ordered list for 10 00:00:26,870 --> 00:00:28,660 your product backlog. 11 00:00:28,660 --> 00:00:32,690 But many teams find it easier to start with the simplest tools available. 12 00:00:32,690 --> 00:00:34,590 Large index cards. 13 00:00:34,590 --> 00:00:38,150 A team can set up their space with the product backlog taped to the wall for 14 00:00:38,150 --> 00:00:39,600 everyone to see. 15 00:00:39,600 --> 00:00:44,080 Use painter's tape to attach the cards to the wall, because it's safe to attach and 16 00:00:44,080 --> 00:00:45,620 remove the tape. 17 00:00:45,620 --> 00:00:48,140 Otherwise, you may find yourself in trouble 18 00:00:48,140 --> 00:00:52,330 when you remove a product backlog item, and take a piece of the wall with it. 19 00:00:52,330 --> 00:00:57,070 Maintaining the product backlog is one of the responsibilities of the product owner. 20 00:00:57,070 --> 00:00:59,908 The product owner makes sure each piece of work for 21 00:00:59,908 --> 00:01:02,621 the team is captured by a product backlog item. 22 00:01:02,621 --> 00:01:05,741 These don't necessarily start out as fully formed user stories. 23 00:01:05,741 --> 00:01:11,440 Sometimes you just need to get an idea, like export to .CSV. 24 00:01:11,440 --> 00:01:11,990 And then later, 25 00:01:11,990 --> 00:01:15,850 work them into user stories that are small enough to include in a sprint. 26 00:01:15,850 --> 00:01:21,160 The product owner also maintains the priority order in the backlog. 27 00:01:21,160 --> 00:01:24,570 An advantage of a product backlog that is printed on cards 28 00:01:24,570 --> 00:01:26,690 is that it lends itself to sorting. 29 00:01:26,690 --> 00:01:29,910 The product owner can hold two items in their hand and 30 00:01:29,910 --> 00:01:34,260 ask themselves the question, which of these has a higher priority? 31 00:01:34,260 --> 00:01:38,860 By repeating this question and comparing items in sequence, higher priority items 32 00:01:38,860 --> 00:01:43,340 bubble up through the list, while lower priority items move lower. 33 00:01:43,340 --> 00:01:45,990 When the product backlog is on the wall for everyone to see, 34 00:01:45,990 --> 00:01:51,030 it provides transparency to the team, and even to the organization. 35 00:01:51,030 --> 00:01:53,210 Everyone can see what the team will be working on. 36 00:01:53,210 --> 00:01:58,160 A common question is, when is the product gonna have this feature? 37 00:01:58,160 --> 00:02:00,170 With a visible product backlog, 38 00:02:00,170 --> 00:02:04,620 stakeholders can see where each feature sits in the product backlog. 39 00:02:04,620 --> 00:02:07,660 They can talk to the product owner if they think a particular item 40 00:02:07,660 --> 00:02:09,840 deserves a higher priority. 41 00:02:09,840 --> 00:02:13,310 The product owner is constantly trying to gather information 42 00:02:13,310 --> 00:02:16,120 about the priority of items in the backlog. 43 00:02:16,120 --> 00:02:20,960 They have conversations with stakeholders, customers, support representatives, and 44 00:02:20,960 --> 00:02:24,170 anyone else who can help them understand the value and 45 00:02:24,170 --> 00:02:26,610 priority of items in the backlog. 46 00:02:26,610 --> 00:02:28,210 As we learned in sprint planning, 47 00:02:28,210 --> 00:02:31,220 the products backlog feeds into the sprint backlog. 48 00:02:32,390 --> 00:02:35,490 Items are taken from the top of the product backlog where 49 00:02:35,490 --> 00:02:38,310 they have the highest priority and accepted into a sprint. 50 00:02:39,350 --> 00:02:41,590 A team can set aside space on the wall for 51 00:02:41,590 --> 00:02:45,660 the sprint backlog where they can easily see all the items of the current sprint. 52 00:02:46,810 --> 00:02:50,950 Having the sprint backlog visible is very important during the sprint, 53 00:02:50,950 --> 00:02:53,920 as we will learn shortly when we look at the task board.