Child pages
  • Relative session


Agile Poker Cloud

This part of the documentation relates to Agile Poker for Jira Cloud. If you use Jira Server go to the Agile Poker for Jira Server and Data Center documentation.


Relative estimation session by Agile Poker for Jira Cloud is one of the most popular parts of our software. It is:

  • really fast, easy, and intuitive since the team doesn’t need to think of estimation values, but only compare one issue with another. Recommended for:

    • teams that are new to estimation;

    • mature estimating teams that want to speed up the estimation process;

    • for any other team that prefers a visual representation and interaction;

  • designed for making quick and rough estimations of a large batch of issues (50+), still, highly adopted by teams with a small (<20) number of issues per estimation session;

  • considered as an estimation session with a low level of issue discussion comparing to standard Planning Poker, still, a team and session moderator can easily adjust this to their needs.

The Relative estimation session is based on the Team Estimation Game method, employing a Trello-like interface for smooth issue drag and drop user experience. The relative estimation mode is also heavily inspired by techniques known as Magic Estimation, Silent Grouping, Affinity Estimation, or Swimlanes Sizing, so knowing one of them should make you comfortable with the flow. Here is the general gist of the session: 

  1. A moderator starts the Relative session and selects issues to be estimated.

  2. The moderator invites participants to the session via a sharable link. Alternatively, the moderator shares the screen with participants and interacts on behalf of them. 

  3. The first participant places the top issue on the virtual wall.
  4. Next participant places the next top issue on the virtual wall relative to the first issue:

    • if it’s smaller, it gets placed on the left

    • if it’s bigger, it gets placed on the right

    • if it’s around the same, then it should be placed below (forming a column)

  5. Next participant may:

    • either place a user story card from the pile on the virtual wall using the same rules as above

    • move a card already placed on the board together with a comment explaining this move

  6. The team continues to take turns placing issues until the pile is finally depleted and all issues are on the virtual wall.

  7. If required, the team can use the Voting option where participants can vote for a place for a specific user story.
  8. It is the time to fine-tune the order by moving issues one at a time with a few words of explanation.

  9. When everybody is OK with the outcome, the issues are ordered left to right, smallest to largest.

  10. The last step is to assign estimation values corresponding to each column (usually with the Fibonacci sequence).

  11. Save the assigned values to the issues.

Check the detailed explanation below or see how it works here:

Session Configuration

Initial configuration

Onсe launched from the Classic or Next-Gen project menu, the Relative session must be configured by selecting issues you want to estimate (session scope) and clicking on "Create" to start the Relative estimation session. JQL filtering and bulk selection will come in handy:

Please note that there is only one Relative session for each board, so if you need to launch the second one for the same project, the only option to do this is to use another board.

Session scope can also be re-configured from the main Relative session window using add, create and remove from the session (appear during card dragging process) options: 

Inviting participants

Once the session started, you can share the session link with your team by copying it from the address bar, the bread crumbs section, or from participants management; click on Participants from the top right to open it:

The participant management menu can also be used for removing inactive team members from the session. Inactive participants have a grey indicator next to their avatars, while active have a green one:

Moderator role

In the Participants menu, the moderator role can be assigned. It gives several privileges comparing to a non-moderator participants: 

  • start and manage the voting process;
  • submit the final votes;
  • save estimates;
  • the moderator has a crown next to his pointer and avatar.

If there is no moderator selected (default state), all the participants have access to all the above features. Please note that the moderator's role doesn't have an exclusive power to manage participants; every participant has full access to participants and moderator management settings. 

Estimation process

Issue placement phase

While on the session page, drag the issues from the deck (left screen side) to the virtual wall (right screen side): 

Continue dragging issues from the deck. You can drop the issue in the following places:

1) within the existing column (if an item is comparable in size)


2) to the left (or right), if the item is considerably smaller (greater) than the existing issues on the board:

3) place the issue between two existing columns:

Voting option

The Voting option has been added to the latest multiplayer version of the Relative session. The moderator can activate the voting option and ask participants to vote for a place for a specific user story. 

Click on the raising hand person from the top of the "To be estimated" part to start the Voting:

Drag and drop a user story to the voting area:

Then vote for existing or for a new column for this user story. Winner or winners will be highlighted with green: 

Voting status is displayed both in buckets and on Participants' avatars:

If needed, voting progress can be reset and repeated if the team wants to come to a consensus:

To finish voting simply drag the voted story to the winning bucket.

Depending on a team and flow, different session scenarios are possible, like voting for an issue or for the whole session scope. 

Placing estimates

At any moment, but usually after your "To be estimated" deck is finally empty, you can start filling in estimate values for the buckets where it says "No value":

Please note that additional Labels might be added on the left from estimation values fields at any point of the estimation process:

Support help or feedback

"Problem or suggestions?" button from the bottom menu is always available for you, don't hesitate to contact our awesome support!

Saving estimates

  • When happy with what you see, you can click on the 'Save estimates' button (bottom right) to conclude the session and update the issues' respective estimation field. 

    NOTE: all the estimations are saved to an estimation field specified in Board Settings.

  • Then click on the 'Save' to confirm the action:


  • That’s it! Now you can go to the board, or get back to the estimation session:

Limitations and caveats

Current implementation stores the session state in the browser local storage. This has the following implications:

  1. Your browser must support local storage and have it enabled

  2. You can create only one Relative session for each board, so if you need to launch the second one for the same project, the only option to do this is to use another board.

What's next?

Now it's time to check Agile Poker for Cloud Session types: 

Please let us know if this article was helpful, your feedback is appreciated:

  • No labels

This page has no comments.