If briefly, developers estimate tasks in clean hours (or minutes), that's approximate time they need to implement this particular job (without taking into account time required for solving technical problems, meetings, reading manuals and so on). As a rule, developers can estimate clean hours rather accurately. But not dirty hours – they are less predictable for most of us.
When working on tasks, developers specify clean and dirty hours spent on them. Based on different estimates, we can calculate the coefficients of performance and accuracy of all developers and more accurately estimate the deadlines in the future. We plan to use AI later to obtain more accurate deadlines on the basis of these coefficients and collected statistics.
If briefly, developers estimate tasks in clean hours (or minutes), that's approximate time they need to implement this particular job (without taking into account time required for solving technical problems, meetings, reading manuals and so on). As a rule, developers can estimate clean hours rather accurately. But not dirty hours – they are less predictable for most of us.
When working on tasks, developers specify clean and dirty hours spent on them. Based on different estimates, we can calculate the coefficients of performance and accuracy of all developers and more accurately estimate the deadlines in the future. We plan to use AI later to obtain more accurate deadlines on the basis of these coefficients and collected statistics.
As far as I remember, we have described why we don't support points estimation here: https://riter.co/blog/time-estimation-missteps.