Project name: Unrefined
Project URL: https://unrefined.one
Project sources: https://gitlab.com/fpischedda/unrefined
Unrefined's UX for estimations is centered on the estimation cheatsheet, with the assumption that it would help engineers to breakdown tasks to smaller items and assign a number to each of them.
A cheatsheet provides a list of breakdown items such as:
For each item there is a description of the possible actions for example, considering implementation:
With the guidance of the cheatsheet, over time it will become easier and more predictable how to estimate a task, getting to consensus much faster.
One thing it does NOT is to make estimations more ACCURATE! Estimations are gut feeling predictions of how much it could take to complete a task, and should NOT be used to set deadlines.
Here is how it looks in Unrefined's estimation section
The current implementation comes from our experience at $work so it is very specific to our needs, making not so useful for other team in a different domain, with different tech stacks and so on.
For this reason I have started to abstract away the breakdown items and their description but it is clearly very hard to come up with something that can capture every possible permutation of stacks, habits, business domain and what not. This is a source of frustration because it makes it harder to market the tool to other teams.
I am not sure how to proceed with the cheatsheet but I have some ideas:
I think that all of the above options are viable and would help to make this tool more useful to a broader audience, maybe even outside the software engineering circle.