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.

Introduction

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


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. A moderator invites participants to the session via a sharable link. Alternatively, the moderator shares the screen with participants and interacts on their behalf. 

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

  5. Next participant may:

  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 estimation 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 is configured in 3 quick steps:

  1. Create Relative session:
  2. Manage participants:
  3. Select issues:

Once ready, click Start session button to proceed.


From inside the session click Configuration (a cog icon) or Participants from the top right to update session settings. Session scope can be also re-configured from the main Relative session window using Add issue, Create issue and Remove from the session (appears during card dragging process) options: 


Sharing session link

Once the session was started, you can share the session link with your team by copying it from the browser's address bar, the bread crumbs section, or from Manage participants screen; click Participants button located in the top corner to open it:


You can also remove 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 non-moderator participants: 

The moderator is displayed with a crown next to an avatar (except if everyone is a moderator).

If there is no moderator selected (default state), all the participants have access to all the features mentioned above. Please note that the moderator's role in a public session doesn't have an exclusive power to manage participants; every participant has full access to participants and moderator management settings. While for private sessions participants are managed by moderators only. 

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 moderator can activate the voting option and ask participants to vote for a "column" for a specific user story. Alternatively, the team can vote for every single story in sequence using Automatic issue pickup for voting.

In order to enable the voting option the moderator has to expand the Voting panel using the arrow icon:

When enabled, the Automatic issue pickup for voting option will place the next issue from the session scope list to the voting area once the final vote for the current issue has been cast. When disabled, the moderator will manually control issues to vote for. 

Drag and drop a user story to the voting area to start voting:

Now participants can vote for existing or new columns for the selected user story. The personal voting process options are:

Once personal votes are revealed, the following options are available:

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

Placing estimates

At any moment of time, but usually after your "Session scope" deck is empties, 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:

Saving estimates

 


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

Check out other estimation sessions offered by Agile Poker for Cloud:

Please let us know if this article was helpful, your feedback is appreciated: support@spartez-software.com