Kanban Board Software for Teams: A Practical Setup Guide

Kanban board software pays off when a team gets three things right: columns that mirror how work really flows, a cap on how many items can sit in each stage at once, and a short daily review in front of the board. In Hamahang, P-Soft’s project and ticketing platform, the kanban board and Gantt chart come with the Pro plan, and every card on the board is a full task with an owner, reminders and attachments.

This is a hands-on guide, not a theory lesson. If you want to compare kanban with Scrum or waterfall first, read our overview of project management methodologies. Here we focus on what a real team should do on day one, week one and month one.

What does a kanban board actually fix?

Work rarely disappears because people are lazy. It disappears because nobody can see it. One person juggles five half-finished items, another is blocked waiting on a colleague who has no idea, and the manager only notices when a deadline has passed. A board makes that visible: each piece of work is a card, and the column it sits in tells everyone its state.

Sticky notes on an office wall work fine for a small co-located team. The moment part of the team works remotely, travels, or needs files and discussion to live beside each item, a digital board becomes the practical choice.

Step 1: Design columns from your real workflow

The most common mistake is starting with the default To Do, Doing, Done and never changing it. Those three columns hide exactly the places where work stalls. Instead, take the last item your team delivered and trace it from request to hand-over. Every point where it changed hands or waited becomes a column.

Hypothetical example for a four-person marketing content team:

Pay most attention to the Blocked column. When cards pile up there, the team’s problem is not speed; it is dependency on people outside the team.

Step 2: Set work-in-progress limits

Limiting work in progress (WIP) is the core of the kanban method. Agree a number for each active column, and while a column is at its limit, nobody pulls a new card into it. Treat this as a team agreement and write the limit in the column name or on the board description so it stays visible.

• For Drafting, start with the head count: one active item per person.
• Keep Review small so finished work does not queue for days.
• When a column is full, help a colleague unblock a stuck card instead of starting something new.
• Revisit the limits after two or three weeks. Your own data, not a textbook, sets the right number.

Step 3: Write cards people can act on

In Hamahang, a card on the board is a task, so it carries everything a task does: a single owner, a due date with reminders, and attached files. These task features are in every plan. A card with a two-word title is unclear even to its author a day later. A simple template helps:

1. Start the title with a verb: “Rewrite pricing FAQ”, not “FAQ”.
2. State in the description what “done” means for this card.
3. Give it one owner; others can follow it.
4. Attach briefs, images and examples to the card itself, not to a chat thread.
5. If the card is blocked, name the person or decision it is waiting for.

Step 4: Run the daily stand-up at the board

A kanban stand-up is different from a round-the-table status meeting. Rather than each person reciting what they did yesterday, the team walks the board from the column closest to done back towards the backlog. The guiding question is “What is stopping this card from moving?” Keep it to fifteen minutes.

• Review first: who will look at these today?
• Blocked next: which ones need chasing today, and by whom?
• Then in-progress items: which has been sitting longer than usual?
• Finally, if there is spare capacity, pull the next card from the backlog.

Distributed teams can run the same walk-through on a shared screen. The Pro plan also includes internal calls and meetings, so the stand-up does not need a separate conferencing tool.

Which Hamahang plan includes the kanban board?

Hamahang comes in three plans, each containing everything in the one below. Knowing the split helps set the right expectations for board-based work:

A small team that only needs task lists can live on Start. For daily kanban practice, Pro is where you begin.

Feeding tickets into the board

For many teams, half the work arrives from outside: customer emails, website forms, requests from other departments. Hamahang turns an incoming email or web form into a ticket (see email to ticket), and a task created from that ticket lands in the backlog column. The team lead then has one place to prioritise, and outside requests no longer hide in an individual inbox.

Kanban board or Gantt chart?

A board answers “where is the work right now?”. A Gantt chart answers “when will it finish, and what does it depend on?”. Teams with continuous, repeating work, such as support, content or software maintenance, live mostly on the board. Projects with phases and contractual deadlines also need a timeline. Both sit side by side on the Pro plan; our Gantt chart scheduling guide covers the timeline side.

Scaling kanban across departments

When several teams share one system, two needs appear. People should see only their own department’s work, which organisational access levels on the Elite plan handle. Some items also need to pass a defined approval route before delivery, which Elite’s custom workflows let you configure. For an example of a multi-discipline setup, see how an engineering consultancy structures its projects.

Common kanban mistakes to avoid

• Only the manager updates the board. The person doing the work should move the card.
• Old cards are never closed, so the board becomes noise nobody trusts.
• Everything is flagged urgent, which means nothing is.
• Discussion happens in a separate chat group, and the card never learns what was decided. The Pro messenger keeps conversations attached to tasks.

Getting started

You can use Hamahang in a browser or through its Android app, either as a hosted cloud service or on hardware inside your own office. If your current tasks live in spreadsheets or another tool, P-Soft can bring them over, with scope agreed per plan and contract. Our advice for the trial period: put one team on the board, run it for two weeks, then decide.

Frequently Asked Questions

Which Hamahang plan has a kanban board?

The Pro and Elite plans. Start includes task management, and the kanban board and Gantt chart are added from Pro.

How do we choose a WIP limit?

Start with one active item per person in your main working column, then adjust after two or three weeks based on where cards stall.

Can customer emails appear on the board?

Yes. Emails and web forms become tickets, and tasks created from tickets go onto the board.

Does Hamahang work on mobile?

Yes, there is an Android app alongside the web version.

Can we test the board before buying?

Yes. Hamahang offers a trial period so your team can try the board on real work.

Ready to set up a board for your team? Book a walkthrough from our Hamahang overview and start a trial on your own tasks.

Further reading

• What Is a Ticketing System and Why Do Companies Need One?
• The Best Project Management and Enterprise Ticketing Software in Iran: A Buyer’s Guide (2026)
• Enterprise Messenger vs. Ticketing System: Key Differences

Complete guide: project management and ticketing software