Learn Poker Video Source & Info:
eLearning on Agile Estimating and Planning: http://www.mountaingoatsoftware.com/elearning
An excerpt from Mike Cohn’s eLearning video training course on Agile Estimating and Planning. In this video, Mike explains how to play Planning Poker to collaboratively estimate an agile or Scrum team’s product backlog. Earn four PDUs and a certificate of completion after successfully completing the full course.
Course may be downloaded or streamed. Learn more at http://www.mountaingoatsoftware.com/elearning
Source: YouTube
Thanks for the almost real-life planning poker game round showcase…
How does this technique work with teams split into different functions like a frontend, backend, UI/UX and testing team? A particular user story might be a 2 for the frontend team, but a 5 for the backend team and a 8 for the UI/UX or testing team. So in this case, I don't suppose that everyone will converge on a common figure. So should we run the poker estimation individually by teams and if yes how would be consolidate it to arrive at a story size? Or is there a different approach to solving this?
Thanks Mike. Do we need the size 0 in the cards? If it refers to most simple tasks, then I can drop it from the cards. May I start with 1?
what are these numbers? duration of hours or days ?
Thanks Mike for this valuable information. I have a doubt , if I want to pick a card say 5 points then does that mean it includes effort for build, unit testing and other testings( like Integration and QA).
I hope I am clear with my question.
Thanks !
Hi Mike, why do we use Poker card in planning ? What does it mean ?