![]() ![]() The point of the exercise is to give everyone a voice, so pulling rank is not allowed! Figure out if the task or user story needs to be broken down or a better description, or if one of the players has misunderstood something. It is very important that even if it’s the most junior member of the team who made the non-matching estimate that he should have his soapbox to justify things. When this happens, the high estimator and the low estimator are asked to justify their estimates. For example, one person might think that to show a list of products she would also need to include the search and sort features for the list page someone else might not have factored that in to his estimate. If the numbers differ wildly, then something is amiss with the task or people have made different assumptions about it. If the numbers are all the same or similar, then accept that (or average them) as the estimate and move on to the next task. On a given signal, everyone reveals their card at the same time. The facilitator describes the task to be estimated and everyone selects, but does not show, the card that represents their chosen estimate. Different teams play with different variations, for example it is fine to treat them as hours spent coding to get started. These are measurements for a task in story points (story points are an imaginary unit, where the simplest task is half a story point, and the bigger the task the more points it is worth). The exact selection may differ, but typically you’ll have cards with the values 1/2, 1, 2, 3, 5, 8, 20, and a question mark or unknown value. ![]() You can purchase special Planning Poker cards (I have a rather nice set from moo.com), make them from index cards, or improvise with an iPhone or Android card app. a list of tasks you want to estimates for.some players (two minimum, three is awesome, and it works with up to five or so).In this article I’ll show you how using Planning Poker with a team can help you make better estimates for the projects you work on. The unknown elements cause different developers to make different assumptions the task needs to be amended until everyone is able to estimate. When this happens it means the task is not well defined. It becomes possible to spot tasks where the developers’ estimates differ wildly from one another.Since developers tend to under- or over-estimate, you may need to adjust this number. You can look at the various estimates for the same task and gain a clear sense of how long this task will take.When this is the case, Planning Poker enables you to do two very valuable things: When you use Planning Poker to estimate your project, it is very important to give each developer a voice allow them to make their own estimates without being influenced by the opinions or agendas of anyone else. It comes from the world of Agile software development, but can be used in isolation or with other methodologies as well. Planning Poker is an estimation technique which helps developers provide good estimates for project tasks. ![]()
0 Comments
Leave a Reply. |