For years, software development teams have meticulously sized tasks using methods like story points, t-shirt sizes, or ideal days.
We've been told these practices are essential for planning, predictability, and measuring progress. Yet, beneath this veneer of control, a silent drain on productivity, morale, and innovation persists.
This article argues that traditional ticket sizing is not just inefficient; it's a costly illusion, potentially contributing to billions of dollars in wasted effort annually across the industry.
It's time to challenge this deeply ingrained practice.
The fundamental premise of ticket sizing is to provide accurate estimates. However, human estimation is inherently flawed, especially for complex, uncertain software tasks.
Story points, despite their claims of abstractness, often devolve into thinly veiled proxies for time.
Teams spend countless hours debating sizes, only to find the actual effort diverges wildly from their initial predictions. This isn't a failure of the team; it's a failure of the method itself.
This pursuit of false precision creates a mirage of control.
Stakeholders receive numbers that feel concrete, yet they fail to reflect the true complexity, unforeseen challenges, or shifting requirements inherent in software development.
The result is often unmet expectations, eroding trust between development teams and the business, and leading to a cycle of re-estimation and frustration rather than genuine progress.
Consider the sheer volume of time dedicated to sizing activities.
Planning poker sessions, estimation meetings, re-estimation discussions, and the constant negotiation over points consume valuable developer hours.
These are hours that could be spent coding, designing, testing, or collaborating on actual product delivery. This overhead isn't just a minor inconvenience; it's a significant opportunity cost.
In a world where every minute counts towards delivering value, diverting precious engineering time to an activity with questionable returns is counterproductive.
This constant focus on predicting the unpredictable distracts teams from their core mission: building great software efficiently.
The cumulative effect of this time sink across thousands of software teams worldwide represents a staggering loss of potential.
Beyond the direct time investment, the reliance on ticket sizing often leads to detrimental management practices.
Teams are frequently pressured to "hit their points," fostering a culture focused on output metrics over outcome.
This can inadvertently encourage practices like inflating estimates to create buffer, or rushing tasks to meet arbitrary point targets, compromising quality and sustainability.
Furthermore, sizing can obscure the true bottlenecks in a workflow. Instead of identifying and resolving systemic issues, the focus remains on individual task estimates.
This misdirection prevents organizations from adopting lean principles, optimizing their flow, and truly understanding their capacity.
The result is often delayed projects, increased technical debt, and a perpetual struggle to deliver on commitments, directly impacting business objectives and the bottom line.
The constant pressure associated with sizing takes a significant psychological toll on software professionals.
Developers often feel judged by their estimation accuracy rather than their problem-solving skills or the quality of their work.
This can lead to stress, burnout, and a defensive mindset, where the goal becomes to protect one's estimates rather than transparently collaborate on solutions.
The arbitrary nature of points can also foster internal competition and resentment, undermining the very team cohesion agile methodologies aim to promote.
When teams are forced to defend their estimates, or when their "velocity" is used as a blunt instrument for performance evaluation, it destroys trust and creativity, ultimately leading to disengaged teams and higher turnover rates.
This human cost is often overlooked but profoundly impacts long-term organizational health.
If not sizing, then what? The answer lies in shifting our focus from estimation to flow, value delivery, and continuous improvement. Here are key strategies to adopt:
The move away from traditional sizing is not about abandoning planning; it's about adopting smarter, leaner planning that aligns with the realities of software development.
It means trusting our teams to deliver value and providing them with the tools and environment to do so efficiently.
The time has come to critically re-evaluate our reliance on ticket sizing and story points.
While well-intentioned, these practices often create more problems than they solve, leading to wasted time, organizational mismanagement, and significant psychological strain on our valuable software teams.
The "$50 billion lie" isn't a single falsehood, but the cumulative cost of these inefficiencies.
By embracing lean principles, focusing on small increments, managing flow, and prioritizing empirical metrics like throughput and cycle time, we can liberate our teams from the estimation trap.
It's an opportunity to foster greater agility, enhance productivity, and build more engaged, effective software development organizations.
The future of software delivery demands a shift towards practices that truly empower teams to deliver value, not just estimates.
For further reading on alternatives, consider exploring concepts like Flow Efficiency and Kanban methodologies.
Hey friends, thanks heaps for reading this one! 🙏
If it resonated, sparked an idea, or just made you nod along — I'd be genuinely stoked if you'd show some love. A clap on Medium or a like on Substack helps these pieces reach more people (and keeps this little writing habit going).
→ Pythonpom on Medium ← follow, clap, or just browse more!
→ Pominaus on Substack ← like, restack, or subscribe!
Zero pressure, but if you're in a generous mood and fancy buying me a virtual coffee to fuel the next late-night draft ☕, you can do that here: Buy Me a Coffee — your support (big or tiny) means the world.
Appreciate you taking the time. Let's keep chatting about tech, life hacks, and whatever comes next! ❤️