Based on our practice the planning poker helps to find out the gap between
different members in understanding of requirement as well as design.
Even though sometimes some members feel they have good understanding of
requirement, sometimes the poker exercise show there are still obvious
difference there.

Also usually I don't feel there is lot time spent on the vote itself, instead
the time spent is on the justification after gap found.
If team is really on the same page, the process is fast; if it takes long, the
justification is very valuable anyway.

For sure, we take compromise in some case. For example, after 2 rounds, if half
of team is 2 points and half of team is 3 points, we take 3 points.

--- In ScrumChina@yahoogroups.com, Larry Cai <larry.caiyu@...> wrote:
>
> Hi:
>
> I start to confuse when to use planning poker.
>
> Originally we use planning poker in scrum planning meeting 1, and notice it
> cost a lot of time, then we arrange pre-planning meeting, it was hold 2-3
> days before planning meeting 1.
>
> In pre-planning meeting, the team members and PO will clarify the
> requirement and estimate the story points in advance.
> In planning meeting, the whole team and PO double check the story point and
> make commitment.
>
> In the pre-planning meeting, we notice 2-3 people discuss with PO are good
> enough, then no planning poker normally needed.
>
> .. so when we shall use planning poker.
>
> I want to check whether we missed some nice practice for planning poker.
>
> rgs/larry
> --
>
> True software development embraces consistent inconsistency.
>