...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This page is about Agile Poker for Jira |
...
Table of contents:
| Table of Contents | ||
|---|---|---|
|
Introduction
...
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.
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.
| 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 Team the Magic Estimation Game method, employing a Trello-like interface for a smooth issue drag'n'-and-drop user experience. The relative estimation mode is It’s also heavily inspired by techniques known as Magic Estimation or 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 is general gist of the session:
...
Here's a brief step-by-step overview of how the Relative session unfolds:
The session moderator shares their screen with the participants and interacts on behalf of them.
Status colour Yellow title Beta
...
The moderator puts the issues to be estimated in a pile.
...
The first participant places the top issue on the virtual wall.
...
The next participant places the 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).
...
The next participant may:
...
Either place the issue from the pile on the virtual wall using the same rules as above
...
.
...
Move an issue already placed on the wall/table together with a comment explaining this move.
The team continues to take turns placing issues until the pile is finally depleted and all issues are on the virtual wall.
It is the time to fine-tune the order by moving issues one at a time with a few words of explanation.
When everybody is OK with the outcome, the issues are ordered left to right, smallest to largest.
The last step is to assign an estimation value corresponding to each column (usually with the Fibonacci sequence).
Save the assigned values to the issues.
See how it works herethe video below to see how the session works in action:
| Widget Connector | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Creating relative estimation session
...
|
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.
...
Current implementation stores the session state in the browser's local storage. This has the following implications:
1) your browser must support local storage and have it enabled;
2) you can't involve multiple people in the session simultaneously, the only way is sharing a screen with them;
3) you can't create multiple sessions simultaneously on the same browser/profile - first, you need to finish or discard the previous one;
4) the relative sessions are not shown neither on the All Sessions dashboard nor in the Agile Poker menu
Further reading
...
...
Keep in mind the following resources are not created nor maintained by Spartez SoftwareAppfire, but you still might benefit from them:
...
Detailed explanation of the Team Estimation Game method. Good for introductory reading
...
.
...
One-paged "cheat sheet" for the Team Estimation Game.
...
Another explanation of Team Estimation Game. Less pictures, but with more verbose examples.
...
Kindle pocket guide on Team Estimation,
...
authored by the technique author
...
.
...
Introductory explanation to the Magic Estimation method, with a bit of hints.