Kanban Boards

Kanban Best Practices

Seven Kanban habits and the DevStride feature that supports each one.

Practices and where DevStride helps

PracticeIn DevStride
Visualize the whole flow. Every stage work passes through should be a column, named the way the team talks.Define the statuses in Item Statuses and group them into the team's collection. Rename a status at any time; boards update.
Limit work in progress. Set a limit per stage, start generous, tighten as the team learns its real capacity.Set the WIP Limit per status in the collection. The column turns red when exceeded; nothing is blocked, so emergencies still fit.
Pull, don't push. Rank the backlog once; the team takes from the top.Rank in Table view (drag under the default sort, or Sort & Rank → Rank). Rank is shared by everyone; Sort is personal.
Make policies explicit. What does "ready for review" mean?Put it in the status name or a saved View; use Blocked Reason on items that cannot move.
Manage dependencies early.Record them on the card (Manage Relationships) and watch the External Dependencies row in 2D view for other teams' work.
Keep the board current.Status changes anywhere in DevStride move the card. Clear Done with the Item Stays Done on Board automation.
Review the flow together.Open the board in standup; Board Totals and column subtotals replace the status report. Use the Cycle Carry-Forward report if the team also runs cycles.

Setting limits that stick

Start with a limit equal to the number of people who normally work a stage, plus one. Run two weeks. If the column is red every day, the limit is aspirational — raise it or add capacity; if it never goes red, lower it until it occasionally does. The limit is doing its job when it is red about once a week and the team can say why.

Related: Setting up your Kanban board, Boards and WIP limiters.