On a Scrum project the board shows the running sprint — or a sprint that's already completed, so you can look back. Planned sprints and the backlog never appear here. If no sprint is running yet, the board says No active sprint: start one on the Sprints page.

The Product Owner, Scrum Masters, Developers and organisation Owners/Admins move and add cards. Stakeholders see the same board read-only (a Stakeholder can still add work items if an Admin gave them a custom role with Create work items).

Find the work you need

1. Pick a sprint with Select sprint at the top. The running sprint opens first; completed sprints are in the same list.
2. Use Search this board to look for words in a title, or type a number such as 42, #42 or WEB-42 to find that exact item.
3. Turn on the quick filters — Only my items, Recently updated (changed in the last day) and Flagged. You can switch on several at once.
4. Click a person's face to see only their cards, or use Filter by type and Filter by priority. Group by Assignee or Epic splits the board into swimlanes.

Move a card

1. Drag the card to the next column with your mouse, or press and hold it on a phone or tablet.
2. If you'd rather not drag, open the card and change its Status. Stages you can't move it to are greyed out, with the reason beside them.
3. If a column won't take the card, the board says why — a stage entry rule, the workflow, or a WIP limit (see Stage entry rules).

Add work and watch the limits

1. Click Add work item in the toolbar (it starts in the first stage), or the + at the top of a column to add it straight into that stage.
2. Each column header shows how many cards it holds. With a WIP limit set, it reads like 3 / 4; once it's over, the column turns red and says Over the limit of 4 — finish something before starting more.
3. Ordering cards inside a column is for the Product Owner, Scrum Masters and Admins (and Developers, if the project allows it in Project settings › General). Anyone else's card lands at the end of the column.

A Kanban project has no sprints. The board is one continuous flow of all your ongoing work, and the menu has no Sprints or Retro page. The line at the top sums up the whole board, for example "14 in progress · 31 finished in the last 14 days".

Read the board

