Assumption Identification

Assumption Identification, as practiced during backlog refinement, is the deliberate technique of pausing discussion of a story to explicitly ask what unstated beliefs the group is relying on, surfacing them as visible, discussable statements rather than leaving them buried silently within the story's description or within individual team members' private interpretations. Within the flow of a refinement session, this identification step sits alongside clarification, decomposition, and estimation as one of the standard activities the group performs, specifically targeting the hidden beliefs that could otherwise undermine the reliability of everything else the session produces.

Why Identification Is a Distinct Session Activity

Assumptions Hide in Plain Sight

During ordinary discussion, participants often unconsciously fill gaps in a story's description with their own assumed interpretation, proceeding as though that interpretation were an agreed fact rather than a personal guess that may differ from what others in the room are assuming.

Surfacing Prevents Divergent Interpretation

By deliberately pausing to ask what is being assumed, the group converts private, potentially inconsistent beliefs into an explicit, shared statement that everyone can examine, challenge, or confirm together.

Prompts That Surface Hidden Assumptions

Asking About Unstated Conditions

Directly asking what conditions the story assumes to be true — about user behavior, system state, or external systems — prompts participants to voice beliefs they might not otherwise think to mention.

Asking What Happens If This Is Not True

Posing a direct challenge to a stated or implied condition, asking what would happen if it turned out to be false, quickly reveals whether the group has quietly assumed something without verifying it.

Reviewing Silence in the Description

Noting where the story's written description is silent on a relevant point, and asking the group what they are each assuming to be true in that silence, surfaces gaps that might otherwise go unnoticed.

Integrating Identification into the Refinement Flow

Before Estimation

Identifying assumptions before the group attempts to estimate a story's size ensures the estimate is based on a shared, examined understanding rather than divergent private guesses that could each imply very different amounts of work.

Before Decomposition

Surfacing assumptions can also reveal that a story's apparent scope depends heavily on an unconfirmed belief, which may change how the group chooses to decompose it once that belief is examined more closely.

Recording Identified Assumptions

Once surfaced, assumptions are typically recorded directly alongside the story, distinguishing them clearly from confirmed facts so that later readers understand which parts of the story's basis remain provisional.

Prioritizing Which Assumptions to Resolve

Assessing Risk Before Moving On

Not every surfaced assumption requires immediate resolution; the group weighs how significantly the story would change if a given assumption proved false against the cost of pausing to verify it right away.

Deferring Low-Risk Assumptions

Assumptions judged unlikely to be wrong, or whose impact would be minor even if incorrect, are often simply recorded and carried forward rather than requiring the session to halt for immediate verification.

Visualizing the Identification Step

The pause to surface assumptions sits deliberately between ongoing discussion and estimation, ensuring the group proceeds on the basis of examined, shared beliefs rather than unexamined individual guesses.

Common Pitfalls

Skipping the Pause Under Time Pressure

Moving directly to estimation without pausing to surface assumptions risks producing estimates built on inconsistent, unexamined beliefs held by different participants.

Surfacing Assumptions Without Recording Them

Discussing assumptions verbally in the moment, without writing them down alongside the story, risks losing the benefit of the exercise once the session ends and memory fades.

Treating Every Assumption as Equally Urgent

Attempting to resolve every surfaced assumption immediately, regardless of its risk, can slow refinement unnecessarily; prioritizing by potential impact keeps the session efficient.

Benefits of Deliberate Assumption Identification

More Reliable Estimates

Ensuring the group shares a common, examined understanding before estimating produces more consistent and trustworthy size estimates.

Earlier Detection of Risk

Surfacing assumptions during refinement, rather than discovering them only during development, allows high-risk beliefs to be validated while correction remains inexpensive.

A More Transparent Backlog

Recording identified assumptions alongside stories gives future readers visibility into which parts of a story's basis are confirmed and which remain provisional, supporting better-informed decisions later.