In this video, create a task board.
- Sprint planning is when the team scoops stories … out of the product backlog and put them into the sprint. … The product owner begins by going through … the product backlog and presenting what they want … done in the sprint. … The development team decides how much of what the product … owner wants, they can deliver. … It should be a back and forth between what to do … and what can be done. … Often the details about the stories get resolved … in sprint planning. … Up until now, the stories have really been only considered … in the abstract, but the product owner created … the user stories, maybe the were organized into large groups … like epics, and then the development team … estimated the user stories with a round of planning poker. … This was all done at a very high level. … Now the team is very interested in what it takes … to deliver their stories. … An abstract story suddenly becomes … a practical implementation. … Some teams will create a separate sprint backlog. … The sprint backlog is a subset of stories …
- Explain how a sprint differs from a traditional project.
- Name three user roles.
- Define the acronym INVEST and explain its purpose.
- List three main sections of a project charter.
- Identify the benefits of planning poker.
- Recall the challenges associated with the sprint backlog.