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.
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.
Import Templates
Orientation for new admins: build an entire branch of workstreams and items from an Excel template — the fastest way to bring an existing plan or a large body of work into DevStride.
Admin Onboarding - Organizing the When: Understanding Planning Cadences
Step 10a of admin onboarding — cadences, timeboxes, and cycles explained with one example, why nested cadences matter for scaled planning, and how to decide which cadences your teams need.