1. Cards that reached Done more than 14 days ago drop off the board. The Done column says · last 14 days, and Older finished work is in the list opens the backlog to show them.
2. Cards in progress carry an age pill (for example 6d): days since the item first entered an In-progress stage (moving it between in-progress columns doesn't reset it). It turns amber, then red, as the card sits still.
3. Until 10 items have finished, amber starts at 5 days and red at 10. After that, the colours come from your project's own history: amber when half of finished items were already done, red when 85% were.
4. A card in an In-progress stage shows DoD 2 of 4 for its Definition of Done (amber while items are open, green when all are ticked). A Done card shows it only if it entered Done with items still open; To do cards never do. Both board types show this.

Keep work in progress in check

1. Each column header shows its WIP limit in words: 3 of 4, or 3 of 2 · over limit with "Finish something here before starting more." underneath.
2. Use the Ageing quick filter (alongside Only my items, Flagged and Recently updated) to see just the cards that have sat too long.
3. Pull the next card from To do when someone has room, rather than starting several at once.

Switch between Scrum and Kanban

1. Open Project settings › General and look at How this project works. This is for the Product Owner, Scrum Masters and organisation Owners/Admins (or a custom role with Change project settings).
2. Choose the other board type and confirm. Switching to Kanban removes any planned sprints; their work items go back to the backlog.
3. You can't switch while a sprint is running — complete it first. Once a project has more than one completed sprint, its board type is fixed: create a new project of the other type and move the work there.

A stage can have rules for what a work item needs before it enters, and who may move it there. When a move is refused, the card goes back and the app tells you exactly what's missing. This section is about reading those messages and fixing them.

When a move is refused

1. Who may move it: "Only the Product Owner can move items to Review", or "Only the assignee can move items to Done". Ask that person to move it — or, if it says to assign it first, set the assignee.
2. What the item needs: "Before Done: fill in Story points and Due date · 2 sub-tasks are not done · blocked by WEB-41". Fill in the fields, finish the sub-tasks, and get the blocking items to Done.
3. WIP limit: for example Stage "Review" has reached its WIP limit of 3 — or, when you drag on the board, Column has reached its WIP limit. Finish or move something out of that stage first.
4. The workflow: "The workflow doesn't allow this move." That stage can't be reached from where the item is now — move it through the stages in between.

Moving to Done with Definition of Done items open

1. If the item has Definition of Done items that aren't ticked, the app asks Move WEB-42 to Done? and lists them.
2. Choose Open the work item to tick them first (offered when you're not already on that item's page), Cancel to leave it where it is, or Move to Done anyway (the move is recorded with what was open).

Change the rules

1. Entry rules, WIP limits, the Definition of Done and the stages themselves live in Project settings › Workflow.
2. Only the Scrum Masters (the Product Owner while there is no Scrum Master) and organisation Owners/Admins can open it. Everyone else gets the rule's own words when a move is refused, and can ask them to change it.
3. How to set the rules up: Workflows and stage entry rules.

The Sprints page is the sprint list for a Scrum project: the running sprint at the top, then sprints being planned, then completed ones. Every project role can open it; only the people below can change sprints. For your very first sprint, follow Part 3 · Plan & start a sprint.

Follow the running sprint

1. The running sprint's card shows its dates, the time left, its goal, and two bars side by side: how much work is done and Day 3 of 14 — so you can see at a glance whether the work keeps up with the calendar.
2. Open board goes to its board. Retro and Sprint report are on the card (or in its ⋯ menu on a narrow screen).
3. When it's time, Complete sprint is on the same card (see Complete a sprint).

Plan and start the next one

1. Click New sprint, give it a Sprint name, a Sprint goal and, if you like, a Start date. The end date follows from the project's sprint length.
2. On the sprint's row, use ⋯ › Plan in backlog to move work into it.
3. Click Start sprint. Only one sprint runs at a time: while another is running, the button is greyed out and says After … completes.
4. Change a sprint's name or dates with ⋯ › Edit sprint…. Only a sprint that hasn't started can be removed, with ⋯ › Delete sprint….

Look back at completed sprints

1. The Completed table lists each sprint's dates, goal and how much was done.
2. Each row links to that sprint's Board (read-only), its Retro and its Sprint report.

Under each running or planned sprint's goal there's one planning line, on the Sprints page and on the sprint's section in the backlog. It reads like "Capacity 40 pts · committed 46 pts · average velocity 38 (last 3 sprints) · 2 not estimated".

Read the planning line

1. Capacity: the points your people can take on this sprint (only shown once someone has set it).
2. Committed: the story points already in the sprint. Not estimated counts items with no points, so you know the total may be low.
3. Average velocity: what the team actually finished, on average, over the last 3 completed sprints. A new project says "no velocity yet".
4. Warnings appear beside it when you've planned too much: Over capacity by 6 pts, or Above average velocity.

Set each person's capacity

1. Click Capacity on the sprint's line. The dialog lists the project's Product Owner, Scrum Masters and Developers.
2. Type the story points each person can take on. Leave a field empty to not count that person (someone on leave, for example).
3. To start from last time, click Use Sprint 4's numbers — it copies the running sprint's numbers, or the most recent completed sprint's.
4. Click Save. The planning line and its warnings update straight away.

Completing a sprint closes it and decides what happens to anything not yet done. The Complete sprint button is at the top of the board and on the running sprint's card on the Sprints page — for the Product Owner, Scrum Masters, organisation Owners/Admins, and anyone with a custom role that grants Complete sprints.

Complete the sprint

1. Click Complete sprint. The dialog says how many unfinished work items there are (or that every item is done).
2. Under Move unfinished work items to, choose Backlog or a sprint you're already planning.
3. Optionally write Retrospective notes (up to 2,000 characters) — what went well, what could be better.
4. Click Complete sprint. You can complete a sprint early; you don't have to wait for its end date.

What happens afterwards

1. The notes you wrote show as Notes from completing the sprint at the top of that sprint's Retro page and under Reports › Sprint.
2. The sprint is kept as a record: its board becomes read-only and the status of its finished items is frozen.
3. An item can still be moved out of a completed sprint later — with its row's ⋯ › Move to in the backlog, or the item's Sprint field — for example to reopen work that turned out not to be done.
4. Plan and start the next sprint whenever you're ready.

A retrospective is a short look back at a sprint. Pick the sprint at the top (Choose a sprint — running and completed sprints are listed). For a first run-through, see Part 3 · Run a retrospective.

Run the retro

1. The Scrum Master clicks Start retrospective for the chosen sprint.
2. The team adds cards to the four columns: Went well, Improve, Discussion and Kudos.
3. The team votes on what matters most — one vote per person per card. Click your vote again to take it back.
4. Any notes written when the sprint was completed show at the top as Notes from completing the sprint.

Agree on actions

1. Type a New action item, pick an owner and a Due date, and add it.
2. Each action has a status — Open, In progress or Done — and a due pill (for example "Due tomorrow" or "2 days overdue").
3. Click Create work item on an action to turn it into a task in the backlog, so it gets planned like any other work.
4. Actions not yet done appear on later retros under Still open from earlier retros, oldest first, until someone marks them Done.