Reluctantly accept that most developers will always gravitate toward time-based estimates, even if there's evidence saying that it's not a good idea. Instead of dying on this hill over and over, embrace time estimates using the rule of two. Instead of "points", use
- minutes
- hours
- days
- weeks
- months
Where the upper limit on each is exactly two of the next unit. e.g., a "minutes" estimate would be work that takes anywhere between 1 and 120 minutes, since that is two hours. An "hours" estimate would be take between 2 and 16 (work) hours, or two days. And so on.
Reluctantly accept that most developers will always gravitate toward time-based estimates, even if there's evidence saying that it's not a good idea. Instead of dying on this hill over and over, embrace time estimates using the rule of two. Instead of "points", use
Where the upper limit on each is exactly two of the next unit. e.g., a "minutes" estimate would be work that takes anywhere between 1 and 120 minutes, since that is two hours. An "hours" estimate would be take between 2 and 16 (work) hours, or two days. And so on.