Having problems with message search?
Originally we don't have this meeting, and the whole team discuss with PO to clarify the requirement, it is waste.
Therefore in this pre-planning meeting, 2-3 people who foresee will work on this tasks with join this discussion, and bring feedback to the team. It save a lot of time practically. And this is not official meeting, normally people will stay up to discuss.
rgs/larry
On Mon, Jul 6, 2009 at 12:41 PM, Bas Vodde <basv@...> wrote:
Hi Larry,I suppose your "pre-planning meeting" is similar as a backlog
> In the pre-planning meeting, we notice 2-3 people discuss with PO
> are good enough, then no planning poker normally needed.
>
refinement (or grooming) meeting? (meaning looking abour 2-3 sprints
ahead).
Why did you 'optimize' it to have only 2-3 people, this will lead to
another hand-off to the rest of the team later?
Bas
>
>
> .. 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.
>
>
--
True software development embraces consistent inconsistency.
Offline 
Send Email