Describing a planning tool is thankless work. "Capacity-based scheduling across multiple teams with dependencies" either sounds obvious or sounds like buzzword bingo, depending on how many PI Plannings you have survived in a spreadsheet. So from today, ROADagile is something you can open instead of read about.
In short: A public live demo is running at demo.app.roadagile.de. No login, no installation, no email address. It opens straight into a fully planned PI roadmap built from sample data.
What's in the demo
The demo doesn't start on an empty screen — it drops you into the middle of a planned program increment. The sample data comes from a typical automotive scenario: a connected mobility platform, driver assistance, over-the-air updates. Three teams, twelve features, stories with estimates, and real cross-team dependencies.
That's enough to try everything that separates the tool from a spreadsheet:
How big is this program, really?
Story points per team, epic sizes, averages, and a health check: unplanned stories, dependencies, orphaned items. The sanity check you would otherwise assemble from three pivot tables.
Epic → Feature → Story
The SAFe® structure the way Jira meant it — not a flat ticket list, but a tree where you can expand a feature and see the stories underneath it.
The roadmap that follows from your assumptions
Stories are distributed across sprints and teams by capacity, with dependencies drawn in. Features can be dragged onto fixed dates or teams to pin them — everything else is replanned around them automatically.
The setup screen is where it gets interesting: sprint length, PI start, capacity buffer and per-team velocity are all editable in the demo too. Halve one team's velocity, go back to the roadmap, and you see immediately what it does to the PI. That "what happens if…" loop is the reason the tool exists.
The demo runs entirely in your browser too
This isn't a stripped-down variant that computes on a server. Hierarchy building, scheduling and Gantt rendering all run inside your browser tab exactly as they do in the application — once loaded, it even works offline. How that works technically, and how to verify it yourself in DevTools, is covered in "What 'no data leaves your browser' actually means".
What the demo doesn't show
To be straight about it: the demo is a slice, not a product promise.
- The path from a Jira export to a roadmap. Automatic column detection, status filtering and the export back to Jira are exactly the part the demo skips — it starts you off in the finished plan.
- No saved sessions. A reload puts the demo back to its starting state.
- Sample data of a fixed size. Three teams and 145 story points is a realistic but small program. Larger backlogs behave differently on screen.
And the most important point: ROADagile is not generally available yet. The demo shows the current state of the application, not a subscription you could buy today.
The best way to use it
If you have two minutes: open the Gantt view, drag a feature onto a different sprint, and watch what happens to the features that depend on it.
If you have ten: change a team's velocity in the setup screen, adjust the capacity buffer, and look at the roadmap again. Then open the hierarchy view and check whether the feature breakdown resembles the epics you actually work with.
If your reaction is "ours would look different" — good. That's the useful feedback, and the reason the demo is public before the product is.
Open the demo – and be there at launch
The live demo is open to everyone, no sign-up required. If you want to plan with your own Jira data, join the mailing list and you'll be the first to know when ROADagile opens up to teams.
Open the live demo