Backlog Prioritization
This is the truth hour for the product owner as it is where the prepared user stories meet the developers and get the feedback whether the tasks are ready for estimation and delivery or not. Usually (but not always) the whole team is present for prioritizing so that later the whole team can take the commitment to deliver the sprint (as they were present when the tasks were discussed and have all the information required).
The items on the top of the product backlog are gone through in more detail, making sure all information required is in the story and estimated using planning poker (e.g. complexity points like 1,3, 5, 8 and 13). Items further down are discussed more briefly and given rough t-shirt estimations (e.g. Small, Medium, Large) to give the product owner first indications on size. The planning poker estimations are crucial for planning a few next sprints. Rough t-shirt estimations help in further story development and prioritization. It can often be that based on initial t-shirt estimation, a task gets deprioritized in the backlog as the benefit is (currently) not worth the effort required or is so small that it can jump to the top of the list.
Ideally, by the end of a prioritizing session, all the tasks in the product backlog have an estimation, some estimations have been updated in light of new information and the backlog is prioritized. Depending on the teams’ history and the product, full estimation and prioritization of the whole backlog can be difficult to achieve. The important thing to remember is that a bit more than one sprint worth of stories for the team needs to have detailed story point estimations. This is because only estimated stories can be added to the sprint backlog during the Scrum planning meeting.
Recommended Further Reading
The following materials may assist you in order to get the most out of this course: