Intro
Story points are a often used by agile teams - but in my experience, they’re often misunderstood or misused. With the right approach, however, story points can do more than just help estimate effort. They can actually foster the psychological safety and open communication that high-performing teams need.
The Secret Behind Effective Teams
Making tech teams effective is the key responsibility of CTOs and leaders in tech. One of the most influential resources on this topic is Google’s “Project Aristotle.” Their research found that the highest-performing teams share a crucial trait: a culture where everyone feels safe to speak up.
When team members know their voices matter, they’re more likely to contribute ideas, raise concerns, and collaborate productively. Unfortunately, not all teams operate this way. In some, strong leaders dominate, handing out assignments and expecting everyone to fall in line. While this might seem efficient, it ultimately limits collaboration and innovation.
Where Story Points Come In
So what does this have to do with story points?
At their best, story points are about more than just estimation - they’re about participation. In a typical refinement or estimation session, the team reviews new tasks or user stories together. Then, using planning poker, everyone reveals their estimates simultaneously.
This process does two important things:
- Ensures everyone is heard: When estimates vary widely (say, a “3” from one person and a “21” from another), it opens the door for discussion. Why did people see things so differently? What did one person notice that others missed?
- Builds shared understanding: By talking through these differences, the team arrives at a common understanding of both the task and the challenges involved. This means everyone is better prepared to contribute.
More Than Just a Number
Story points aren’t just a number you assign to a task - they’re a tool for building stronger teams. When everyone is involved in the estimation process, you create an environment where people feel comfortable sharing their perspectives. This is the foundation of psychological safety and is key to building an effective, resilient team.
Conclusion
If you’re only using story points to track velocity or forecast deadlines, you’re missing out on their true value. Use them as a way to spark conversation, encourage participation, and build understanding across your team.
