1 00:00:00,580 --> 00:00:04,440 Today, we're sitting in on a team that is planning a sprint. 2 00:00:04,440 --> 00:00:07,700 They begin by setting a time box of two weeks, and 3 00:00:07,700 --> 00:00:11,050 reviewing their schedules to get a good sense of how much time 4 00:00:11,050 --> 00:00:14,280 each team member will be available during the sprint. 5 00:00:14,280 --> 00:00:17,520 Next, the product owner will refer to the product backlog, 6 00:00:17,520 --> 00:00:20,480 where they have assorted lists of product backlog items. 7 00:00:21,500 --> 00:00:25,000 These items are in priority order based on a product owner's understanding 8 00:00:25,000 --> 00:00:28,180 of their value to the business and to the customer. 9 00:00:28,180 --> 00:00:31,170 The product owner presents a sprint goal or theme. 10 00:00:31,170 --> 00:00:35,560 The sprint goal is an area of focus that will bring value to the product. 11 00:00:35,560 --> 00:00:39,270 Having this goal handy will help the team stay on track during the sprint. 12 00:00:40,270 --> 00:00:43,800 The items at the top of the product backlog support the sprint goal. 13 00:00:44,890 --> 00:00:49,020 The product owner reads a product backlog item aloud to the team. 14 00:00:49,020 --> 00:00:52,900 It includes the user story and the conditions of acceptance. 15 00:00:52,900 --> 00:00:56,660 Team members listen and ask clarifying question to ensure that everyone has 16 00:00:56,660 --> 00:00:59,710 a shared understanding of the item, and the work they are agreeing to. 17 00:01:00,840 --> 00:01:02,630 As the finish up with the item, 18 00:01:02,630 --> 00:01:06,380 the team comes to consensus on whether to bring the item into the sprint. 19 00:01:06,380 --> 00:01:10,650 An easier way to check for consensus is by a showing of thumbs. 20 00:01:10,650 --> 00:01:12,710 With thumbs up meaning yes, 21 00:01:12,710 --> 00:01:17,620 thumbs down meaning I have a concern, and a neutral thumb indicating 22 00:01:17,620 --> 00:01:21,270 that the team member is willing to accept the decision of the team. 23 00:01:22,540 --> 00:01:24,980 Okay, so notice here that the product owner and 24 00:01:24,980 --> 00:01:27,940 the scrum master are not part of this decision. 25 00:01:27,940 --> 00:01:30,830 This is because only development team members 26 00:01:30,830 --> 00:01:33,660 decide how much work they can commit to in a sprint. 27 00:01:33,660 --> 00:01:38,530 The product owner's role here is to present the highest priority items first, 28 00:01:38,530 --> 00:01:42,010 and to clarify the items to reach a shared understanding. 29 00:01:43,220 --> 00:01:47,460 The scrum master helps with estimating the team's availability, and 30 00:01:47,460 --> 00:01:51,150 identifying obstacles to the sprint that should be considered. 31 00:01:51,150 --> 00:01:55,120 When the development team accepts a product backlog item into the sprint, 32 00:01:55,120 --> 00:01:58,770 it is moved from the product backlog to the sprint backlog, and 33 00:01:58,770 --> 00:02:00,900 the team moves on to discuss the next item. 34 00:02:01,990 --> 00:02:06,450 This process continues item by item, until the team members decide 35 00:02:06,450 --> 00:02:09,670 they do not have the capacity to accept the next item into the sprint. 36 00:02:10,680 --> 00:02:13,510 When they team has reached the limit of what they can commit to, 37 00:02:13,510 --> 00:02:15,520 sprint planning is complete. 38 00:02:15,520 --> 00:02:19,850 The sprint backlog includes the work to be done along with the sprint goal. 39 00:02:19,850 --> 00:02:22,910 The sprint goal can help the team to stay on track, and 40 00:02:22,910 --> 00:02:25,230 remember the purpose of the sprint. 41 00:02:25,230 --> 00:02:29,610 If changes come up mid sprint, it can be helpful to have it as a reference for 42 00:02:29,610 --> 00:02:32,400 the team to decide if they are still effectively moving 43 00:02:32,400 --> 00:02:34,150 towards the sprint goal. 44 00:02:34,150 --> 00:02:38,200 When the team commits to a sprint, something important happens in scrum 45 00:02:38,200 --> 00:02:42,530 that you might not appreciate if you've worked on teams outside of scrum. 46 00:02:42,530 --> 00:02:44,750 The commitment to a sprint happens in two directions. 47 00:02:45,850 --> 00:02:49,770 The development team commits to completing the work within the time box, and 48 00:02:49,770 --> 00:02:54,400 the product owner commits to making no new requests of the team during this sprint. 49 00:02:54,400 --> 00:02:57,040 If someone important comes to a developer in mid sprint and 50 00:02:57,040 --> 00:03:00,400 says, wouldn't it be great if we added this feature, 51 00:03:00,400 --> 00:03:04,700 the developer can respond by saying that sounds important. 52 00:03:04,700 --> 00:03:07,940 You should probably talk to our product owner about that. 53 00:03:07,940 --> 00:03:10,950 This helps the team to avoid distractions as they work on 54 00:03:10,950 --> 00:03:13,050 items that have been thoughtfully prioritized. 55 00:03:14,220 --> 00:03:16,390 After planning the work to be done in the sprint, 56 00:03:16,390 --> 00:03:19,100 the team looks at how the work will be done. 57 00:03:19,100 --> 00:03:22,050 Product backlog items are broken out into tasks 58 00:03:22,050 --> 00:03:25,350 that can be picked up by individual team members. 59 00:03:25,350 --> 00:03:26,850 The set of tasks written for 60 00:03:26,850 --> 00:03:32,020 a given PBI should describe all the steps necessary for the item to be done. 61 00:03:32,020 --> 00:03:35,540 These tasks will get a lot of attention during the sprint and 62 00:03:35,540 --> 00:03:37,180 will be tracked on the task board.