The Sprint Planning Meeting

Who, What, When, Where, Why
The Sprint Planning Meeting is attended by the product owner, Scrum Master, and the entire Scrum Team. Outside stakeholders may attend by invitation of the team, although this is rare in most companies.

Two defined artifacts that result from a sprint planning meeting:

A sprint goal

A sprint backlog

A sprint goal is a short, one- or two-sentence, description of what the team plans to achieve during the sprint. It is written collaboratively by the team and the product owner. The following are typical sprint goals on an eCommerce application:

There are two parts in Sprint Planning Meeting

Part 1 – Prioritization 

What needs to be done by the end of this upcoming Sprint?

1. PO presents the ordered backlog items to the team.
2. Team discusses and understands the work for this Sprint.
3. Team forecasts and commits on the items that can be done.
4. Team creates the Sprint Goal for this Sprint.

Part 2 – Planning How will the chosen work get to done?

The output of the second planning meeting will be the Sprint Backlog.

1. Team arrives at the plan to get the items to done in a Sprint Backlog.
2. Team arrives at a design and work needed to achieve the Sprint goal.