# Planning Poker - Apps on Google Play.

To play estimation poker, each development team member will need a deck of estimation poker cards. The numbers on these cards, called story points, often use the Fibbonacci sequence. The development team can also use doubling decks, in which each subsequent number is twice the value of the previous number, or affinity decks containing t-shirt sizes that the team can use for relative estimation.

During planning poker, a product owner should explain the user stories to the development team, but he or she should not try to unduly influence the development team's estimates.

Numbers on planning poker represent complexity of a task. You should not consider that a story with 8 as value is the double size in effort or time of a size 4 story for example. You could use as many different representations for these numbers as you want (like t-shirt sizes). You just need to have an idea that one value is more complex than another and there is another value that is even.

More details. Agile Poker is a flexible toolkit for estimating your backlog to get it ready for grooming and planning.Inspired by the most popular estimation methods, it derives the best scrum estimating practices from each of them. The app supports team managers in getting trustworthy estimates for accurate planning, by engaging all team members in the process.

So as you play planning poker, the goal is not to come up with perfect estimation. The idea is to understand the requirement in totality. Story point as a number is just a side-effect of planning poker exercise. More on Story Points and Agile Estimation. This post is a part of a blog post series on story points and agile estimation.

Planning Poker Technique. In Planning Poker Estimation Technique, estimates for the User Stories are derived by playing planning poker. The entire Scrum Team is involved and it results in quick but reliable estimates. Planning Poker is played with a deck of cards. As Fibonacci sequence is used, the cards have numbers - 1, 2, 3, 5, 8, 13, 21, 34.

You might be wondering why you would want alternatives to planning poker. It’s not a bad system, but there are some problems with it. It is slow. It can take a long time to do planning poker estimation. I’ve seen sessions go for two or three hours, and it’s not fun. Throwing down cards is fun at first but it gets old really fast. Bickering over whether something is a 2 or a 3 is boring.

Story points and planning poker. Teams starting out with story points use an exercise called planning poker. At Atlassian, planning poker is a common practice across the company. The team will take an item from the backlog, discuss it briefly, and each member will mentally formulate an estimate. Then everyone holds up a card with the number that reflects their estimate. If everyone is in.

PlanITpoker is a cool on-line planning poker app that helps Agile project teams estimate projects easily. With a one click signup and always free, Try it today!

During sprint planning in SCRUM, poker-like cards are used as a unit of measure for estimating the “size” of a task. The points assigned to the task will help the team estimate how long it will take to complete each task: how difficult it is likely to be, and what will be included in the next sprint, based on this estimation. Not sure if you should be using Agile or Lean planning.

Story Points to Ideal Days. Ask Question Asked 7 years, 3 months ago.. Now i wanted to use Planning Poker, User Stories and Story Points with a proper Sprint Board and to capture the required data (story points) to measure our Velocity. My constraints are they must fit within this Plan Driven system described earlier. What I'm trying to ask really is can i use Story Points within this.