Back to report

Research appendix

Full Data: State of Planning Poker 2026

This page contains the complete anonymized dataset behind the State of Planning Poker 2026 report. All findings in the main post are derived from these numbers. Publishers and researchers are welcome to reference the data with a link back to the original report.

Data window: Q4 2025 - May 2026Sources: Firebase + PostHogzymantas@scrumjam.app

Sessions

2,465

Filtered planning poker sessions.

Teams

208

Distinct real ScrumJam teams.

Votes

103,343

Individual votes in PostHog.

Median duration

41.8 min

Session start to last reveal.

1. Dataset Overview

MetricValueSource
Total sessions analysed2,465Firebase
Total teams208Firebase
Total reveals / estimates14,119PostHog
Total individual votes103,343PostHog
Data windowQ4 2025 - May 2026ScrumJam
Session filter2+ reveals with 2+ participantsScrumJam

2. Day Of Week

Session creation grouped by weekday.

DaySessions% of total
Monday1,84417.2%
Tuesday2,35021.9%
Wednesday2,30821.5%
Thursday2,66024.8% - peak
Friday1,30812.2%
Saturday1581.5%
Sunday1101.0%

3. Hour Of Day

Session creation grouped by UTC hour.

Hour (UTC)Sessions%
06:002972.8%
07:005805.4%
08:001,07310.0%
09:001,25111.7% - peak
10:008187.6%
11:009158.5%
12:009869.2%
13:001,0159.5%
14:008828.2%
15:005505.1%
16:004254.0%
17:004624.3%
Outside 06-18~600~5.6%

Times are UTC. Most teams appear to be in European timezones, placing the real peak at 10-11 AM local time.

4. Session Duration

MetricValueSource
Median duration41.8 minFirebase
Average duration48.3 minFirebase
P25, fastest quarter~20 minFirebase
P75, slowest quarter~62 minFirebase
Sessions under 15 min~12%Firebase
Sessions over 60 min~28%Firebase

Duration is measured from session start to last reveal. Sessions shorter than 1 minute or longer than 4 hours are excluded.

5. Tasks Estimated Per Session

Tasks per sessionSessions%
2-3 tasks85833.6%
4-6 tasks96137.6% - most common
7-10 tasks52420.5%
11-15 tasks1325.2%
16+ tasks803.1%
Average tasks per session5.4
Median tasks per session5

6. Team Size Analysis

Team sizeSessionsMedian durationTasks/hourAny perfect consensus
2-3 people8920.8 min51.551.7%
4-5 people42338.0 min21.556.3%
6-7 people53638.1 min20.840.5%
8-10 people28144.8 min19.031.0%
11+ people10046.5 min15.325.0%

Tasks/hour is estimation throughput regardless of point values. Perfect consensus means a session had at least one round where all participants voted identically.

7. Vote Distribution

Based on 103,343 individual votes across all sessions.

CardVotes%
331,07330.1% - most common
223,66022.9%
521,09720.4%
111,16010.8%
87,5447.3%
132,1482.1%
0.56860.7%
216820.7%
46580.6%
Other / T-shirt~4,635~4.4%

Cards 1-5 make up 84.2% of all votes. Cards 8+ make up 10.7%. Average individual vote is 4.73; median individual vote is 3.

8. Highest Estimate Per Session

Highest average vote recorded in any single round, per session.

Highest estimateSessions%
1-2 pts8021.9%
3 pts13737.5%
5 pts9024.7%
8 pts318.5%
13 pts82.2%
21+ pts195.2%

84.1% of sessions never produce an estimate above 5 points. Only 15.9% include an estimate of 8 or above.

9. Deck Usage

Deck% of sessionsSource
Fibonacci Sequence84.5%Firebase
Fibonacci Flat Sequence4.9%Firebase
T-Shirt Sizes2.3%Firebase
Simple Numbers2.1%Firebase
Hours Sequence0.6%Firebase
Doubled Sequence0.5%Firebase
Custom decks~5.1%Firebase

Fibonacci variants combined: 89.4%. Notable custom decks included half-point linear sequences, large-scale sequences, Yes/No decks, and novelty sequences such as 1, 2, 3, 5, 8, >9k.

10. Sprint Cadence

Among teams that have run three or more sessions.

Sessions per month%
5+/month36.1%
3-4/month39.6% - most common
2-3/month24.3%

75.7% of active teams run three or more sessions per month.

11. Consensus And Alignment

MetricValueSourceNotes
Weighted consensus score71 / 100FirebaseStep-distance based, not binary
Perfect consensus rate15.6%PostHogAll votes identical
Teams with measurable outlier voter31.9%PostHog2+ point gap between two team members
Banana rains per session0.88FirebaseRounds where all votes were identical

Consensus score is a 0-100 weighted score based on Fibonacci step distance. Two votes one step apart, such as 8 and 13, score 85/100.

12. Session Overview

Firebase aggregate fields used in the report.

MetricValue
Average reveals per session5.4
Average resets per session4.21
Average banana rains per session0.88
Median session duration41.8 min
Average session duration48.3 min

Data Quality And Filters

Sessions included if:

  • At least 2 estimation rounds with 2+ participants voting.
  • Session duration between 1 minute and 4 hours.
  • Associated with a real team, not anonymous single-user tests.
  • Not from ScrumJam internal test accounts.

Data sources:

  • Firebase: session-level aggregates, deck usage, duration, consensus, and reveal counts.
  • PostHog: event-level votes, participant counts, timestamps, and outlier analysis.
  • Where sources overlap, Firebase is primary because it captures all sessions.

How To Cite

ScrumJam, "State of Planning Poker 2026", scrumjam.app/blog/state-of-planning-poker-2026.