| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about Agile Poker for Jira Data Center. Using Cloud? Click here. |
Overview
The Relative session is fast, simple, and intuitive. Instead of assigning specific estimation values, teams only need to compare issues to one another.
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Who should use Relative session? Relative session is ideal for making quick and rough estimations of a large batch of issues (50+). Still, it’s highly adopted by teams with a small number of issues per estimation session (<20). It’s also recommended for:
|
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.
...
| Widget Connector | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Before you begin
The current implementation stores the session state in the browser's local storage. This has the following implications:
Your browser must support local storage and have it enabled.
You can't involve multiple people in the session simultaneously, the only way is to share a screen with them.
You can't create multiple sessions simultaneously on the same browser/profile. First, you need to finish or discard the previous one.
The relative sessions are not shown either on the All Sessions dashboard or in the Agile Poker menu.
How to create a Relative session
Step 1: Open the Create session screen
| Expand | ||
|---|---|---|
| ||
|
Step 2: Create Relative Session
Choose the issues you want to estimate (session scope) and click Create to create your new relative estimation session.
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:
Issue placement phase
While on the 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:
under the existing column (if the item is comparable in size)
to the left (or right), if the item is considerably smaller (greater) than existing issues on the wall
put the issue between two existing columns to create a new one
Placing estimates
At any moment, which usually happens after your Issues to be estimated deck is empty, you can start filling in the estimate values for the column items.
...
Saving estimates
When happy with what you see, you can click Save estimates button (bottom right) to conclude the session and update the issues' respective estimation field.
You will be prompted with a dialog asking you where to store the results:
Choose the desired field to update and click the Save button.
Further reading
Keep in mind the following resources are not created nor maintained by Appfire, but you still might benefit from them:
...