The Coffee Cup and Infinity Symbol

The Coffee Cup and Infinity Symbol: Planning Poker Cards Explained

Most teams using Planning Poker are doing it wrong.

They’re arguing about numbers, not decisions. They’re obsessing over “Is this a 5 or an 8?” while ignoring the two most powerful cards in the deck: the coffee cup and the infinity symbol.

If your Planning Poker sessions feel like:

Endless debates
Repeated “Let’s just call it a 3 and move on”
Estimates that never match reality
…then this is for you.

Let’s unpack what those “weird” cards actually mean—and how to use them to run estimation sessions that are fast, honest, and actually useful.

What Planning Poker Is Really For (Hint: It’s Not About Accuracy)

Planning Poker is not about predicting the future with perfect precision. That’s a fantasy.

Studies across hundreds of teams show that story estimates are often off by 30–50% on average. That’s not a bug; it’s the nature of knowledge work.

The real purpose of Planning Poker is to:

Expose misunderstandings early
Reveal hidden complexity and risk
Force alignment on what “done” actually means
Help you slice work into something your team can actually finish

The numbers are just a proxy. The conversation is the point.

And that’s exactly where the coffee cup and infinity symbol shine.

The Planning Poker Deck: More Than Just Numbers

Most decks include:

Fibonacci-ish numbers: 1, 2, 3, 5, 8, 13, 20, 40, 100
A “?” card
A coffee cup (or break symbol)
An infinity (∞) symbol

Teams usually understand the numbers. They often misuse the “?” card. And they almost completely ignore coffee and infinity.

That’s a missed opportunity.

The Coffee Cup Card: The Signal You’re Ignoring

The coffee cup card is not just “I need caffeine.” It’s a signal about team health and meeting quality.

What the Coffee Cup Really Means

Used well, the coffee cup card is a way to say:

“We’re mentally saturated. This conversation isn’t productive anymore.”
“We need a break before we start phoning in estimates.”
“This meeting is dragging; let’s reset.”

Think of it as a safety valve for cognitive load.

There’s a reason pilots, surgeons, and air traffic controllers work in tightly controlled shifts: decision quality drops fast as fatigue sets in. Your team is no different.

How to Use the Coffee Cup Card Intentionally

Instead of waiting for people to quietly burn out in the session, make the coffee cup a first-class citizen:

At the start of the session, explicitly say:
“If you’re losing focus, getting frustrated, or feel this is going nowhere, play the coffee card. No justification needed.”
Treat a coffee card as a team-level event, not a personal weakness:
- One person plays it: pause and ask, “Do others feel the same?”
- Multiple people play it: take a 5–10 minute break or timebox the rest of the session.
Use it as a diagnostic:
- Frequent coffee cards early in the session? Your backlog is probably under-groomed.
- Coffee cards late in the session? Your meeting is too long or too detailed.

Example: When Coffee Saves the Sprint

A team I coached used to do 2-hour Planning Poker marathons. The last 30 minutes were always a mess: rushed estimates, rising tension, and stories that later blew up in development.

We introduced explicit use of the coffee card:

Rule: Any coffee card played after 75 minutes triggers a 10-minute break and a decision: “Do we continue or stop?”
Result after 4 sprints:
- Sessions capped at ~90 minutes instead of 120
- Fewer “surprise” oversized stories mid-sprint
- Higher participation from quieter team members (less fatigue)

The coffee card isn’t about politeness. It’s about protecting decision quality.

The Infinity Symbol: Your Early Warning System

If the coffee cup is about fatigue, the infinity symbol (∞) is about risk and scope.

What the Infinity Card Really Means

The infinity card is not “This is really big.”
It’s “This is too big to estimate meaningfully.”

That’s a critical distinction.

When someone plays ∞, they’re saying:

“We don’t understand this well enough.”
“This is not a story; it’s an epic or a project.”
“There are too many unknowns to give a number that means anything.”

Why Infinity Is Better Than “100”

Some teams use 40 or 100 to mean “huge.” That’s lazy.

Once a story crosses a certain size, the exact number stops mattering. Whether it’s a 40, 100, or 500, the only rational move is:

Stop estimating. Start slicing.

Using ∞ makes this explicit. It’s a flag that says:
“We should not be spending time guessing a number. We should be breaking this down.”

How to Act When Someone Plays Infinity

Here’s a concrete sequence you can use:

Ask for a quick explanation
- “What makes this feel infinite to you?”
- Look for: dependencies, unknown tech, unclear acceptance criteria, regulatory risk, etc.
Decide whether to continue or defer
- If the PO or stakeholder is present and engaged:
  - Do a 5–10 minute spike discussion to clarify scope.
- If key people are missing:
  - Stop. Mark the story as “Needs refinement” and move on.
Slice the story (if you continue)
- Ask:
  - “What’s the smallest version of this that would still deliver value?”
  - “What can we safely postpone?”
- Examples:
  - “Implement full reporting dashboard” →
    - “Basic daily report with CSV export”
    - “Admin-only dashboard with 2 key metrics”
  - “Migrate all customers to new billing system” →
    - “Migrate internal test accounts”
    - “Migrate 5% of low-risk customers”
