It also subtly takes the focus off of swarming and puts attention toward a developer per story. 5 to 15 stories per sprint is about right. Four stories in a sprint may be okay on the low end from time to time. Twenty is an upper limit for me if we're talking about a Web team with lots of small changes to do.
Further to this, what is the intended outcome of planning poker?
The intended outcomes of planning poker are to: Leverage the knowledge and input of all team members into the estimation process. Achieve a team-based consensus on estimates.
Plus, who is responsible for assigning a priority to user stories? As discussed earlier, project stakeholders are responsible for prioritizing requirements. Note that in Figure 2 a numerical prioritization strategy was taken (perhaps on a scale of 1 to 20) whereas in Figure 3 a MoSCoW (Must Should Could Won't) approach was used.
For that reason, who participates in planning poker?
Also in a Planning Poker meeting will be the ScrumMaster. A team's ScrumMaster is its facilitator, and so the ScrumMaster should participate in all regularly scheduled meetings, and a Planning Poker session is no exception.
How do I start planning poker?
In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. The cards are revealed, and the estimates are then discussed.