A high estimate ( 20 for example) usually means that the story is not well understood in detail.
Renaissance Software Consulting (April 2002).
Mr D admits spinal tap slot review that he was sleeping and asks what the story is about.Smaller stories can be estimated in greater detail.Units used vary - they can be days duration, ideal days or story points.Why the strange number series?
Mrs C realizes that, with the design that Mr A presented, the story might be smaller than.
Repeat the estimation process until a consensus is reached.
"Throwing a king" ends discussion of the item for the current sprint.OK, not complete convergence.Everybody has to present a card, so Mr D and E wake.They start doubting their own estimates.Tasks discussed during planning poker rounds took longer to complete than those not discussed and included more code deletions, suggesting that planning poker caused more attention to code quality.Instead they all have to present a card, face down, containing their estimate.This makes B and C confused.Procedure edit At the estimation meeting, each estimator is given one deck of the cards.The coffee cup card means Im too tired to think.Scale Your Team With CodeFirst Developers.The product owner says: Once again, the team starts thinking about how long the story will take.After some discussion, Mr A realizes that he has forgotten some important tasks that need to be included in the story.
Explore Features "Hundreds of agile teams use Planning Poker every day.