How to Use a Kanban Board for Game Development
Six months into our second game, we had a 300 line to do list in a text file, three people working from different versions of it, and no idea how far from launch we really were.

Six months into our second game, we had a 300 line to do list in a text file, three people working from different versions of it, and no idea how far from launch we really were. Switching to a kanban board for game development fixed that in about two weeks. It did not make us faster at coding. It made us honest about what was finished, what was stuck, and what we were only pretending to work on.
Here is the exact setup we use at Fox Studios, why it is smaller than most templates you will find, and the mistakes that cost us time before we got it right.
What a kanban board for game development does
A kanban board is a set of columns that represent stages of work, with one card per task moving from left to right. The idea comes from manufacturing, but it fits games well because game work is full of small, uneven tasks: a sprite here, a bug there, a sound that needs replacing, a menu that needs a back button.
The board answers three questions at a glance:
- What is everyone working on right now?
- What is blocked, and by whom?
- How much is left before the next milestone?
A text list can technically answer those, but nobody reads a 300 line list every morning. Everybody glances at a board.
Picking a tool
We have tried four tools over the years. All of them work; the differences are mostly about price and where your code lives.
| Tool | Cost for a small team | Best for |
|---|---|---|
| Trello | Free for most small teams | Fast setup, non programmers on the team |
| GitHub Projects | Free with a repository | Teams already using GitHub issues for bugs |
| Codecks | Free tier, paid from about $8 per user monthly | Game specific features like playtest feedback |
| HacknPlan | Free tier, paid from about $5 per user monthly | Teams that want a game design document built in |
For a solo developer or a team of two, Trello or GitHub Projects is plenty. We use GitHub Projects now because cards link straight to commits, which matters when we track down when a bug appeared. If you are still choosing your wider toolset, our list of free tools a small game studio actually uses shows where the board sits next to everything else.
Our five column setup
Most templates come with eight or ten columns. We cut ours to five, and each one has a rule.
- Backlog. Every idea and task goes here. No rules, no sorting required.
- Next. The tasks we have agreed to do for the current milestone, sorted by priority. Maximum 15 cards.
- Doing. Work actively in progress. Maximum two cards per person.
- Review. Finished by the person who did it, waiting for someone else to play it in a build.
- Done. Tested in a real build, merged, and working. Cleared at the end of each milestone.
The limits on Next and Doing are the part people skip, and they are the reason the board works. When Doing is capped at two cards, you cannot start a shiny new feature until you finish or explicitly park something. That one rule cut our half finished features from around a dozen to two or three.
Writing good cards
A card should describe something you could demo. "Player" is not a card. "Player can double jump with a 0.2 second coyote time window" is a card. If a card would take more than two days, split it. We aim for most cards to take between two hours and one day.
Add a short "done when" line to every card that touches gameplay. For the double jump card, ours read: "Done when a tester can double jump off every ledge in level 2 without falling through the floor." That single sentence ends most arguments in Review, because the person testing knows exactly what to check and the person who built it knows exactly what they promised.
We also use three labels and only three: bug, art and blocked. Every extra label we added in the past ended up unused within a month.
Why we stopped estimating every card
Common advice for teams is to estimate every task in hours or story points. For a large studio with a producer, that probably helps. For a small team, we found it wasted time and gave false confidence.
Game tasks have wildly uneven sizes. A collision bug can take ten minutes or three days, and nobody knows which until they look. We spent about an hour a week estimating, and our estimates were off by more than double half the time.
Instead, we count cards. If we finished about 18 cards per week over the last month and there are 54 cards left in Next plus the milestone backlog, we are roughly three weeks out. Because we keep cards small and similar in size, the count is more accurate than our old estimates and costs nothing to calculate. It also lines up nicely with a release checklist for a small indie studio, since each checklist item can become a card.
Habits that keep the board alive
A board only works if it reflects reality. These habits keep ours honest:
- A ten minute check in, three times a week. Each person says what moved, what is stuck and what they will pull next.
- Cards move only when the build proves it. Nothing goes to Done because "it works on my machine."
- Backlog grooming once per milestone. We delete about a third of the backlog every time. Old ideas that nobody has argued for in two months go.
- Playtest notes become cards the same day. Feedback sitting in a chat log is feedback that will be forgotten.
For solo developers, the same rules apply with one change: replace the check in with a five minute note to yourself at the end of each session listing what you will pull next. Starting tomorrow with a decision already made is half the value of the board.
Frequently asked questions
Is kanban or scrum better for game development?
For small and solo teams, kanban usually fits better because it has no fixed sprint length and handles unpredictable bug work well. Scrum can help larger teams that need regular planning meetings and set deliverables. Many indie teams use kanban with milestone deadlines as a light middle ground.
Can a solo developer use a kanban board?
Yes, and it often helps more than for a team, because there is nobody else to notice when you drift. Keep the Doing limit at one or two cards. A short end of session note about what to pull next makes it easy to restart the following day.
What should be on a game development kanban board?
Small, testable tasks for code, art, audio, design and bugs, each written so someone could demo the result. Keep columns simple, such as Backlog, Next, Doing, Review and Done. Add work in progress limits so tasks get finished before new ones start.
More in Tools
Tools
Running Godot 4 on a Low Spec School Laptop Without Lag
Nine of the fourteen laptops in the Tuesday class I teach are the same kind of machine: a four or five year old 14 inch model,...
Tools
Devlog GIF Capture Tools and How to Shrink the Files
The best clip we ever recorded was six seconds of a boss slamming into a wall and dropping its shield, and almost nobody saw it...
Tools
Using butler to Upload itch.io Builds in One Command
We shipped a jam game last spring and then spent two days patching it.