i always think of story points as "function points ( as in IFPUG[0] ) for lazy people". It should measure complexity[1] of a task. The time dimension will come

i always think of story points as "function points ( as in IFPUG[0] ) for lazy people". It should measure complexity[1] of a task. The time dimension will come later, after you have some perpective on your team's technical skills ( "oh, on average they can produce N magical-points over each day/week/month", what Joel calls 'evidence-based scheduling'[2] ). [0] https://www.codeproject.com/Articles/8151/Using-function-point-to-quote-a-software https://www.codeproject.com/Articles/8151/Using-function-poi... [1] https://ciandt.com/us/en-us/complexitypoints https://ciandt.com/us/en-us/complexitypoints [2] https://www.joelonsoftware.com/2007/10/26/evidence-based-scheduling/ https://www.joelonsoftware.com/2007/10/26/evidence-based-sch...