Agile estimation for shared understanding

Estimate user stories
with shared understanding

Separate complexity, effort and risk. See where your team’s ratings differ, discuss the assumptions and agree on an estimate you can explain.

Free during public preview. No payment details required.

STORY-4821 · Add SSO via Azure AD Example 4 Team Members
Team vote
Complexity
⌀ 3.00
Scope
⌀ 4.00
Risk
⌀ 2.00
Moderator selection

Change the moderator selections to see the final estimate update. Example votes stay unchanged. This example uses the default scale.

Complexity
Medium
Several approaches, some thinking
Scope
Large
Many activities across different areas
Risk
Low
Few open questions, low potential impact
Estimate: 8
Estimate
8
Calculation
Category Value x Factor = Total
Complexity 3 x 2 = 6
Scope 4 x 1 = 4
Risk 2 x 2 = 4
Total 14
Mapping Table
From To Estimate
5 5 1
6 7 2
8 9 3
10 11 5
12 15 8
16 20 13
21 25 21
Current range: 12 – 15 → 8
Estimate
8

Why these dimensions?

Guest access
no participant accounts needed
Sprint planning
and refinement
Independent
ratings before discussion
Live overview
see voting progress and results
Jira & Azure DevOps
import stories and write estimates back
The challenge

When estimation discussions get stuck

The first number sets the tone

An early estimate can influence everyone else before they have considered the story themselves.

Another vote, the same disagreement

Repeating the vote adds little when the assumptions behind different estimates stay hidden.

One number mixes different questions

One person considers technical difficulty, another the amount of testing, and another an unknown dependency.

Three dimensions

Why these three dimensions?

Different reasons for a large estimate need different conversations. Separating difficulty, quantity and uncertainty helps your team see what is driving the estimate and what to discuss next.

  • Give each dimension a shared meaning within your team
  • See where assessments differ
  • Agree on final ratings and the next step

See an example in the guide

Complexity

A small change can require difficult reasoning. Complexity brings tricky rules, interactions and technical challenges into the discussion.

Effort / scope

Straightforward work can still be substantial. Scope makes the amount of implementation, testing and related work visible.

Risk

Unknowns and dependencies can change the work ahead. Risk helps identify what needs investigation or clarification.

Prefer to rate expected time investment? Choose time instead of scope in your team settings. Complexity and risk stay separate: there are always three ratings. Time describes the expected work for one participant, not a delivery deadline.

Your first session

How it works

01

Prepare stories

Create stories manually or import them from CSV, Jira or Azure DevOps. Add the context your team needs before voting.

02

Invite your team

Share the session link. Participants can join as guests; the organizer needs an account with a confirmed email address.

03

Rate independently

Each participant rates the three dimensions. Once votes are revealed, compare the distributions and discuss the differences.

04

Agree and save

The moderator records the final ratings and saves the estimate. With a configured integration, write the result back to Jira or Azure DevOps.

For agile teams

A shared view of the work ahead

Scrum Master

Guide the conversation toward differences in assumptions and clear next steps.

Product Owner

Understand what an estimate includes and which questions still affect scope or priority.

Engineering teams

Bring technical knowledge into the discussion and explain the reasons behind your ratings.

Ready for clearer estimates?

Bring one story to Consonus. Compare your team’s complexity, effort and risk ratings, discuss the different assumptions and agree on your next step.

Free during public preview. No payment details required.