Skip to content
JiraVision

Scaling Delivery

Illustrative scenario · StartupX — 8 people becoming 40

StartupX scales from one board to five without a platform team

A scenario for a small org that has one shared board and is about to need five: how to split it, what to standardise, and which automation replaces the coordination one founder used to do from memory.

Team
8 today, 40 within three quarters
Cadence
One-week sprints, one board, everyone on it
Existing tooling
Spreadsheets and a chat channel

StartupX is a fictitious team. This is not a customer story and contains no result figures or attributed quotes. What it does contain is real: every route below exists in the product, and every measure states where its number is computed.

Where it starts

  • One board holds marketing, engineering and support work in the same columns.
  • Status is communicated in chat and is stale within an hour.
  • Nobody owns cross-team dependencies, so they surface at the deadline.
  • Onboarding a new hire takes a founder two days of shadowing.

What to turn on, in order

Order matters — each step assumes the one before it is already in place.

  1. 1

    Start from a template, not a blank board

    The board templates open directly in the product with columns, task fields and views already set. Copy one per team rather than inventing five variants of the same thing.

  2. 2

    Standardise the task fields once

    Custom fields are defined at workspace level, so a 'customer tier' field means the same thing on all five boards and reports can group by it.

  3. 3

    Split the backlog from the sprint

    Grooming happens in the backlog; the sprint is what the team committed to. Keeping them separate is what makes the committed-versus-completed number mean anything.

  4. 4

    Replace chat-status with automation

    Rules fire on real events — task moved, comment added, sprint started — and post to the team's channel and to the notification feed. The rule list shows what each rule did last.

  5. 5

    Make cross-team dependencies visible

    Goals sit above sprints and roll progress up from the tasks linked to them, which is where a dependency between two teams stops being tribal knowledge.

  6. 6

    Write the onboarding path down

    The quick start is the same document a new hire follows, and it only references routes that exist. Pair it with the activity feed so a newcomer can see how work actually moves here.

What to watch

No target values. Each row says where the number is computed and what feeds it, so you can decide what good looks like on your own data.

Measures and where each one is computed
MeasureWhere the number comes from
Cycle time per boardComputed from task status-change timestamps on /dashboard/analytics — the page shows the window it aggregates over.
Sprint commitment accuracyPoints committed at sprint start versus completed at sprint end, on /dashboard/sprints.
Cross-team goal progressRolled up from the tasks linked to each goal on /dashboard/goals; the roll-up rule is shown on the goal.
Time to first task for a new hireObserved by the team, not measured by the product. Stated here so it is not mistaken for a computed figure.

Walk this scenario on your own workspace

Every route above is live. The fit quiz will tell you which of these scenarios is closest to your team before you start.