How does Rekall work?

Estimating issues using Rekall is easy as

Step 1

First, select the issue that you need to estimate. This should be the issue at the top of the first column in the Triangulation Board since Rekall has displayed the unestimated issues in the same order as the one found in your product backlog.

Step 2

Next, browse the issues that your team have executed in past sprints by using the Story Points Selector located in the top right corner of the Triangulation Board. You can directly go to the desired story points number or use the arrows to sequentially see the issues across all the story points. The previously executed issues are displayed in the second and third columns of the Triangulation Board so that you can always compare your unestimated issue with possibly bigger or smaller issues.

Step 3

Once you have found previously executed issues that are similar in size to the one you need to estimate, simply drag and drop your unestimated issue over the column containing the similar issues. Rekall will assign it the same number of story points and will confirm you the estimate.

Behind the curtain

Although the estimation process using Rekall is relatively simple, a lot of work is actually performed for you in the background.

Selection of unestimated issues

Rekall will present to you the issues that have not yet been estimated. It will display them in the same order as they were found in your product backlog. If your product backlog is properly groomed, then you just need to take the one at the top of the column since it should be among the first issues to be implemented next.

Selection of executed issues

Rekall will crawl past sprints to find issues that were previously executed. An executed issue is an issue that has work logs and for which the status is generally either "Closed" or "Resolved". It will take these issues, find the number of story points that were assigned to them and sort them out accordingly. Since the number of issues presented in the Triangulation Board is limited, Rekall will take, for each story points, the 10 issues that took the longest time to implement and the 10 issues that took the least time to implement. When Rekall shows you the executed issues, it will display them in a specific order to help you out making the best decision possible. Rekall will sort the issues in the second column from highest time spent to lowest time spent and from lowest time spent to highest time spent in the third column. This gives you a unique view on the transition from one story points estimate to the next.