Fox Studios logo Fox StudiosGame projects, devlogs and Scratch builds
Tools

Kanban Board for Game Development a Small Team Keeps Current

Three weeks into a project, the task list stops matching reality. Someone fixed the jump bug but never moved the card, the art backlog has 60 items nobody has looked at, and the question "what are you working on?" gets a different answer...

A whiteboard covered in colorful sticky notes arranged in columns next to a monitor showing a pixel art game

Three weeks into a project, the task list stops matching reality. Someone fixed the jump bug but never moved the card, the art backlog has 60 items nobody has looked at, and the question "what are you working on?" gets a different answer from the board than from the person.

A kanban board for game development only helps if it stays current without anyone policing it. After running boards for four small projects, two game jams and one port, we have settled on a setup that a team of two to five people actually keeps updated. Here is the layout, the rules, and the parts we threw away.

Why a kanban board for game development beats a long task list

A task list tells you what exists. A board tells you where everything is right now. That difference matters in games because work moves between disciplines constantly: a level needs art, then code for a new enemy, then a playtest, then fixes from that playtest.

Kanban also avoids the overhead of sprints. A small studio rarely has a stable two week rhythm, especially when people work evenings or part time. A board with limits on work in progress gives you most of the focus benefit of sprints with none of the planning meetings.

The five columns we use

More columns mean more cards stuck between them. We use five and resist adding a sixth.

ColumnWhat goes hereLimit
BacklogAgreed tasks for the current milestoneAbout 40 cards
This WeekWhat the team commits to before the next check in3 per person
DoingActively being worked on today2 per person
TestBuilt and waiting for someone else to play it6 total
DoneTested and mergedArchived every Friday

The Test column is the one most teams skip, and it is the one that saved us. A feature is not done when the code compiles. It is done when someone other than its author has played it in a build. When Test fills to six, everyone stops pulling new work and plays builds until it drains.

Writing cards people can actually finish

A card should describe something one person can finish in one to three working sessions. "Make the boss fight" is a milestone, not a card. Split it until every piece has a clear finish line:

  • Boss idle and attack animations, 4 frames each
  • Boss phase two triggers at 50 percent health
  • Arena camera locks during the fight
  • Playtest the fight three times and log deaths

Every card gets a short title that starts with a verb, an owner, and one sentence on how to verify it. Labels stay minimal: we use art, code, audio, design and bug, color coded. If you write a design document, link the relevant section from the card instead of copying text into it. Our guide to writing a game design document a small team will use explains how we keep those sections short enough to link.

Which tool to pick

The tool matters less than the rules, but some fit small game teams better than others.

  • Trello is quick to learn and free for a small team. It gets slow to scan once a board passes about 150 cards, so archive weekly.
  • GitHub Projects makes sense if your code already lives on GitHub, because cards link directly to issues and pull requests. Artists who never open GitHub may resist it.
  • HacknPlan is built for game development, with boards per discipline and a design model tied to tasks. It suits teams that want structure from day one.
  • A physical board with sticky notes works well for a jam or a shared room, and nothing else matches how visible it is.

We use Trello for most projects and a whiteboard during jams. For the rest of our free setup, see the free tools a small game studio actually uses.

The advice we stopped following

The usual recommendation is to put everything on the board: every idea, every bug, every "wouldn't it be cool if" from a playtest. The logic is that nothing gets lost.

We tried that on our platformer and ended up with 230 cards in the backlog, half of them ideas nobody had agreed to build. The board became a wish list, and people picked fun tasks over necessary ones. Morale actually dropped, because the backlog never seemed to shrink.

Now ideas go into a separate document we call the parking lot. Once a month we read it together and promote, at most, five ideas to the board. Bugs go on the board only if they block play or ship in the next build. Cosmetic bugs live in the issue tracker. The backlog stays near 40 cards, and finishing a week of work visibly moves it.

A weekly routine that keeps it honest

The board stays current because of a 15 minute check in every Monday and one rule: you move your own cards the moment their status changes.

  1. Everyone reads the Test column first and claims something to play.
  2. Each person pulls up to three cards into This Week.
  3. Anything in Doing for more than five days gets split or discussed.
  4. On Friday, Done gets archived and the team looks at what shipped.

Link cards to the actual work wherever you can. A code card should point to its branch or commit, and an art card should point to the file in the shared folder, not a screenshot pasted into a comment. When large art and audio files live in version control, the card link stays valid for the whole project. Our notes on Git LFS for game projects explain how we keep those big files manageable.

That Friday look back is small but important. Seeing 14 archived cards after a rough week reminds a tired team that the project is moving.

Frequently asked questions

Is kanban or scrum better for indie game development?

For teams under five people with irregular hours, kanban usually fits better because it needs no sprint planning or fixed cycles. Scrum can work for a full time team with a publisher deadline. Many small studios borrow one scrum habit, a short weekly check in, and run everything else as kanban.

How many columns should a game dev kanban board have?

Four to six is the practical range. Backlog, In Progress and Done is the minimum, and a separate Test or Review column catches features that work only on their author's machine. Beyond six, cards tend to stall between stages.

What is a good WIP limit for a small game team?

Start with two cards in progress per person and adjust after a few weeks. If people often wait on someone else, raise it to three. If cards linger in progress for over a week, lower it and split the tasks smaller.

MK
Mira Kovac

Mira teaches coding to beginners and writes the step-by-step guides, always testing each one on someone who has never coded before.

More posts by Mira

More in Tools

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips strcoding tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto ankertoto