Sylvics Apply for the beta
One-roadmap boardTool
TOOL

One-roadmap board

๐Ÿ› ๏ธ One-roadmap board

๐Ÿ’ก Use Case

  • The single board that replaced the Exceptions backlog and the Tracking backlog when ๐Ÿ“‚ Merge the Exceptions and Tracking roadmaps finished. The roadmap was published on 8 August; the board went up the Monday after.
  • It is ๐Ÿ“œ One roadmap for the merged team, not two made visible: one list, one order, and no lanes named after the old teams.
  • Four columns: Next, Now (five cards at most), Waiting on someone else, Done this quarter.
  • Read from the top. If two people disagree about the order, the board is wrong and we fix the board.
Who may move what
  • Anyone may move a card to the right.
  • Only Lucรญa Ortega and I change the order of Next, together, on Mondays.
  • A card enters Now only when one leaves.
  • Nothing is added during a planning meeting. It goes on a list and is argued for on Monday.

โš–๏ธ Pros & Cons

Pros

  • The limit of five in Now did more for the merged team than any workshop.
  • Waiting on someone else has its own column, so a blocked card is visible and not quietly old.
  • Nobody can tell from a card which half of the team it came from. That was the point.

Cons

  • One order means somebody's important thing is ninth. For the first month that somebody was always from Tracking.
  • The rules are written down, which makes them easy to quote at me.
  • It shows order, not size. A two-day card and a two-month card look the same.

๐Ÿ”„ Alternatives

  • Two lanes, one per former team, as Greta Holm first proposed. Tidier, and it would have kept two teams alive inside one.
  • A ranked document. We had one from May to August and nobody opened it twice.