STORY POINTS ARE POINTLESS, MEASURE QUEUES

Summary from the TLDR Web Dev newsletter

Story points, used to estimate effort in Agile development, are unreliable due to their relative nature and inherent variability. Velocity, which converts story points into time, further worsens this problem by creating unrealistic deadlines and discouraging teams from exceeding expectations. A better approach is to break down projects into smaller tasks, creating queues, and tracking the average task rate, which provides a more reliable way to project completion times and adjust for scope changes.