Poker Face Table Size

• Poker Face Table Size Table
• Poker Face Table Size Chart
• Poker Face Table Size Calculator
• Poker Face Table Sizes

Almost as important as selecting the most suitable online poker room, is the selection of the best poker table to play at. Once again the profitability of each table can vary massively, so is it just luck whether or not you pick the most profitable?

Well no, there is a logic behind it and in this lesson we are going to look at how to select the most profitable cash game table from the lobby.

What are we Looking for?

We’re looking for the fish, plain and simple. We’re looking for any signs of bad players who play too many hands against the odds and chase, hoping to hit cards on the flop, turn or river to make their hand irrespective of how unlikely it is to happen.

1. Pokerface is a Group Video Chat Poker Game that lets you play with your friends and meet new ones. Join Pokerface, see your friends, and chat with them live! Have a real poker night from anywhere in the world! Download Poker Face Now, Invite your friends, and get up to 1,000,000 welcome bonus chips. Featured on CNET.com, Geekdad.com, MSN.com, Yahoo News, and many more!
2. The Rex dresses up his poker face. And so, on Monday, March 23, a full table’s worth of us fired up the app on our smartphones or our tablets or (running it on an Android.
3. Poker contains a lot of repetitive math, especially when studying poker hands away from the table. While you can use software to do a lot of this math, sometimes a good ‘ol fashioned spreadsheet is the best way to visualize and play with the numbers.
4. A typical casino poker table has a length of between 92 and 104 inches (234 and 264 cm), a width of 44 inches (112 cm), and a height of 30 inches (76 cm). You can expect to also add 4 inches (10 cm) to the length and width for the outer “racetrack” railing.

The table above shows 3 weaker players, each has been identified by having a stack size smaller than 100 big blinds. Typically strong winning players will sit in with a stack size of 100 big.

Now in a live casino the only way to do this would be to stand and observe the tables and spot the one with the players who are chasing.

Luckily with online poker this guesswork and time consuming observation is taken away from us, as we are given table statistics in the lobby for each and every table, which is extremely helpful seeing as there can be hundreds of tables to choose from.

So How do we Choose the Most Profitable Table?

The first step is to ensure that you are looking at the right tables. In the first stage of this course and the Poker Bankroll Challenge you will be playing at the 5cent / 10cent stake level and throughout this course you will be focused on the No Limit Texas Holdem ring (cash) game tables.

So, from the lobby, make sure you are looking at the ring game tables, and click on the Holdem tab and select the No Limit button just underneath. The tables we are looking for are the 5c/10c tables with 9 players on a table. Throughout this course we will be playing on full tables of 9 or 10 player tables so you can ignore the short-handed (6 player) tables for now.

As you look at the tables available you will see a number of statistics here, lets have a quick look at what they mean:

• Players – The number of players sat at the table and the maximum players, eg: “7/9” = 7 players sat down with 2 spare seats.
• Stakes – The size of the small blind and big blind and subsequent bets, eg: “5c/10c” = small blind is 5 cents ($0.05) and the big blind is 10 cents ($0.10).
• Limit – The type of Poker Betting Limit of the game being played, either No Limit, Pot Limit or Limit (Fixed) – eg: “NL” = No Limit
• Type – Poker room specific which will show icons for the type of game it is, for example there might be an icon for webcam poker tables, usually there is a legend explaining the icons at the bottom of the lobby.
• Average Pot – Self explanatory, keeps track of all the winning pot values and provides an average pot size as a statistic for the table.
• Players / Flop – The average number of players who see the flop, ie: the players that are not folding before the flop and at least call the pre flop bet and see the cards on the flop, eg: “45%” = at a full 9 man table this would indicate that on average 4 players (9 x 45%) see each flop, meaning there is at least 4 big blinds in most pots.
• Hands / Hour – This is an indication of the speed of the table and displays the average number of hands that are dealt in each hour, the higher the number the faster the table is acting and getting through more hands per hour.
• Wait – If a table is full then you can sign up for the waiting list for that table, as a player leaves, that seat is offered to the next person on the waiting list. This statistic shows you how many people are currently on the Waiting List.

Players per Flop: The Fish-o-meter

The statistic we are interested in to start with is the % of players seeing the Flop, or the Players per Flop column. What this number is telling us is the average % of the players at the table who see each flop. This is our Fish-o-meter as the basic rule of thumb here is that the higher this number is, then the more fish (bad players) the table contains.

Poker Face Table Size Table

Why? Because as you have already learnt, fish chase bad cards, they play hands that they should just fold, and hence you get more players trying to play each flop without any kind of proper hand selection.

A table with a lower percentage would indicate better players, so if you saw a table with 5% then this table has a lot of better players, who play hands selectively before the flop and don’t play with hands they shouldn’t.

As you can see from the screenshot above, there is one table that stands out above the others in the list with a 45% players/flop statistic – this is a really really good table to sit down at, and I would be getting my name on that table’s waiting list as soon as possible.

What we are looking for is tables with a Plrs/Flop % higher than 20%. If you can get greater than 30% then that is even better. The higher the better and the more fishy table.

The screenshot above was taken at 888 Poker and as you can see there are lots of tables above 20% and some over 30%, culminating with that fish stinking 45% table. It’s a similar case at Bovada, and just goes to backup the results of our tests that there are lots of inexperienced players at these two sites where we can make profit.

Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used to estimate effort or relative size of development goals in software development. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent for subsequent estimates.

Planning poker is a variation of the Wideband delphi method. It is most commonly used in agile software development, in particular in Scrum and Extreme Programming.

The method was first defined and named by James Grenning in 2002^[1] and later popularized by Mike Cohn in the book Agile Estimating and Planning,^[2] whose company trade marked the term ^[3] and a digital online tool.^[4]

Process[edit]

Rationale[edit]

The reason to use planning poker is to avoid the influence of the other participants. If a number is spoken, it can sound like a suggestion and influence the other participants' sizing. Planning poker should force people to think independently and propose their numbers simultaneously. This is accomplished by requiring that all participants show their card at the same time.

Equipment[edit]

Planning poker is based on a list of features to be delivered, several copies of a deck of cards and optionally, an egg timer that can be used to limit time spent in discussion of each item.

The feature list, often a list of user stories, describes some software that needs to be developed.

The cards in the deck have numbers on them. A typical deck has cards showing the Fibonacci sequence including a zero: 0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89; other decks use similar progressions with a fixed ratio between each value such as 1, 2, 4, 8, etc.

The reason for using the Fibonacci sequence instead of simply doubling each subsequent value is because estimating a task as exactly double the effort as another task is misleadingly precise. A task which is about twice as much effort as a 5, has to be evaluated as either a bit less than double (8) or a bit more than double (13).

Several commercially available decks use the sequence: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100, and optionally a ? (unsure), an infinity symbol (this task cannot be completed) and a coffee cup (I need a break, and I will make the rest of the team coffee). The reason for not exactly following the Fibonacci sequence after 13 is because someone once said to Mike Cohn 'You must be very certain to have estimated that task as 21 instead of 20.' Using numbers with only a single digit of precision (except for 13) indicates the uncertainty in the estimation. Some organizations^[which?] use standard playing cards of Ace, 2, 3, 5, 8 and king. Where king means: 'this item is too big or too complicated to estimate'. 'Throwing a king' ends discussion of the item for the current sprint.

Smartphones allow developers to use mobile apps instead of physical card decks. When teams are not in the same geographical locations, collaborative software can be used as replacement for physical cards.

Procedure[edit]

At the estimation meeting, each estimator is given one deck of the cards. All decks have identical sets of cards in them.

The meeting proceeds as follows:

• A Moderator, who will not play, chairs the meeting.
• The Product Owner provides a short overview of one user story to be estimated. The team is given an opportunity to ask questions and discuss to clarify assumptions and risks. A summary of the discussion is recorded, e.g. by the Moderator.
• Each individual lays a card face down representing their estimate for the story. Units used vary - they can be days duration, ideal days or story points. During discussion, numbers must not be mentioned at all in relation to feature size to avoid anchoring.
• Everyone calls their cards simultaneously by turning them over.
• People with high estimates and low estimates are given a soap box to offer their justification for their estimate and then discussion continues.
• Repeat the estimation process until a consensus is reached. The developer who was likely to own the deliverable has a large portion of the 'consensus vote', although the Moderator can negotiate the consensus.
• To ensure that discussion is structured; the Moderator or the Product Owner may at any point turn over the egg timer and when it runs out all discussion must cease and another round of poker is played. The structure in the conversation is re-introduced by the soap boxes.

The cards are numbered as they are to account for the fact that the longer an estimate is, the more uncertainty it contains. Thus, if a developer wants to play a 6 he is forced to reconsider and either work through that some of the perceived uncertainty does not exist and play a 5, or accept a conservative estimate accounting for the uncertainty and play an 8.

Benefits[edit]

A study by Moløkken-Østvold and Haugen^[5] reported that planning poker provided accurate estimates of programming task completion time, although estimates by any individual developer who entered a task into the task tracker was just as accurate. 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. Planning poker was considered by the study participants to be effective at facilitating team coordination and discussion of implementation strategies.

See also[edit]

Poker Face Table Size Chart

• Comparison of Scrum software, which generally has support for planning poker, either included or as an optional add-on.

References[edit]

1. ^'Wingman Software Planning Poker - The Original Paper'. wingman-sw.com. Retrieved 5 July 2017.
2. ^Mike Cohn (November 2005). 'Agile Estimating and Planning'. Mountain Goat Software. Retrieved 1 February 2008.
3. ^'Planning poker - Trademark, Service Mark #3473287'. Trademark Status & Document Retrieval (TSDR). 15 January 2008. Retrieved 26 May 2014.
4. ^Cohn, Mike. 'Planning Poker Cards: Effective Agile Planning and Estimation'. Mountain Goat Software. Mountain Goat Software. Retrieved 30 March 2016.
5. ^K Moløkken-Østvold, NC Haugen (10–13 April 2007). 'Combining Estimates with Planning Poker—An Empirical Study'. 18th Australian Software Engineering Conference. IEEE: 349–58. doi:10.1109/ASWEC.2007.15. ISBN978-0-7695-2778-9.

Poker Face Table Size Calculator

• Mike Cohn (2005). Agile Estimating and Planning (1 ed.). Prentice Hall PTR. ISBN978-0-13-147941-8.

Poker Face Table Sizes