DevStride is for organizations that run many projects across several teams and need to know, reliably, when things will land. Everything you configure in this guide serves one idea, so it is worth getting it straight before you open Settings.
Most project tools make you answer two different questions with one list:
Mixing them is what produces boards named after products that nobody works from, and reports that cannot say how far an initiative has got because its work is scattered across six team boards.
DevStride keeps the two apart and links them:
| Question | Structure | Module | Who lives here |
|---|---|---|---|
| What are we delivering? | Workstreams holding a hierarchy of items (Epic → Story → Task) | Map Value | Product owners, sponsors, portfolio leads |
| Who does it, and when? | Folders of boards, perpetual or tied to a cadence | Plan Delivery | Teams, scrum masters, delivery managers |
An item exists once, in a workstream. Putting it on a board does not copy it; it places the same item in a team's queue. A parent Epic in the "Customer Portal" workstream can therefore have its design Stories on the Design board, its API Stories on the Backend board, and its test Stories on the QA board, and the Epic's progress still rolls up correctly because every Story is still its child.

Because teams get their own structure in Plan Delivery, resist creating workstreams called "Frontend Team" or "QA". Name them for what is being built: "Customer Portal", "Q3 Product Launch", "Sales Acceleration". You will assign teams later, on boards.
Two supporting areas you will also touch: Configure Settings, where the data model (item types, statuses, fields, cadences) and people (users, teams, roles) are defined, and Automate Workflows, once the basics are running.

The steps that follow build on each other, so take them in order:
Next: Create your organization.
Creating Your Account
How to sign up for DevStride — with Google or Microsoft, or with an email address and password — and what happens next depending on whether you were invited or are the first one in.
Admin Onboarding - Getting Started
Step 1 of admin onboarding — confirm your organization exists, complete your Organization Profile (name, domain, logo, timezone), choose the Global Automations defaults, and learn your way around Configure Settings.