Poker

Planning Poker Web Application

This is a web application built with Socket.io, React-Spring, and Tailwind CSS that allows software development teams to estimate tasks using the Planning Poker technique. Link to the WIP application: https://poker-p0x6.onrender.com/

What's plannig poker?

Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used for timeboxing in Agile principles. You can read more on the topik on wiki.

Rationale

There are many similar applications out there with similar functionality, but every one have some downfalls (eg. paid premium, too simple and urly of a design, too complicated and ugly of a design etc.). I decided to take it uppon myself to change it creating the most simple but tastefully designed application for such and easy but impotant task.

Technologies

• React 18
• React-Spring
• Express.js
• Socket.io
• Tailwind CSS

Installation

To install the application, follow these steps:

1. Clone the repository to your local machine.
2. Navigate to the project directory and run yarn install to install the necessary dependencies.
3. Run yarn build to build the application.
4. Run yarn start to run the application.

Usage

To use the application, follow these steps:

1. Open the application in your browser at http://localhost:3000.
2. Create a new room or join an existing one using the room code.
3. Once all team members have joined the session, the facilitator can start a new round of estimation.
4. Each team member will be presented with a set of cards representing different estimates.
5. Each team member selects a card representing their estimate for the task.
6. Once all team members have submitted their estimates, the facilitator reveals everyone's estimates and leads a discussion to reach a consensus on the estimated effort required for the task.

Contributing

If you would like to contribute to the project, please follow these steps:

1. Fork the repository to your own account.
2. Clone the forked repository to your local machine.
3. Create a new branch for your changes and switch to it.
4. Make your changes and commit them with a descriptive message.
5. Push your changes to your forked repository.
6. Open a pull request from your branch to the main repository.

License

This project is licensed under the MIT License - see the LICENSE file for details.