...
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 user experience. The relative estimation mode is also heavily inspired by techniques known as Magic Estimation or as Magic Estimation or Silent Grouping, so knowing one should make you comfortable with the flow. Here is general gist of the session:
- Session moderator selects issues to estimate and shares his is going to share screen with the participants . Moderator is going to and 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 them.
Status colour Yellow title Beta - Put the issues to be estimated in a pile.
- First participant places top issue on 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 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 the already placed issue (forming a column, or a bucket)
- Another person Next participant may:
- either take another place issue from the deck and place it pile on the virtual wall with using the same rules as above
- move a single story card 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 deck pile 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 to each column - usually using Fibonacci sequence, and save the results (by default under Story Points custom field).
...
Loerm ipsum: talk about localStorage issue. + screenshots.
Further readings about technique
| Anchor | ||||
|---|---|---|---|---|
|
Keep in mind these resources are not created nor maintained by Spartez, but you still might benefit from them.
https://www.thedroidsonroids.com/blog/the-best-way-of-estimating-your-product-backlog-effectively-and-quickly - a detailed explanation of the Team Estimation Game method. Good for introductory reading.
http://www8.cs.umu.se/kurser/5DV151/VT15/lectures/slides/f4_Team_Estimation_Game.pdf - one-paged "cheat sheet" for the Team Estimation Game.
http://www.agilelearninglabs.com/2012/05/how-to-play-the-team-estimation-game/ - another explanation of Team Estimation Game. Less pictures, but with more verbose examples.
https://www.amazon.com/Practical-Estimation-Dependable-Project-Schedules-ebook/dp/B00SS794IQ - a Kindle pocked guide about Team Estimation, written by the technique author.
http://tracks.roojoom.com/r/2258#/trek?page=4 - a short comparision between Planning Poker, Magic Estimations and Team Estimation Game.
https://systemagility.com/2011/05/22/using-silent-grouping-to-size-user-stories/ - a detailed explanation of the Silent Grouping method.
https://www.wibas.com/scrum/magic-estimation/en - an introductory explanation to the Magic Estimation method, with a bit of hints.