During this first phase of Sprint Planning, we focus on what we think we can complete in the coming Sprint. It is a forecast by our Development Team that determines which User Stories can be included in this Sprint Backlog. The Product Owner and the Scrum Master aren't allowed to participate in the forecast as such, but they will be advising the team on User Story details and what their priorities are.

Starting with the backlog in priority order, and in a similar way to Product Backlog refinement, present the first story card to your team. The story card should be read aloud and then placed in the center of the table. Your Development Team should then decide if the User Story is achievable as part of this Sprint.

You should continue selecting story cards from the top of the backlog, reading them out and placing them in them on the Sprint Backlog until your Development Team think they won't be able to achieve any more in this Sprint.

At the end of this stage, you will have a line of User Stories sitting in the middle of the table, ordered from top to bottom in priority order.