Kanban task tracking: build your first board

Start with four columns

Use To do for work that is ready to start, In progress for active work, In review for a result awaiting checks, and Done for accepted outcomes. Avoid a new column for every small step. Use Waiting for information when needed; a task blocked on a customer response should not silently inflate the amount of active development work.

Define when a card can move

Before an issue moves into In progress, it should have an owner and an expected outcome. In review needs a testable result; Done needs an acceptance check. For a report bug, “the code was written” and “the output was verified against sample data” mean different things. A short description template helps the team preserve that distinction.

Limit work in progress

Two people starting six tasks does not mean six tasks will finish quickly. Agree on a working limit for the In progress column. Taskending does not currently enforce an automatic work-in-progress limit, so apply it as a team rule and check the board. Helping finish a task awaiting review can be more valuable than starting another item.

Record blockers with a next action

A note that says “waiting” is not enough. Record what you need, who can provide it and when to check again. Use a Blocks link for dependencies between issues. If information is missing from a customer, separate the technical internal note from the public question. This prevents the same unresolved uncertainty from consuming every meeting.

Combine the board with sprints

A board describes the state of work; a sprint describes a goal within a time window. You do not have to abandon one to use the other. Run incoming support requests on a board and planned product work in team sprints. Taskending’s compact board shows four main states, with additional states available in the expanded view.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free