Show HN: Planning poker online – estimate tasks without influencing others
planningpokeronline.com
planningpokeronline.com
Planning poker, also called Scrum poker, it is a simple cards game where teams can estimate the effort of tasks in software development.
The goal of the app is to allow remote teams to play it in a simple and funny way.
It is used by 1k daily users and we are getting the first premium subscriptions.
We want to keep improving it so any feedback is appreciated.
Tech stack (my favourite as it is super agile): - React (CRA with typescript) - Firebase - Stripe
I like it because I don't need to worry about naming conflicts so I can speed up development a bit.
Within my teams, estimating doesn't appear to have downward pressure. Team members appear to want to estimate correctly because they want to have a realistic and steady workload. Driving down estimates means their workload goes up (at least in the short term, until our average velocity adjusts).
Sidenote: Planning poker is a registered trademark [1]. I hope you don't run into any legal issues.
[1] http://tsdr.uspto.gov/#caseNumber=3473287&caseType=US_REGIST...
Thanks for legal advertisment.
Having the word Scrum and Agile on the homepage, explaining the problem and solution statement could help a lot.
For those who know what planning poker is, the landing page is very clear.
More generally: Tech is absolutely rotten with jargon, most of which is assembled from pre-existing words that have different meanings in their original context. I don't think it does us much use to complain about this fact whenever we get tripped up by it. Nobody wants to have to always define the context of their jargon before using it in order to avoid confusion any more than they want to use XML Schema and qualify the names of their tags at all times. It would just be a horrible chore. It will be quicker and easier for everyone if we just learn these bits of jargon ad-hoc, and accept the occasional moments of mild confusion as part of the job.
for me, the most valuable part of planning poker is when we see one vote that's way out of line with the rest, and that person explains their thinking, and some important discussion can take place. with asynchronous voting, i would imagine you'd get a fair bit of "oh, yeah, to be honest i don't remember why i gave that one an XL".
to be honest, i don't even see the point of keeping votes anonymous. if there's enough judgement in the room that people are ashamed to honestly say how difficult a task would be for them, i think that's a larger problem.
Judgement is potentially a problem.
But, beyond that, seeing votes could lead more timid team members to simply wait for the tech lead (or a boisterous team member) to vote and follow along.
With async 5 of those people can work on something else when 2 or 3 have questions or ideas about the story.
@MiquelLHC Welcome to the Atlassian marketplace =) Good to have new vendors there to compete with)
1. When all players in the game have voted, just turn the cards to show the results right away
2. The tutorial moving around the screen was only ever so slightly annoying, wish it stayed in the one spot (or let me advance using arrow key on keyboard or something?) so I could just click through and read faster
3. I assume the link we get given is persistent and never expires? We'd want to have it as part of a recurring slack call for example without having to generate a new one each week.
EDIT: 4. I didn't think to click my username arrow to see all the menu options (especially 'Go unlimited') you may want to consider making at least that a bit more prominent.
Nice work.
About point 3: yes, game urls are persistent and never expire but only in premium version, for free users games expire after a certain amount of votings. (Only game's creator needs to be premium)
Thanks for your time!
I've shared it internally, excited to see if teams decide to use it. So far we've seen everything from spreadsheets to physical cards being used.
Congrats!
White page.
No, I won't allow localStorage just to see your homepage.
> Could not reach Cloud Firestore backend. Backend didn't respond within 10 seconds.
https://ultimateplanningpoker.com/
Downloadable: https://github.com/spelinbedrijf/ultimateplanningpoker