Poker Scale: Straight Flush. Five cards in numerical order, all of identical suits. In the event of a tie: Highest rank at the top of the sequence wins.
Planning Poker® in Scrum brings together multiple expert opinions for the agile estimation of a project. In this type of agile planning, we include everyone from programmers, testers and database engineers to analysts, user interaction designers and more. Because these team members represent all disciplines on a software project, they’re better suited to the estimation task than anyone else.
To get started with Planning Poker with your team, you can purchase Planning Poker cards from Mountain Goat Software. Or, play Planning Poker online for free.
- Important is that the team shares a common understanding of the scale it uses, so that every member of the team is comfortable with it. Planning Poker® / Scrum Poker. One commonly used method during the estimation process is to play Planning Poker® (also called Scrum Poker).
- VpFREE2 has 11 unique pay tables for the Super Aces (aka: SA) video poker game. Of these, vpFREE2 considers 6 games 'good' or 'playable', under typical circumstances, with a return of at least 99%, including SA (FP).
- Pain scale results can help guide the diagnostic process, track the progression of a condition, and more. There are at least 10 pain scales in common use, which are described below. They tend to fall into certain categories: Numerical rating scales (NRS) use numbers to rate pain.
How Does Planning Poker Work?
At the start of this agile planning exercise, each estimator is given a deck of Planning Poker cards. Each card has one of the valid estimates on it, for example: 0, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100 and infinity.
For each user story or theme to be estimated, a moderator (usually the product owner or an analyst) reads the description. There will be some discussion, where the product owner answers any questions the estimators have. But the goal of Planning Poker in Scrum is not to derive an estimate that will withstand all future scrutiny. Instead, we want a valuable estimate that can be arrived at inexpensively.
After discussion, each estimator privately selects a Planning Poker card representing his or her agile estimation. Once each estimator has made a selection, cards are simultaneously turned over and shown so that all participants can see one another’s estimate.
Estimates will likely differ significantly. And that’s OK. The highest and lowest estimators explain their perspective so that the team can know where they’re coming from. The moderator takes notes during this agile planning session that will be helpful when the story is programmed and tested.
After discussion, each estimator re-estimates by selecting a card. Often, the estimates will converge by the second round. If not, repeat the process until the team agrees on a single estimate to use for the story or these. It rarely takes more than three rounds in agile estimation to reach the goal.
Tips for Planning Poker in Scrum
Here’s some tips for common challenges in Planning Poker:
- Keep discussions productive: Consider purchasing a two-minute sand timer, and allowing anyone in the meeting to start it at any time. When the sand runs out, the next round of Planning Poker cards is played. This helps teams learn to estimate more rapidly within agile planning.
- Break out into smaller sessions: It is possible to play Planning Poker with a subset of the team. It’s not ideal, but a good option if there are many stories to be estimated, as can often happen at the start of a new project.
- Choose the right time to play: Estimating teams will need to play Planning Poker at two different occasions. The first time, teams will usually estimate a large number of items before the project kicks off or during first iterations. The second time, teams need to put forth ongoing effort to estimate new stories identified during an iteration.
You can learn more about Planning Poker in detail in the Mountain Goat Software store or in Mike Cohn’s book, Agile Estimating and Planning.
Scrum@Scale At Work
Scrum@Scale naturally extends the core Scrum framework to deliver better results across any organization. Scrum@Scale provides the structure for systems and processes to grow organically out of the unique conditions your organization has. It was created by Dr. Jeff Sutherland, the co-creator of Scrum and the Scrum Guide.
Take A Class
Become A Trainer
Launch A Transformation
Poker Scale Of Hands
Why Scrum@Scale?
The pain of decision latency is costly.
The pain of course-correcting is palpable.
Poker Scale
By remaining agile in times of uncertainty and innovating and accelerating when others stall in indecision. Scrum@Scale provides a framework to help you do just that.
The Scrum@Scale framework is a natural extension of the Scrum framework. It is a framework that empowers organizations to achieve business agility and deliver greater impact by scaling the Scrum framework out to teams of teams. Rather than trying to apply a ‘one-size-fits-all,’ turnkey solution to your organization, Scrum@Scale provides a lightweight, adaptable framework that has the ability to adjust to your context, making it customizable to many different industries.
Scrum@Scale provides the tools organizations need in order to produce high-performing teams of teams. It allows them to deliver value to the customer while supporting their teams to work at a sustainable pace.
When you’re ready to scale, there’s only one logical choice. Scrum@Scale.
Does this sound familiar?
Poker Scale Winning Hands
Communication breakdowns
Frustrated team members
Chasing deadlines
Missed deliverables
Budget creep