Core concepts

A project that groups related Quests, such as Mobile App Redesign. Each Adventure has a short key (MAR) and runs on a Game Board. Learn more →

A deliverable piece of work inside an Adventure: a feature, a release, an initiative. Each Quest has an owner (its King), a closure date, a priority, a coin pool, and a Council. Learn more →

The three people who prepare a Quest before delivery: the Wizard (product), the General (tech lead) and the Alchemist (design). They gather requirements, produce the estimate, and send their work to the King. Learn more →

The Quest’s time, worked out from four factor scores. The AI proposes it from the Council’s Markdown materials, the Wizard approves it, and the General commits it. Learn more →

One piece of work in a Quest, done by one Hero. Each Step has a type (Development, Design, Testing, PM) whose workflow decides the statuses it moves through. Learn more →

A bug, logged as a Step, that can name the Step that caused it. Traps count in the Quest’s bug ratio and in bug governance. Learn more →

The template of phases (columns) a Quest’s Steps move across, and the step types allowed on it. Assigned to an Adventure and inherited by its Quests. Learn more →

Timing your work on a Quest with the header timer. Stopped sessions are allocated to the Steps you worked on. Learn more →

Experience points earned as Steps move forward and Quests complete. XP raises your level on a 36-level ladder. Learn more →

Q-Coins, a separate reward, won mainly in Expeditions: open challenges where the King picks up to four winners. Learn more →