Board
The board is where a project’s to-dos live, written down one per card. Each card is called a ticket.
Think of sticky notes on a whiteboard: you move a note to the right when you start on it, and further right when it’s finished. The board is that, on screen.
Why use a board
Section titled “Why use a board”When your to-dos are scattered across your head, chat threads and notepads, this tends to happen:
- You can’t tell whether something you asked for is in progress or forgotten
- You can’t count how many things you’re carrying right now
- You spend time going around asking “how’s that going?”
Put them on a board and everything is in one place, and each ticket’s column tells you how far along it is. Instead of asking around, you open the board.
The board is also how you hand work to a minion. Write on a ticket what needs doing and what “done” looks like, and the minion reads it, does the work, and puts the ticket in the column for things waiting to be checked. You ask the same way you’d ask a person.
What belongs on the board
Section titled “What belongs on the board”Make a ticket for work that takes a few days or more, or work you’re handing to a person or a minion.
| Example | Where it goes |
|---|---|
| Add a new menu item to the website | The board. It has several steps, and you want to confirm it’s done |
| Write a blog post | The board. A minion can draft it |
| Summarize last week’s sales every Monday | A workflow or routine. The same steps repeat |
| A meeting tomorrow at 3pm | The calendar. It’s an appointment with a fixed time |
| A five-minute errand | No ticket needed |
The five columns
Section titled “The five columns”Tickets move from left to right.
Backlog → Todo → Doing → Review → Done| Column | Put a ticket here when |
|---|---|
| Backlog | It’s an idea or something for someday. You haven’t decided to do it yet |
| Todo | You’ve decided to do it, soon |
| Doing | Someone has started on it |
| Review | The work is finished and waiting for someone to check it |
| Done | It’s been checked and is finished |
Three things people tend to get stuck on:
- When something comes to mind, write it in Backlog first. Once it’s written down you won’t forget it. You can decide later whether to do it, and leaving tickets in Backlog does no harm
- Only put things in Todo once you’ve decided to do them. If everything goes into Todo, you can’t tell where to start. Within Todo, work from the top down
- Review and Done are separate because “I finished it” and “this is what I wanted” are different. The person who did the work may think it’s finished, but the person who asked may want changes. Whoever did the work moves the ticket to Review, and whoever asked checks it and moves it to Done. A minion that picks up work from the board also stops at Review. If you work alone and don’t need a check, it’s fine to skip Review and go straight to Done
Getting started
Section titled “Getting started”As an example, let’s split “Announce the autumn campaign” into three tickets and put them on the board.
1. Turn the board on
Section titled “1. Turn the board on”The board is switched on per project. Open the project’s Settings tab and turn on Board under Features. A Board ↗ tab appears on the project, and you can also open it from Board in the sidebar.
If several projects use a board, switch between them from the project name at the top left of the board.
2. Write down what needs doing
Section titled “2. Write down what needs doing”On the Kanban view, click the + in the Backlog column header, type a title, and press Enter. The input stays open for the next title, so keep writing as things come to mind. A ticket lands in the column whose + you clicked.
- Write the campaign announcement
- Post it in the news section of the website
- Email our regular customers about it
Tickets you create are assigned to you.
3. Fill in a ticket
Section titled “3. Fill in a ticket”Click a card to open its details. To begin with, this is enough:
- Description — why it’s being done, useful references, anything to watch out for
- Acceptance Criteria — what has to be true for it to be finished. One per line; press Enter to add
- Due date — only if there’s a real deadline
- Assignee — change it if someone else is doing the work
There are tips on writing these in Writing tickets.
4. Move it right as you go
Section titled “4. Move it right as you go”Drag cards to move them. Move a ticket to Todo when you’ve decided to do it, to Doing when you start, to Review when the work is finished, and to Done once it’s been checked.
Changing Status in the details does the same thing.
5. Group related work under a parent
Section titled “5. Group related work under a parent”All three tickets are part of “the autumn campaign”. In that case, create one ticket called “Autumn campaign”, then open each of the three and choose it as their Parent (epic). The parent gets an EPIC badge and a progress bar, so you can see at a glance how many of the three are Done.
Asking a minion
Section titled “Asking a minion”A ticket’s assignee can be a minion as well as a person. You can hand a ticket over in chat, or leave it on the board for a minion to pick up when it’s free. See Handing tickets to minions for how.
What to read next
Section titled “What to read next”- Writing tickets — how to write a ticket people understand, and how to keep the board up to date
- Handing tickets to minions — the two ways to ask, and what to check when nothing happens
- Board reference — the details of views, filters, custom fields and sprints