Time logged
Uses the time logged on the issue. You can optionally include time logged on its sub-tasks.
Estimation Insights
Learn from your estimates
Insights compares the estimates your team agreed on in Pokerly with the effort the work actually took, so you can see how well your estimates hold up over time.
How actual effort is measured
Choose the method that matches how your team works.
Cycle time
Measures the time between two statuses you choose, for example from “In Progress” to “Done”. You can optionally count weekdays only.
What the report shows
- Accuracy %
- How closely estimates matched the actual effort.
- Team pace
- Hours per point, based on the effort measured for estimated issues.
- Under- and over-estimated issues
- The issues where the estimate and the actual effort differed.
- Rounds per issue
- How many voting rounds each issue needed before the team settled.
- Effort per estimate chart
- Actual effort plotted for each estimate value.
- Calibration table
- Each estimate value alongside the actual effort it took.
Each issue, side by side
Every estimated issue is listed with its estimate next to the effort it took:
Estimated: 5 points · Actual: 11h
Example format. Your report uses your own issues and effort data.
Setting it up
- Open Pokerly Settings (Jira admins can always open Settings).
- Choose how actual effort is measured: time logged, or cycle time between two statuses.
- Set the options for that method: include sub-tasks, or count weekdays only.
- Keep estimating in Pokerly. Estimation history is recorded per session and issue and feeds the report.
Estimation history is kept for Insights until the app is uninstalled. See thedata and privacy statement.