Sprint Planning Part Two focuses on how to implement the items that the Team decides to take on.
The Team forecasts the amount of items they can complete by the end of the Sprint, starting at the
top of the Product Backlog (in others words, starting with the items that are the highest priority for
the Product Owner) and working down the list in order. This is a key practice in Scrum: The Team decides
how much work it will complete, rather than having it assigned to them by the Product Owner. This makes for a
more reliable forecast because the Team is making it based on its own analysis and planning. While the
Product Owner does not have control over how much the Team signs up for, he or she knows that the
items are drawn from the top of the Product Backlog – in other words, the items that he or she has
rated as most important. The Team has the ability to lobby for items from further down the list; this
usually happens when the Team and Product Owner realize that something of lower priority fits easily
and appropriately with the high priority items.