Relative session

The Relative session is fast, simple, and intuitive. Instead of assigning specific estimation values, teams only need to compare issues to one another.

Compared to standard Planning Poker, the Relative session focuses on quick estimations with less issue discussion. However, the session can be easily customized by the team and moderator to fit their specific needs.

Requirements

• The current implementation stores the session state in the browser's local storage. Therefore, it is important to ensure that your browser supports and has enabled local storage functionality.

Mechanics of the Relative session

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

Here's a brief step-by-step overview of how the Relative session unfolds:

1. After configuring session settings, a moderator starts the Relative session and selects issues to be estimated.

2. The moderator invites participants to the session through a shareable 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. The next participant places the next issue on the virtual wall relative to the first issue:

   • If the issue is smaller, it is placed on the left.

   • If the issue is larger, it is placed on the right.

   • If the issue is of similar size, it is placed below, forming a column.

5. The following participant can either:

   • Place a user story card from the pile on the virtual wall using the same placement rules.

   • Move a card already on the board with an accompanying comment explaining the move.

6. The team continues taking turns, placing issues until all issues are on the virtual wall and the pile is depleted.

7. If necessary, the team can utilize the Voting option, allowing participants to vote for the placement of specific user stories.

8. It is now time to fine-tune the order by moving issues one at a time with a few words of explanation.

9. Once everyone is satisfied with the outcome, arrange the issues from left to right, from smallest to largest.

10. The last step is to assign estimation values corresponding to each column, typically using the Fibonacci sequence.

11. Save the assigned estimation values to the respective issues.

Check the video below to see how the session works in action:

How to create a Relative Session

Step 1: Open the Create session screen

Step 2: Create Relative session

Open

3. Name your session (up to 100 characters) or go with a pre-set one.

4. Optionally save the current configuration as your personal default, which means it will be used when creating new sessions for the current board. The following fields will be remembered: session type, estimation field, and participants.

5. Select the session type (Public/Private).

Click Next and you’ll be directed to the Manage participants page.

Step 3: Manage participants

6. Choose a Moderator to give them exclusive control over the estimation session. Otherwise, everyone can control the session.

7. Pick the people that estimate with you.

Click Next and you’ll be directed to the Select issues page.

Step 4: Select issues

8. Select a Jira field that would be the destination for session estimates.

9. Select the issues that will be estimated during the session. For more details on filtering issues, refer to this documentation.

10. From the Issue Types dropdown, define if you'd like to estimate Epics or Sub-tasks as well.

Click Start session and the estimation will start. Keep in mind that you can create and run multiple Relative sessions in parallel.

How to join the Relative session

• Team members can join an active session from the Agile Poker session selection page or the All Sessions page.

• Alternatively, the moderator can share the session link with the team by copying it from the address bar, the breadcrumbs section, or from the participants' management menu (click Participants from the top right to open it).

Estimation process

The estimation process within a Relative session follows a structured workflow. During the estimation, the team members will size user stories based on their relative “weight” by moving the cards around the collaborative board. The position of every user story can be voted on by the team if consensus is required. Here's what happens step by step:

1. Entering the session

Upon entering the session, each new participant is prompted to go through navigation tips. To review the tips again, click the three dots icon at the right-hand side of the screen, and then click Take a tour.

In the Participants panel, which is on the left-hand side of the screen, you can see your team members participating in the estimation. Here are some things to keep in mind:

• Moderator: Identified by a crown icon on their avatar.

• Inactive Participants: Avatars are greyed-out.

2. Starting the 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 locations:

3. Optional: Vote!

The moderator has the option to activate voting 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. To enable the voting option, the moderator has to expand the Voting panel using the arrow icon. They can then drag and drop a user story into the voting area to start the voting process.

Participants now have the option to vote for existing or new columns for the selected user story. The personal voting process options are:

• To cast a vote, participants can click on a like icon or the header of their preferred column.

• Participants can change their votes an unlimited number of times before the voting ends.

• The voting process is unbiased, with participants unable to see the votes or cursors of other team members.

• Status marks on participants' avatars can be used to monitor the voting progress.

• The voting process automatically concludes when all participants have voted.

• The moderator has the authority to finish the personal voting process at any time by clicking on the Reveal votes button.

• During the personal voting phase, the moderator(s) have the flexibility to move cards around the board, but they cannot add new columns or remove existing ones to avoid conflicts with participants' voting progress.

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

• The winner(s) will be highlighted with blue Accept buttons, while other existing or potential columns will have standard grey Accept buttons.

• The moderator casts the final vote by clicking on the Accept button inside the appropriate column or by dragging the issue to that column.

• The moderator can use the Reset voting option to restart the personal voting process if the team wants to reach a consensus.

• During the final voting phase, the moderator or moderators have the freedom to move cards around the board and even add or remove columns, although this may result in the loss of personal votes.

Depending on the team and workflow, various session scenarios are possible, such as voting for a single issue or voting for every issue within the session scope.

4. Place estimates

At any point in time, typically after your "Session scope" deck is empty, you can begin assigning estimate values for the buckets that display "No value".

Please note that additional labels may be added to the left of the estimation value fields at any stage of the estimation process.

5. Save estimations

When you are satisfied with the results, you can click the Save estimates button located at the bottom right to conclude the session and update the respective estimation fields of the issues.

Then click Save to confirm the action.

That's it! Now you can either go back to the board or continue with the estimation session. If the Finish session button is used, the session will be terminated for all participants without saving the progress.