Mythology sprint names

Because the names come with meaning attached. Icarus, Phoenix, and Hydra each tell a one-word story that maps neatly onto how software work actually goes — over-reach, rebirth, and problems that multiply. That gives the team a shared shorthand: “this is turning into a Hydra sprint” needs no explanation.

Creatures and stories (Kraken, Odyssey, Valkyrie) tend to work better than gods alone, because there are more of them and they’re less likely to collide with product or server names already using Zeus and Apollo. Mixing Greek and Norse also widens the pool — Fenrir and Valkyrie sit comfortably next to Cerberus and Atlas.

Each sprint takes the next letter: Atlas, Basilisk, Cerberus, Draugr, Echidna… One pass covers about a year of two-week sprints, and the ordering doubles as a timeline — anyone can see that the “Minotaur” incident happened after the “Kraken” release. When you finish the alphabet, start again with new names or switch themes.

Split the pantheons: one team takes Greek, another Norse, a third Egyptian. Sprint names mostly live inside a team, but shared dashboards and release calendars get confusing fast if two squads both have a “Phoenix” sprint in flight.