[MiquelLHC]

I am super excited to share with you the project I've been working on since January!

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

[Clex]

The words "poker online" will trigger all the antispams you can think of

[MiquelLHC]

yes good point! It is in the domain name so it will be difficult to get rid off it hehe I will think about it though, thanks!

[woodrowbarlow]

yeah, my work firewall blocked the site as 'online gambling'. i suspect this is going to be a common challenge when trying to get businesses to use your site.

[ollyculverhouse]

Looks nice! We have been looking at improving our sprint planning process and going to try this out today (instead of our typical spreadsheet!)

[MiquelLHC]

I hope you like it! :)

[nautilus12]

My issue with planning poker (and estimates in general) is that there is still a social pressure to push your estimates down as far as possible and ignore reality. I still think deadlines and limiting scope is the way to go.

[alistairSH]

How do you fix the deadline and scope without estimates?

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).

[yachtman]

Estimates for anything sufficiently complex are pure fantasy. They just serve to place an engineer in a bargaining conundrum and makes them implicitly decrease the scope for the 1000's+ decisions they will need to make during the course of implementation that they are not going to deliver the desired (also implicit) expectations. Its better to work from deadlines, then at least the engineer can try to hedge down the scope and deliver something they are comfortable with.

[suls]

And where are the deadlines coming from?

[lonelappde]

That's a people problem not a poker problem.

[NoNonsense118]

Are you using any CSS frameworks?

[MiquelLHC]

No, only CSS modules (https://github.com/css-modules/css-modules). It is already included as a feature in CRA https://create-react-app.dev/docs/adding-a-css-modules-style...

I like it because I don't need to worry about naming conflicts so I can speed up development a bit.