erinrep/name_that_sprint

Sprint naming tool for fun. Phoenix and Elixir. React and Material UI using context for realtime socket communication via Channels.

Summary

NameThatSprint is a small Phoenix web application written in Elixir that lets a team brainstorm and vote on names for their upcoming sprint. The README describes it as a game where teammates join to propose ideas and pick their favorites. It is positioned as a lighthearted, internal-facing tool rather than a production product.

What it is useful for

This repository is useful for two practical cases. First, an engineering team that wants a low-effort way to make sprint planning more playful can run it locally and use it as a shared naming activity. The README frames it as something teammates "join" to come up with ideas and vote, so the workflow maps directly onto a short kickoff meeting.

Second, it can serve as a compact Phoenix project for Elixir developers who are learning the framework. The app is small and self-contained, and the README documents a standard Phoenix workflow: install Elixir, run mix setup, start mix phx.server, and visit localhost:4000. Because the description on GitHub is just "sprint naming tool for fun," there is no claim of broader functionality, so it should not be expected to replace any real sprint management tooling.

How engineers can use it

The README documents a straightforward local setup, assuming Elixir 1.10.4 or higher and npm are available. The steps it lists are:

1. Install Elixir 1.10.4 or higher (the README points to brew install elixir or elixir-lang.org for other options) and install npm from npmjs.com.
2. From the project directory, run mix setup to install and configure dependencies.
3. Start the Phoenix server with mix phx.server, or inside IEx with iex -S mix phx.server.
4. Open localhost:4000 in a browser to play.

For verification, the README notes that mix test runs the unit tests.

A few caveats based on the supplied material: the repository has no listed topics, no stated license, and the README is brief. Details such as how participants join from different machines, whether the app persists results between sessions, and how voting resolves ties are not described in the supplied material. Engineers looking for those answers would need to read the source or check with the maintainer.