Agile Poker Server
This part of the documentation relates to Agile Poker Enterprise for Jira Server. If you use Jira Cloud go to the Agile Poker Enterprise for Jira Cloud documentation.
Table of contents:
Introduction
Relative estimation sessions are designed for making quick and rough estimations of large batch of issues (50+). The flow for relative estimation sessions is based on the Team Estimation Game method (description on agilelearninglabs.com, another description on thedroidsonroids.com), translated into electronic world and employing trello-like user interface for smooth issue drag'n'drop experience. The relative estimation mode is also heavily inspired by techniques known as Magic Estimation or Silent Grouping. Here is general gist of the session:
- Session moderator selects issues to estimate and shares his screen with the participants. Moderator is going to interact with the user interface on behalf of the participants.
- Someone starts the session by taking the top issue from the deck, and places it in the middle of the virtual wall.
- Another person picks the next issue off the top of the deck, then decides if it’s smaller or bigger than the issue already placed on the virtual wall:
- 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 the already placed issue (forming a column, or a bucket)
- Another person may:
- either take another issue from the deck and place it on the virtual wall with the same rules as above
- move a single story card already placed on the wall/table together with a comment explaining this move
- The team continues to take turns placing issues until the deck is finally depleted.
- All issues are on virtual wall. Now 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 estimation value corresponding for each column - usually using Fibonacci sequence, and save the results (by default under Story Points custom field).
Creating relative estimation session
- On the sessions dashboard view, click the "Create session" button.
- On the "Create new session" popup choose "Relative estimation" and click "Next":
- Choose issues you want to estimate (session scope) and click "Next" to create your new relative estimation session.
Issue placement phase.
- While in 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 existing column (if item is comparable in size)
- to the left (or right), if the item is considerable smaller (greater) than existing issues on the wall:
- stick the issue between two existing columns:
- under existing column (if item is comparable in size)
Placing estimates
- At any moment, which usually happens after your "Issues to be estimated" deck is finally 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 Save button.
Limitations / caveats (todo)
Loerm ipsum: talk about localStorage issue. + screenshots.