0 True To create useful relative sizes for our estimation units, we can use the Fibonacci Sequence. False : Planning Poker estimates cannot be changed during a Sprint. 0 True Using Planning Poker for estimating promotes quick decisions without a lot of discussion. True Human brains are intuitively able to compare sizes of things, which helps in relative estimation. : Planning Poker is only used for development tasks. Once a team has estimated its stones, it is ready to schedule them. : 'Dog sizes\" and 'tshirt sizes\" are just as valid units as story points. Agile uses 'justintime' estimating to reduce time wasted on estimating user stories that may not be developed. : We derive size and estimate duration. We ignore quality considerations when estimating stories. Testers should not be included in the Planning Poker team. 3 The number of story points a team can deliver per iteration is called \"team revolutions.r 0 0 0 0 0 0 0 0 To compare effort, the team chooses a baseline story against which all the other stories will be compared. Estimation is easy. Planning Poker uses absolute measures to estimate effort. Teams must use story points as their units of estimation. Planning Poker takes place during Iteration Reviews. Story size estimates have to take account of complexity and risk. Once team members have each revealed their estimation dun'ng Planning Poker, the results are averaged. The Product Owner is not needed in Planning Poker