Disagree, this is like arguing that "dollars ∝ apples" simply because you were able to buy apples today at a given price. It does not mean the relationship can--or should--be constant across all teams and all time forever.
IANACertifiedScrumLord, but reasons for "points" are:
1. Humans give less-reliable data when you ask them for hours, both because we're not wired to have that kind of time-sense (future or past) and also because it adds a kind of implicit peer pressure.
2. Humans are better at estimating "is it similar to that other thing I worked on recently", and points are the way to formalize those carry-over comparisons.
3. How human-teams think of (and deliver) work is variable both over time and variable across teams, which means their points are variable in the same ways.
4. Goodhart's law. You want to keep some separation between the measure and the target, that separation is between points and hours, and it's the job of whomever is running the sprints to be that kind of privacy-screen.
So the ideal outcome is that you allow the drift, and account for it by using a recent running-average for that team's delivered points (modified by vacation time etc) to generate your private time-estimates.
IANACertifiedScrumLord, but reasons for "points" are:
1. Humans give less-reliable data when you ask them for hours, both because we're not wired to have that kind of time-sense (future or past) and also because it adds a kind of implicit peer pressure.
2. Humans are better at estimating "is it similar to that other thing I worked on recently", and points are the way to formalize those carry-over comparisons.
3. How human-teams think of (and deliver) work is variable both over time and variable across teams, which means their points are variable in the same ways.
4. Goodhart's law. You want to keep some separation between the measure and the target, that separation is between points and hours, and it's the job of whomever is running the sprints to be that kind of privacy-screen.
So the ideal outcome is that you allow the drift, and account for it by using a recent running-average for that team's delivered points (modified by vacation time etc) to generate your private time-estimates.