Support, help and how to use Trainyard.

Your first ten minutes

Trainyard has four spaces in the top bar: OKRs for outcomes and funding, Classes for teaching, Templates for boards in any method, and Plan for the ART from strategy to PI planning. Setup lives in the account menu.

1. Sign in with your email and password (or the API key you got at sign-up).
2. Teaching? Open Classes → Class boards and start a class; hand participants the board link.
3. Running a train? Open Plan → Readiness, WSJF & risks, then the PI planning board.
4. Reporting to executives? Open OKRs → Dashboard, then Sources, measures & funding to load your own data.
5. Connect Jira or Azure DevOps under Setup → Jira & Azure DevOps when you want two-way sync.

Press ? on any page to open the help for that page.

The search box in the top bar finds any ticket, card, canvas or board.

OKR dashboard

The read-only view of every objective and its key results: overall progress, how many are on track, at risk or off track, days left in the quarter, the trend and what needs attention.

1. Pick an entity at the top to see only its objectives and everything beneath it.
2. Read the ring for overall progress: each key result is measured from its first value (the baseline) to its target.
3. Open check-in from Needs attention to say what is true this week.

Nothing here is typed in: it comes from your measures. Change the data or check in, and these numbers move.

Alignment

Key results grouped by the objective they prove.

1. Drag a key result onto another objective to realign it; it stays an outcome or a KPI.
2. Use Note, Pen and Timer in the dock to run an alignment workshop on the same board.
3. Switch to List for a printable view, or Copy as text to paste the result anywhere.

Weekly check-in

The same key results grouped by status. The data proposes a status; your check-in overrides it until the next one.

1. Drag a key result to On track, At risk or Off track.
2. The card shows who checked in last; the dashboard follows at once.

A key result marked “from data” has had no check-in yet.

Sources, measures and funding

Where the evidence comes in: sources (CSV from your CRM, finance, learning platform, surveys, Jira), measures over them, objectives per entity, initiatives with their funding, and the printable one-pager.

1. Sources: upload a CSV with a period column (a date or month). Each source is a table you can measure.
2. Measures: pick a column and how to count it per month (sum, average, count, latest), or divide one measure by another.
3. Objectives: choose which measures are outcomes (the change you want) and which are KPIs (health), with targets.
4. Initiatives & funding: what was committed, by whom, spend to date, and which outcomes show what it bought.
5. One-pager: pick an entity and print or save as PDF for the executive team or the board.

Start empty clears the example data. Two examples are built in: an education programme and Northstar Bank.

Class boards

Leading SAFe, SPC, Advanced SPC, POPM and RTE, each a board with a Start here strip and one frame per lesson.

1. Choose Start this class: a board for this cohort is created and opened.
2. Share the board link with participants.
3. Classes you are running are listed below for next time.

Chapters that teach a Trainyard tool (PI planning, readiness, value streams, Inspect & Adapt) are built from the tool itself, so they stay current.

Breakout groups

Tables of four for the class you pick; a full table refuses a fifth person.

1. Add participants by name, or keep the sample roster.
2. Drag people onto tables, or Seat everyone at random.
3. Add or remove tables with + Table and − Table.

Day plan

The class's lessons laid out over its days; each half-day holds 180 minutes.

1. Drag lessons between sessions; going over 180 minutes warns you.
2. Use −15 and +15 on a lesson to change its length.
3. Reset to the class order puts everything back.

Template gallery

Ready-made boards in each method's own words: SAFe, Scrum, Kanban, Lean, Six Sigma, manufacturing and general.

1. Pick a method: the page takes on that method's look.
2. Pick a template on the left and preview it as lanes or as a whiteboard.
3. Name it and choose Create board from template.

Or start blank from Your boards and add any templates to one board.

Your boards

Every board in the workspace: from templates, blank whiteboards, classes and imports.

1. New blank whiteboard opens an empty board.
2. Open any board and use Add a template to place a template beside what is there.
3. Filter by Classes, Whiteboards and templates, or Imported.

Working on a board

A whiteboard everyone edits: frames, cards, links and connectors.

1. + Card adds a sticky; double-click a card to write; drag to move.
2. Connect draws a dependency between two cards.
3. + Link a record turns a card into a live link to a feature, risk, objective or canvas.
4. Add a template places another board's frames to the right.
5. Save as template keeps the structure for next time; Map onto the plan turns cards into backlog items, risks and dependencies.

Bring your own boards

Pull a board in from Miro, Mural, Trello, monday.com, iObeya or a spreadsheet, exactly as it is.

