Admin Onboarding: Getting Started

Boards: Managing Workflow and Statuses

Step 9 of admin onboarding — why boards come after workstreams and statuses, how to set up your first working-group folder and board, and where the full board documentation lives.

Up to now you have defined what the work is (workstreams and items) and how it flows (statuses). Boards are where you add the who and when: a board belongs to a working group, uses one status collection as its columns, and is either perpetual (an ongoing list) or cycle-based (tied to a cadence).

Boards come at this point in the guide because they consume everything you set up earlier. A board needs a status collection to draw its columns, teams to assign cards to, and items to put on it. Set one up now with the items you created in the last step; refine later.

Your first board, in brief

  1. Open Plan Delivery and create a folder named for the working group (for example "Platform Team"), not for the product. Folders can nest to mirror how teams roll up.
  2. In the folder, add a board. Choose the status collection it should use (the default collection is pre-selected) and leave it perpetual for now; you will add cadences in the next step.
  3. Put work on it: open items from Map Value and set their Board, or add existing items from the board itself.
  4. Drag cards between statuses. Your teams will live here day to day.

Everything about boards, including the three views, WIP limiters, folder permissions, and importing items onto a board, is in the Plan Delivery section, starting at How DevStride manages the When and Working Group Folders.

Next: Understanding Planning Cadences, so cycle boards have dates to run on.