Why I Built Pointwise: Making Software Estimation More Collaborative
Pointwise Product Updates | Part 1 of 4
When I started building Pointwise, I wasn't trying to reinvent planning poker.
I wanted to solve a fairly familiar problem: software estimation often becomes disconnected from the work we're actually discussing.
The problem with estimation meetings
If you've worked in a software development team, you'll probably recognise the process.
A team gets together to estimate upcoming work. Someone shares their screen, opens a ticket, and walks everyone through the requirements.
Then the estimation begins.
People switch between the issue tracker, a planning poker tool, and whatever application they're using for the meeting.
Sometimes the discussion is productive. Other times, the estimates arrive before everyone has properly understood the requirements.
And occasionally, the most experienced engineer gives their estimate first, which can influence everyone else's thinking.
None of these problems is particularly dramatic on its own. But together, they can make estimation less useful than it should be.
Keeping the work at the centre of the conversation
I wanted Pointwise to work directly with GitHub issues.
Instead of copying requirements into another application or constantly switching between tools, the team can keep the issue visible throughout the estimation session.
The idea is simple: everyone should be estimating the same piece of work, with the same information available.
Each participant submits their estimate independently, without seeing anyone else's score.
Once everyone is ready, the session leader reveals the estimates together.
If the scores differ, that's where the useful conversation begins.
Why does one engineer think the work is straightforward while another sees considerably more complexity?
Has someone identified a dependency, an unclear requirement, or an implementation risk that others missed?
Those conversations are often more valuable than the eventual number.
Building something I wanted to use
I'm a Senior Software Engineer, and Pointwise began as an independent project built around my own experience of software delivery.
I wanted something lightweight, practical and integrated with the tools development teams already use.
GitHub was the natural starting point.
Over time, the project developed into a production SaaS application with collaborative estimation sessions, GitHub integration and optional AI-assisted issue reviews.
But the original objective hasn't changed.
Better estimates should come from better conversations, not simply collecting numbers.
Where Pointwise is today
Pointwise is now live and available to try.
Teams can connect their GitHub repositories, select an issue and run collaborative estimation sessions without losing sight of the requirements.
There's also an optional GitHub Copilot review feature, which I'll cover in a later update.
I'm continuing to develop the application and would particularly welcome feedback from developers, engineering leads and Agile practitioners.
If your team estimates GitHub issues, I'd be interested to hear what works well in your current process and what frustrates you.
Try Pointwise: https://pointwise-estimates.tech
See how it works: https://pointwise-estimates.tech/how-to
GitHub Marketplace: https://github.com/marketplace/pointwise-estimation
Next in the series: Bringing Planning Poker into GitHub, and how independent estimates, simultaneous reveals and shared issue context work together.

Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.