Skip to end of banner
Go to start of banner

Relative estimation sessions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Agile Poker - estimation tool for Jira Server'.

Table of contents:

Introduction

Relative estimation sessions are designed for making quick and rough estimations of large batch of issues (50+). The relative estimation sessions is based on the Team Estimation Game method, employing trello-like interface for smooth issue drag'n'drop user experience. The relative estimation mode is also heavily inspired by techniques known as Magic Estimation or Silent Grouping, so knowing one of them should make you comfortable with the flow. Here is general gist of the session: 

  1. Session moderator shares screen with the participants and interacts on behalf of them. BETA
  2. Moderator puts the issues to be estimated in a pile.
  3. First participant places top issue on the virtual wall.
  4. Next participant places top issue on the virtual wall relative to 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)
  5. Next participant may:
    • either place 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
  6. The team continues to take turns placing issues until the pile is finally depleted and all issues are on the virtual wall.
  7. It is the time to fine-tune the order by moving issues one at a time with a few words of explanation.
  8. When everybody is OK with the outcome, the issues are ordered left to right, smallest to largest.
  9. The last step is to assign estimation value corresponding to each column (usually with Fibonacci sequence).
  10. Save the assigned values to the issues.


See how it works here:

Creating relative estimation session

  1. On the sessions dashboard view, click the "Create session" button.
  2. On the "Create new session" popup choose "Relative estimation" and click "Next":


  3. Choose issues you want to estimate (session scope) and click "Next" to create your new relative estimation session.

Issue placement phase

  1. While in the session page, drag the issues from the deck (left screen side) to the virtual wall (right screen side): 
  2. Continue dragging issues from the deck. You can drop the issue in the following places:
    1. under existing column (if item is comparable in size)
       
    2. to the left (or right), if the item is considerable smaller (greater) than existing issues on the wall:
    3. stick the issue between two existing columns:
       

Placing estimates

  1. 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

  1. 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:
  2. You will be prompted with a dialog asking you where to store the results:
  3. Choose the desired field to update and click Save button.


Limitations and caveats

Current implementation stores the session state in the browser local storage. This has following implications:

1) your browser must support local storage and have it enabled
2) you can't involve people in the session otherwise than sharing screen with them - people either need to be in the same place (e.g. conference room) or use some screen sharing service
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 session are not listed on the dashboard nor on the dropdown lists


Further readings 

Keep in mind the following resources are not created nor maintained by Spartez, but you still might benefit from them:

https://www.thedroidsonroids.com/blog/the-best-way-of-estima…

Detailed explanation of the Team Estimation Game method. Good for introductory reading.
http://www8.cs.umu.se/kurser/5DV151/VT15/lectures/slides/f4_…

One-paged "cheat sheet" for the Team Estimation Game.

http://www.agilelearninglabs.com/2012/05/how-to-play-the-tea…

Another explanation of Team Estimation Game. Less pictures, but with more verbose examples.

https://www.amazon.com/Practical-Estimation-Dependable-Pr…Kindle pocked guide about Team Estimation, written by the technique author.
http://tracks.roojoom.com/r/2258#/trek?page=4Short comparison between Planning Poker, Magic Estimations and Team Estimation Game.
https://systemagility.com/2011/05/22/using-silent-grouping-to-s…Detailed explanation of the Silent Grouping method.
https://www.wibas.com/scrum/magic-estimation/enIntroductory explanation to the Magic Estimation method, with a bit of hints.




  • No labels