1. Pick the tool your board lives in.
2. Connect it with an access token (Miro, Mural, Trello, monday.com) and choose a board, or upload an export (Miro CSV, iObeya export, any CSV).
3. Open the imported board, save it as a template or map it onto the plan.

Tokens are stored encrypted and used only to read your boards.

Portfolio

Value streams with their budgets, epics in the Portfolio Kanban ranked by WSJF, guardrails, and portfolio OKRs.

1. Move epics through funnel, reviewing, analyzing, backlog, implementing, done.
2. Score WSJF on each epic to rank the backlog.
3. Envision the future state from the Canvases page to turn strategy into epics.

Value streams

Identify value streams in five steps, then measure one as a value stream map.

1. Choose a type (fulfilment, manufacturing, software product, supporting): its example loads as a starting point.
2. 1 · Operational value stream: the steps from trigger to value; click any chevron to rename it.
3. 2 · Solutions: the systems each step runs on. 3 · People: who builds and supports them, where.
4. 4 · Development value streams: group the solutions and people. 5 · ART design: cut trains of 50 to 125.
5. Full breakdown shows all five levels at once; click a box to trace it. Measure it opens the map.

What the facilitator would flag lists the gaps still open.

Readiness, WSJF and risks

Everything that has to be true before PI planning: readiness checks, the ART backlog ranked by WSJF, risks with ROAM, and the launch canvases.

1. Pick the PI at the top.
2. Score each feature's user/business value, time criticality, risk reduction and job size; WSJF and the rank update as you go.
3. Raise known risks and give each a ROAM status.
4. Open the launch canvases: ART launch timeline and readiness checklist, LACE mission, value stream and ART canvases.

Score one column at a time across all features, smallest first: relative values beat absolute ones.

Canvases

SAFe's working artifacts kept as data, in roadmap order: strategy and epics, launching the train, readying the backlog.

1. Choose New on a canvas type, or prefill a development value stream or ART canvas from an identification.
2. Click any section to write in it; set the date and current or future state in the header.

PI planning board

Milestones on top, features by team and iteration with dependency strings, and risks to ROAM below; changes sync back to Jira or Azure DevOps.

1. Drag a feature to another iteration or team to replan it.
2. Click a team's name to set its capacity: typed in, from members, or from velocity.
3. Red strings show dependencies; dashed ones arrive too late.
4. Add milestones and events with + in the top row.

Readiness, WSJF and risks live on their own page before the event.

Coach Sync

The Scrum of Scrums during PI planning: six checkpoints over two days, four questions each, answered per team.

1. At each checkpoint, mark each team Yes, Partly, Not yet or Needs help.
2. Add a note per team; Needs help flags the checkpoint for the RTE.

PI Outcome Planning

AI-Native SAFe's one-day planning: the outcome tree, the PI Outcome Planning Board, team boards, the management review and the vote.

1. Build the outcome tree from objectives to key results.
2. Drag work and milestones on the board; string cards that depend on each other.
3. Tick a team's card to show it on the ART board; finish with the confidence vote.

Delivery dashboards

Flow, predictability and planning metrics by team, increment and work level, with a narrative.

1. Pick a dashboard and filters; every widget explains how it is calculated.
2. Use the assistant to draft the readout (when AI is configured).

Operating model

The framework your workspace speaks: levels, roles, events, cadence. SAFe, LeSS, Scrum@Scale, Nexus, Flight Levels and more, or your own fork.

1. Pick a model, or fork one and rename its levels and events.
2. Boards and dashboards follow the model's vocabulary.

Jira and Azure DevOps

Two-way sync of features, stories, risks and dependencies.

1. Add a connection with the site URL and a token.
2. Map projects or area paths to teams and choose the work item types.
3. Changes made in Trainyard queue for review before they are pushed.

Card types

The card types boards use, with SAFe's colour legend and any types you add.

1. Add a type with its fields and colour.
2. Admins can recolour the built-in types.

AI portfolio

AI initiatives through discover, specify, build, validate and release, with spend and value.

1. Add initiatives and move them through the stages.
2. Link features to an initiative to see what delivers it.

AI agents

Agents working on your teams, with an accountable human and an autonomy level each.

1. Register an agent, its team and the person accountable for it.
2. Set how far it may act without review.

Users and passwords

Who can sign in, with which role, and their passwords and API keys.

1. Add a user with a role: admin, planner, architect or viewer.
2. Set or reset a password; everyone can change their own.
3. Rotate an API key when someone leaves.

Plan and billing

Your plan, seats, trial and invoices.

1. Upgrade or add seats; changes are charged pro rata.
2. Switch to yearly after the first paid month.
3. Claim the money-back guarantee here within your first paid month.