What initial columns would you set up on a Kanban board?
Tests your grasp of Kanban's core goal: visualizing workflow. Start with a simple board (To Do, In Progress, Done), explaining how each column represents a work state. A red flag is creating an overly complex board without justifying the need for each stage.
What's really being asked
Your understanding of Kanban's first principle: visualizing the workflow. The interviewer is looking for a practical, simple starting point, not a complex, over-engineered process. They want to see that you understand the board is a tool to reflect the team's process, not impose a rigid one. It also tests your ability to communicate the purpose behind each element of the system.
The full answer
A good answer outlines a simple, three-part structure. First, a 'To Do' or 'Backlog' column, which holds prioritized but not-yet-started work items. Second, an 'In Progress' column for work that is actively being worked on by the team. This is the most critical column for managing flow. Third, a 'Done' column for completed work, which provides a sense of accomplishment and data for measuring throughput. A great answer also mentions that this is just a starting point and the board should evolve to reflect the team's actual workflow over time.
The mistakes people make
The most common red flag is proposing an overly complex board from the start. For example, suggesting columns like 'Analysis', 'Design', 'Development', 'Code Review', 'QA', and 'Done'. While these stages might eventually be needed, starting with them on day one for a new project assumes a process that doesn't exist yet. It shows a tendency to impose a rigid framework rather than discovering the team's natural workflow. Another mistake is failing to explain the purpose of the columns, simply listing them as if it's a vocabulary test.
What usually comes next
Be prepared for "How would you introduce Work In Progress (WIP) limits to this board?" or "When would you decide to add more columns, like 'Code Review' or 'Testing'?" Another likely question is "How does this board help the team identify bottlenecks?"
A concrete example
For a new software project, I'd start with three columns: 'To Do', 'In Progress', and 'Done'. 'To Do' contains all user stories prioritized by the product owner. Let's say we have 10 stories ready. 'In Progress' is for the 2-3 stories the team is actively coding. We'd set a WIP limit of 3 on this column to encourage focus. 'Done' is for work that meets our Definition of Done, meaning it's coded, reviewed, tested, and merged. This simple setup immediately shows us what's ready, what's being worked on, and what's completed, giving a clear picture of our flow.
Interview question
For a new team adopting Kanban, which initial set of columns is most recommended to visualize workflow effectively?
- a.Backlog, Ready, Working, Blocked, Review, Approved, Done
- b.A single "Tasks" column to list all work, and a "Completed" column
- c.Analysis, Design, Development, QA, Deployment, Done
- d.To Do, In Progress, DoneCorrect
Why? this is the answer
The card emphasizes starting with a simple 'To Do, In Progress, Done' structure to visualize basic workflow and allow for evolution. Options B and C represent overly complex initial setups that impose a rigid process, while option B is too simplistic to effectively visualize flow.
Just read this? Test yourself on what you have been reading.
Read the original → atlassian.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Open roles that interview on agile — each one lists the topics its interview covers.
See open roles