Sprint Planning3:37 with Matt Anthes-Washburn
In Sprint Planning, the team commits to new work
Product Backlog Item (PBI): A description of a unit of work that is a candidate for a sprint. These often include User Stories, defects, and technical items.
Product Backlog: A prioritized list of Product Backlog Items that are candidates for sprints
Sprint Backlog: A group of Product Backlog Items that have been accepted into the current sprint.
Today, we're sitting in on a team that is planning a sprint. 0:00 They begin by setting a time box of two weeks, and 0:04 reviewing their schedules to get a good sense of how much time 0:07 each team member will be available during the sprint. 0:11 Next, the product owner will refer to the product backlog, 0:14 where they have assorted lists of product backlog items. 0:17 These items are in priority order based on a product owner's understanding 0:21 of their value to the business and to the customer. 0:25 The product owner presents a sprint goal or theme. 0:28 The sprint goal is an area of focus that will bring value to the product. 0:31 Having this goal handy will help the team stay on track during the sprint. 0:35 The items at the top of the product backlog support the sprint goal. 0:40 The product owner reads a product backlog item aloud to the team. 0:44 It includes the user story and the conditions of acceptance. 0:49 Team members listen and ask clarifying question to ensure that everyone has 0:52 a shared understanding of the item, and the work they are agreeing to. 0:56 As the finish up with the item, 1:00 the team comes to consensus on whether to bring the item into the sprint. 1:02 An easier way to check for consensus is by a showing of thumbs. 1:06 With thumbs up meaning yes, 1:10 thumbs down meaning I have a concern, and a neutral thumb indicating 1:12 that the team member is willing to accept the decision of the team. 1:17 Okay, so notice here that the product owner and 1:22 the scrum master are not part of this decision. 1:24 This is because only development team members 1:27 decide how much work they can commit to in a sprint. 1:30 The product owner's role here is to present the highest priority items first, 1:33 and to clarify the items to reach a shared understanding. 1:38 The scrum master helps with estimating the team's availability, and 1:43 identifying obstacles to the sprint that should be considered. 1:47 When the development team accepts a product backlog item into the sprint, 1:51 it is moved from the product backlog to the sprint backlog, and 1:55 the team moves on to discuss the next item. 1:58 This process continues item by item, until the team members decide 2:01 they do not have the capacity to accept the next item into the sprint. 2:06 When they team has reached the limit of what they can commit to, 2:10 sprint planning is complete. 2:13 The sprint backlog includes the work to be done along with the sprint goal. 2:15 The sprint goal can help the team to stay on track, and 2:19 remember the purpose of the sprint. 2:22 If changes come up mid sprint, it can be helpful to have it as a reference for 2:25 the team to decide if they are still effectively moving 2:29 towards the sprint goal. 2:32 When the team commits to a sprint, something important happens in scrum 2:34 that you might not appreciate if you've worked on teams outside of scrum. 2:38 The commitment to a sprint happens in two directions. 2:42 The development team commits to completing the work within the time box, and 2:45 the product owner commits to making no new requests of the team during this sprint. 2:49 If someone important comes to a developer in mid sprint and 2:54 says, wouldn't it be great if we added this feature, 2:57 the developer can respond by saying that sounds important. 3:00 You should probably talk to our product owner about that. 3:04 This helps the team to avoid distractions as they work on 3:07 items that have been thoughtfully prioritized. 3:10 After planning the work to be done in the sprint, 3:14 the team looks at how the work will be done. 3:16 Product backlog items are broken out into tasks 3:19 that can be picked up by individual team members. 3:22 The set of tasks written for 3:25 a given PBI should describe all the steps necessary for the item to be done. 3:26 These tasks will get a lot of attention during the sprint and 3:32 will be tracked on the task board. 3:35
You need to sign up for Treehouse in order to download course files.Sign up