I don't think that's the intent, but that's definitely how I've seen it implemented, either through spending lots of time comparing velocities, trying to optimi

I don't think that's the intent, but that's definitely how I've seen it implemented, either through spending lots of time comparing velocities, trying to optimize burndowns, or making equivalencies like 1 point = 1 day (that company also allowed estimating at the 1 hour granularity). That said, when done well, I think there are benefits to elements of Agile, but one really has to buy in to the fact that average velocity or similar metrics far more useful for looking at what might be delivered in several months, not what will be delivered in 2 weeks. It _can_ be done right, but I think that's the exception and not the rule.