Support Stimo
Ad

Quick guide

How Stimo works

Stimo helps agile teams estimate user stories by adding up the effort from each role.

Workflow

  1. Create a room and share the invitation link.
  2. Each person joins with their name and role.
  3. Voting roles estimate privately.
  4. The organizer reveals and reviews the results.

Roles

Developer, QA, UX and Other vote. Scrum Master and Product Owner observe by default.

Conservative calculation

Stimo calculates each role without intermediate rounding, adds the roles and only adjusts the final total when needed.

Results

You will see the final estimate, profile sum, the median and average comparison, and a role summary with votes, average, median and final result.

Before you start

Come to the session with small stories, visible acceptance criteria and a clear question to resolve.

  • Define what is being estimated: scope, risks and dependencies.
  • Invite only the people who bring context or estimation input.
  • Use one room per session to keep the conversation focused.

Organizer role

The person who creates the room controls reveal and new round actions. They also share the invitation link.

  1. Present the story and confirm everyone understands the goal.
  2. Wait until voting roles have finished.
  3. Reveal, discuss disagreements and start another round if the shared understanding changes.

How to vote well

Vote the likely effort from your role, not what you think the rest of the team will vote.

  • Use `?` when key information is missing and you cannot estimate responsibly.
  • Use coffee when the conversation needs a pause or clarification before moving on.
  • You can change your vote while the round is still open.

Fibonacci and days

Fibonacci works well for relative uncertainty. Days are useful when the team wants to discuss approximate time.

Choose the scale when creating the room. During the session, avoid changing scales so criteria stay consistent.

How to read the result

The final estimate helps the team decide; it is not an automatic order. Also look at spread and roles with differences.

  • If median and average are close, the team usually has enough consensus.
  • If one role is far away, ask what risk that role is seeing.
  • If many `?` votes appear, postpone the estimate or split the story.

Common issues

If someone does not see updates, refreshing the room and joining again with the same link is usually enough.

  • If the link does not open, ask the organizer to copy the invitation again.
  • If a room expired, create another one and share a new link.
  • If someone joined with the wrong role, they can leave and join again.
Back home