TL;DR
https://www.mountaingoatsoftware.com/agile/scrum/sprint-planning-meeting
Output:
- A sprint goal
- A sprint backlog
A sprint backlog is a list of the product backlog items the team commits to delivering plus the list of tasks necessary to delivering those product backlog items. Each task on the sprint backlog is also usually estimated.
https://www.mountaingoatsoftware.com/blog/2-times-to-play-planning-poker-and-1-time-not-to
Estimating backlog objectives:
- They allow the product owner to prioritize the product backlog
- They allow the company to make longer-term predictions.
A team should estimate early enough to fulfill these two needs but no earlier than necessary.
When to use:
[...] should play Planning Poker after a meeting like a story-writing workshop in which they have written a large number of product backlog items. I recommend doing such workshops about quarterly.
The second time a team should play Planning Poker is once per sprint. Some teams will do this as part of a regular product backlog grooming meeting, and I think that’s fine if the whole team participates in grooming.
But the team should avoid estimating so late in the sprint that the product owner cannot consider the newly estimated items when deciding what the team will work on in the next sprint.
When not to use:
There’s only one time when I think it’s a mistake to play Planning Poker: at the start of the sprint planning meeting.
Some product owners may be able to rejigger priorities on the fly, but even they could, probably do so better with a little more time to think.
with Planning Poker, they (the Team) are asked instead to think at a high-level and put a rougher, less precise estimates on the user stories. Many team members seem to have a hard time giving rough estimates in a meeting in which they will next be asked to give much more precise estimates of tasks.