Agile boards
Scrum and Kanban desks for development teams, with backlog, board, mandatory QA, definition of done, sprints, releases and metrics.
An agile board is a development team's workspace. It holds its items (stories, bugs, tasks, subtasks and epics), the board where they move forward, the QA review, the definition of done, the releases and the team's metrics. Tickets from a service desk can reach an agile board when someone Escalate a ticket to development.
Scrum or Kanban
Each agile board starts with one of two templates, and it can't be changed later.
Scrum | Kanban | |
|---|---|---|
Pace | Work in sprints of 1 to 4 weeks | Continuous flow, no sprints |
Where new items go | To the Backlog, and from there they are planned into a sprint | Straight to To do on the board |
Views in the menu | Backlog, Board, Sprints, Versions and Metrics | Board, Versions and Metrics |
What the board shows | The active sprint | All the items in progress |
Work-in-progress limits | Optional | Set to 3 for In progress, In review and QA |
Metrics | Velocity, lead time, cycle time, throughput and cumulative flow | Lead time, cycle time, throughput and cumulative flow |
To open a desk, go to Desks in the side menu and choose the desk. Its views appear below its name and, if you are its lead, Settings.
An item's flow
Agile boards start with these statuses, which the lead can rename, add or remove (see Board statuses and columns):
Backlog (Scrum only) → To do → In progress → In review → QA → Done → Released
Backlog: what's pending, prioritized. It doesn't appear as a column on the board.
To do, In progress and In review: the work of the sprint or the flow.
QA: someone with the QA role reviews the item against its Acceptance criteria and QA. If they reject it, the item goes back to In progress.
Done: it can only be reached from QA, with QA approved and the Definition of done complete.
Released: the item went to production in a Releases.
With the built-in configuration, only a person with the QA or Lead role can move an item from QA to Done. An item with open subtasks can't move to Done either.
Roles in an agile board
Your desk role decides what you can do in it. The lead assigns it in Settings → Members (see Desk members and roles).
Role | What it can do |
|---|---|
Lead | Everything a member can do and also create, start and close sprints, create and release versions, give QA verdicts and change the desk's settings |
Member | Create items, move them on the board, estimate them, prioritize the backlog, block them, edit acceptance criteria and check the definition of done |
QA | Everything a member can do and also give the QA verdict (approve or reject) |
Viewer | See the desk, the board, the sprints, the releases and the metrics, without changing anything |
If a desk is public you can open it even if you aren't a member, but only to read. To write in it you must be a Lead, Member or QA.