Roman Estimation

---

Origins

Roman Voting (also called Roman Estimation when applied to estimation) comes from the broader facilitation tradition rather than software specifically. The metaphor borrows from the (mostly fictional) Roman gladiatorial vote: thumbs up means continue, thumbs down means stop, thumbs sideways means undecided.

Agile teams adopted the format as a coarse triage technique, particularly for situations where Planning Poker would be overkill. Used as a first pass during refinement or release planning, Roman Estimation lets a team filter a long list quickly before investing in detailed estimation.

The Mechanics

For each item, the facilitator reads the title and a brief description. The team simultaneously gives one of three signals:

• Thumbs up: this item is small and well-understood. Comfortable estimating now.
• Thumbs down: this item is too big, too vague, or too risky to estimate. Needs refinement before serious estimation.
• Thumbs sideways: uncertain. Could go either way. Discussion needed.

The whole vote takes 5-15 seconds per item. The output is a triage of the list:

• Items with unanimous thumbs-up move to detailed estimation.
• Items with thumbs-down go back for refinement.
• Items with mixed signals get a brief discussion to clarify what's missing.

When Roman Estimation Earns Its Time

• Long backlog refinement: a backlog of 80 items can be triaged in 20 minutes. Detailed estimation of the same list would take hours.
• Pre-Planning Poker filter: identify which items are actually ready for Poker before running it. Avoids spending Poker time on items that aren't yet refined enough.
• Release planning at high altitude: when the question is "is this approximately in our capacity?" not "exactly how much capacity?"
• Cross-team prioritization conversations: when scope discussions need a fast sense of what's small enough to consider versus what's likely too big.

Variants

Fist of Five

A five-point scale instead of three. Fingers up indicate confidence (5 = high, 1 = low) or size or whatever metric the team is voting on. Slightly more nuance than thumbs-up/down/sideways without going to a full Fibonacci card deck.

T-Shirt First Pass

Each person silently shows S/M/L/XL with a hand sign or written card. Coarse triage that gives more information than Roman but less than Planning Poker.

Dot Voting

If the question is "which of these items are most important?" rather than "how big is this?" dot voting accomplishes similar triage for prioritization.

What Roman Estimation Doesn't Do

Roman Estimation is triage, not sizing. It tells you which items are roughly ready and which aren't. It doesn't tell you how big the ready ones are.

Teams that try to use Roman as their primary estimation technique end up with imprecise plans. The format is meant to filter before detailed estimation, not to replace it.

Common Pitfalls

• Using it as the only estimation: Roman doesn't produce numbers detailed enough for forecasting. Use it to triage, then estimate the ready items properly.
• Voting without context: if the team doesn't have enough information to understand each item, the votes are random. Provide brief context before each vote.
• Skipping the mixed-signal discussion: items with thumbs-up and thumbs-down mixed are the most useful conversation. Don't move on without understanding why people disagreed.
• Letting thumbs-down items rot: items pushed back to refinement need someone to actually do the refinement. Without ownership, they stay thumbs-down forever.
• Treating thumbs-up as commitment: a thumbs-up means "I'm willing to estimate this," not "I will deliver this." Don't conflate.

Coaching Tips

Use It as a Filter

Roman comes before detailed estimation, not instead of it. Triage first, then estimate the ready items properly.

Discuss the Mixed Signals

Items with thumbs-up and thumbs-down both have information. Spend 60 seconds understanding why people disagreed before moving on.

Assign Refinement Owners

Thumbs-down items need someone to refine them. Without an owner, the same items appear thumbs-down session after session.

Provide Brief Context

Each item needs enough context for the team to vote meaningfully. A title alone is rarely enough.

Don't Promote to Commitment

Thumbs-up means "ready to estimate," not "we'll deliver this." Make the distinction clear before voting.

Keep It Fast

The format's value is speed. 15 seconds per item, not 5 minutes. If items are taking longer, the team needs refinement, not Roman voting.

Summary

Roman Estimation is the cheapest estimation-adjacent technique in the toolkit. Its value comes from getting the team to look at every item briefly before investing time in detailed estimation on the wrong ones. A team that runs Roman on its backlog before refinement sessions ends up doing less wasted estimation work.

The discipline is using it for what it's for. Roman gives you triage; it doesn't give you sizing. Teams that try to extend it past its purpose produce imprecise plans; teams that use it as the cheap first pass it was designed to be get the value it offers without overreaching.

Back to Agile Delivery