Bringing Planning Poker into GitHub

by•

Pointwise Product Updates | Part 2 of 4

In my previous update, I talked about why I started building Pointwise and some of the frustrations I've experienced with software estimation.

This time, I wanted to explain how the core estimation experience works and why I decided to build it around GitHub.

Estimation should start with understanding the work

One of the things I've noticed during estimation sessions is how easily the conversation can become focused on the numbers.

Is this a 3, a 5 or an 8?

But the number itself isn't particularly useful unless everyone understands what they're estimating.

A GitHub issue might contain acceptance criteria, implementation details, dependencies, technical constraints and conversations between contributors.

All of that information matters.

When teams move into a separate estimation tool, that context can become secondary. Someone ends up switching between browser tabs or sharing their screen to keep everyone informed.

I wanted Pointwise to remove as much of that friction as possible.

Keeping GitHub issues visible

Pointwise connects directly to GitHub, allowing teams to select issues from their repositories and estimate them collaboratively.

The issue remains available throughout the session, so participants can refer back to requirements and supporting information while discussing the work.

There's no need to duplicate tickets or maintain a separate backlog.

GitHub remains the source of truth.

Pointwise simply provides the collaborative estimation experience around it.

Independent estimates, without influencing each other

Another important decision was to keep estimates hidden until everyone has submitted their score.

I've been in estimation meetings where an experienced engineer gives their estimate early, and the rest of the team quickly gravitates towards it.

That doesn't necessarily mean anyone is deliberately influencing the discussion.

It's just human behaviour.

But it can mean that different perspectives never really surface.

In Pointwise, participants choose their estimates independently.

The scores remain hidden until the session leader reveals them simultaneously.

This gives everyone the opportunity to form their own judgement before seeing what others think.

The differences are where the value is

Imagine three engineers estimating the same issue.

One chooses 3 story points, another chooses 5, and the third chooses 13.

That difference is interesting.

Perhaps the engineer who selected 13 has identified a dependency that wasn't obvious.

Perhaps the engineer who selected 3 knows there's already an existing component that solves most of the problem.

Or perhaps the requirements simply aren't clear enough.

The purpose of revealing estimates together isn't to identify who's right or wrong.

It's to expose those differences and encourage the team to understand them.

Once the discussion has taken place, the team can work towards a shared estimate.

The number is the outcome. The conversation is the valuable part.

Building the experience around the team

I also wanted Pointwise to feel lightweight.

A session leader can create an estimation session, invite contributors and select the GitHub issue to discuss.

Participants can submit their estimates, reveal scores together and move on to the next issue.

The aim is to support the meeting without turning the tool itself into another thing everyone has to manage.

Underneath that relatively simple interface, there's quite a bit of engineering involved in keeping session state consistent between participants.

I'll cover more of the technical decisions behind Pointwise in a future update.

What's next?

The core planning poker experience was the foundation of Pointwise.

But during development, I started exploring another question:

What if AI could help teams identify missing requirements, risks and unanswered questions before they commit to an estimate?

That led to the optional GitHub Copilot review feature, which I'll cover in Part 3.

In the meantime, Pointwise is available to try, and I'd welcome feedback from teams already using GitHub for their development workflow.

Try Pointwise:

See how it works:

GitHub Marketplace:

A question for developers and engineering teams:

When your team estimates work, do you find the biggest challenge is agreeing on the number, or making sure everyone has understood the requirements in the same way?

7 views

Add a comment

Replies

Be the first to reply

Have a question or a thought to share? Add a comment above to start the conversation.