Boards: Scrum, Kanban & Delivery pipeline
The three board types in BoardMark — Scrum, Kanban and Delivery pipeline: statuses, workflow, WIP limits, environments, dragging cards and concurrent edits.
How do the board types differ?
| Board | Sprints | Best for |
|---|---|---|
| Scrum | Yes | Teams working in iterations, with story points, a burndown and a backlog planning page |
| Kanban | No | Continuous work such as operations or support; starts in a Backlog column, optional WIP limits |
| Delivery pipeline | No | Teams that need to know which environment every issue is on; Testing and Passed columns per environment |
How does the Kanban Backlog column work?
Kanban projects have a Backlog status as the first column, before To Do. New issues start in Backlog and are dragged to To Do when the team is ready. The Backlog lane can be collapsed. Kanban projects created before this existed get a one-time Add Backlog column button for project admins.
WIP limits per status are set in project.md; columns over their limit are highlighted.
How does a Delivery pipeline work?
When creating the project, list 1–10 environments in delivery order. The board gets Backlog · To Do · Test Rejected · Developing · Dev Done, then Testing and Passed for each environment, then Done. Each environment's columns sit under one header band.
- An issue that fails testing on any environment moves to Test Rejected and goes back to development
- Project admins add, rename or reorder environments later in Project settings
- An environment can be removed only when none of its columns hold issues — the blocking issues are listed
- Delivery pipelines have no sprints
---
key: REL
name: Releases
board_type: pipeline
environments: # 1–10, in delivery order
- { id: develop, name: develop }
- { id: uat, name: UAT }
- { id: prod, name: production }
statuses: # generated from the environments
- { id: backlog, name: "Backlog", category: todo }
- { id: todo, name: "To Do", category: todo }
- { id: test_rejected, name: "Test Rejected", category: in_progress }
- { id: developing, name: "Developing", category: in_progress }
- { id: dev_done, name: "Dev Done", category: in_progress }
- { id: testing_develop, name: "Testing (develop)", category: in_progress }
- { id: passed_develop, name: "Passed (develop)", category: in_progress }
- { id: testing_uat, name: "Testing (UAT)", category: in_progress }
- { id: passed_uat, name: "Passed (UAT)", category: in_progress }
- { id: testing_prod, name: "Testing (production)", category: in_progress }
- { id: passed_prod, name: "Passed (production)", category: in_progress }
- { id: done, name: "Done", category: done }
---Where do statuses and workflow come from?
From each project's project.md. Every status has a category (todo, in_progress, done), and transitions are either any-to-any or an explicit list. New projects get To Do, In Progress, In Review, Test Rejected and Done.
---
key: APP
name: Mobile App
board_type: scrum
statuses:
- { id: todo, name: "To Do", category: todo }
- { id: in_progress, name: "In Progress", category: in_progress }
- { id: in_review, name: "In Review", category: in_progress }
- { id: test_rejected, name: "Test Rejected", category: in_progress }
- { id: done, name: "Done", category: done }
transitions: any # any | explicit list
parallel_sprints: false # Scrum only; off by default
---How do I move cards?
- Drag a card to another column to change its status, or up and down to reorder
- Drag an issue from the backlog strip straight into a column — it joins the running sprint with that status
- On phones, long-press then drag, or change the status in the issue drawer
- From the keyboard: ⇧← / ⇧→ moves between columns, ⇧↑ / ⇧↓ reorders
Everyone viewing the board sees the change in real time.
What happens when two people edit the same issue?
Every save sends the version it read. If someone saved first, nothing is overwritten: you see the difference and choose Keep mine, Take theirs or Merge — even when the changes do not overlap.