Re-estimate the smaller stories
- Once you’ve split the story into smaller chunks, go back to normal cards.

Example: Infinity That Saved a Release

One team had a story:
“Implement multi-region failover for all services.”

Half the team threw down 13. One engineer played ∞.

We paused and asked why. His reasons:

No clear list of “all services”
Unclear RTO/RPO expectations
Unknown constraints from the infrastructure team

We stopped estimating and did a 30-minute spike:

Split the work into:
- “Define critical services list”
- “Agree on RTO/RPO per service”
- “Implement failover for 1 non-critical service as a pilot”
Those became separate, estimable stories.

That ∞ card probably saved them from a 3-month death march hidden behind a “13”.

The “?” Card: Useful, But Overused

The “?” card is supposed to mean “I don’t know enough to estimate.”
The problem: teams throw “?” when they actually mean ∞.

Use “?” when:

You joined mid-discussion and missed context
You’re unfamiliar with the domain or tech
You need a quick clarification

Use ∞ when:

The story itself is too big or too unknown
Even the experts are hand-waving

If more than 30–40% of your stories get “?” or ∞ regularly, that’s not an estimation problem. It’s a backlog refinement problem.

Common Mistakes with Coffee and Infinity (What Not to Do)

1. Treating Coffee as a Personal Weakness

Wrong pattern:

People feel guilty playing the coffee card.
The loudest voices keep going.
Everyone else zones out and rubber-stamps estimates.

Correct approach:

Normalize it: “Using coffee is part of how we keep quality high.”
Retro on it: “We used coffee 4 times today. Why were we so drained?”

2. Ignoring Infinity and Forcing a Number

If you’ve ever said, “We need a number for the roadmap,” you’re part of the problem.

Forcing a number on an ∞-worthy story leads to:

False predictability
Commitments based on fiction
Demoralizing “we’re behind” narratives later

If a story is ∞, your roadmap needs milestones, not fake precision. For example:

“Complete discovery for X by end of sprint 3”
“Pilot implementation in 1 market by Q3”

3. Using Large Numbers Instead of Infinity

If your deck includes 40 and 100, be careful:

40 and 100 often become “dumping grounds” for unclear work.
They hide the fact that you should be splitting, not estimating.

My stance:
Most teams should remove 40 and 100 from their deck and use ∞ instead. If it’s bigger than 20, it’s probably not a story.

4. Never Stopping the Session

Red flags:

No one ever plays coffee.
No one ever plays ∞.
Every story somehow becomes a 3, 5, or 8.

That’s not alignment; that’s groupthink.

If your team never uses the “non-numeric” cards, they’re probably:

Afraid to challenge the flow
Rushing to “get it done”
Treating estimation as a checkbox, not a decision-making tool

Practical Tips: How to Make These Cards Work for Your Team

1. Redefine the Rules of the Game

At your next Planning Poker session, explicitly define:

Coffee cup = “We need a break or reset.”
Infinity = “This is too big/unknown to estimate. We need to slice or refine.”
“?” = “I personally don’t understand this yet.”

Put these definitions on a shared board or slide. Refer back to them.

2. Timebox Ruthlessly

Estimation should not be a sinkhole.

Timebox discussion per story:
- Simple stories: 5 minutes max
- Complex stories: 10 minutes max
If you hit the timebox and still have confusion:
- Consider playing ∞ and moving the story back to refinement
- Or use coffee to reset and decide if it’s worth continuing

3. Track Your “Signal” Cards

Treat coffee and ∞ as metrics, not decorations.

Start tracking:

How many coffee cards per session?
How many ∞ cards per session?
How many stories get pushed back to refinement?

Look for patterns:

Spike in ∞ after new product direction? Backlog is misaligned.
High coffee usage at the end? Shorten the meeting or improve prep.
No coffee or ∞ ever? You probably have psychological safety issues or passive disengagement.

4. Prepare Stories Before Estimation

Estimation is not the time to discover what the story is about.

Before Planning Poker, ensure that each story has:

Clear, concise description
Acceptance criteria
Known dependencies (or at least identified unknowns)

If more than 20–30% of stories are getting ∞ or “?” because of missing basics, your refinement process is broken. Fix that first.

5. Use Tools That Support Anonymous, Fast Rounds

Anchoring bias is real. When the most senior engineer says “Eh, that’s a 3,” everyone else magically lands near 3.

Use tools or practices that:

Allow anonymous voting
Support quick revotes after discussion
Make it easy to pause (coffee) or mark a story as too big (∞)

Tools like ScrumPoi make this smoother: anonymous voting reduces anchoring, and you can quickly spin up a session without signups while keeping everything tied back to Jira.

Planning Poker Is a Conversation Tool, Not a Crystal Ball

If your Planning Poker sessions feel like a ritual you endure rather than a practice that improves your work, the problem isn’t the cards—it’s how you’re using them.

Use the coffee cup to protect focus and honesty.
Use the infinity symbol to expose risk and oversized work early.
Use the numbers only after you’ve had the right conversations.

Stop pretending you can estimate the unknowable. Start using your cards to surface what you don’t know—and make smarter decisions because of it.

The Coffee Cup and Infinity Symbol: Planning Poker Cards Explained