The problem with story points

Story points, originally created to provide an abstract measure of effort in software development without committing to specific timelines, have become a contentious issue in engineering organizations, often leading to miscommunication and misaligned expectations. They are criticized for conflating complexity, time, and risk into a single number, which creates ambiguity and false precision. This has led to the misuse of velocity for comparison, encouraging teams to inflate estimates to protect perceived output, ultimately diverting focus from delivering actual value. Instead of relying on story points, measuring work cycle time and analyzing developer activity, such as through Swarmia's FTE model, provides more accurate insights into productivity and effort distribution. This shift allows teams to forecast completion dates based on historical data rather than unreliable velocity estimates, enabling more meaningful conversations about improving workflow efficiency. By focusing on actual work progress and bottlenecks, teams can better address systemic issues and enhance their ability to deliver value, moving away from the outdated reliance on story points towards a more data-driven approach to project management.