Skip to content

Roadmapping & change

The EA problem

A repository describes the present. Planning is about the future — and the gap between them. Leadership wants to know what's changing, when, and how the planned changes connect to the systems and capabilities they care about. Initiatives that live only in slide decks and project trackers are invisible to architecture, so their architectural consequences are discovered too late.

How ArcaMira addresses it

Initiatives as first-class entities. An initiative records scope — what it delivers, retires, and enables — plus owner, dates, and budget. Because it's an entity in the same graph, its relationships connect planned change directly to the capabilities and applications it touches.

Roadmap (/roadmap): the initiatives timeline — a single view of what's in flight and what's coming, by when.

Change shows up where the work is. On an application or capability page, in-flight initiatives appear in context ("3 initiatives touching this app"), so anyone looking at an asset sees what's about to change it.

From plan to consequence. Roadmapping pairs naturally with impact analysis: an initiative tells you intent; impact analysis tells you the blast radius of acting on it, including replacement candidates and capability gaps that would open up. To test a set of changes before committing to them, the Scenarios engine (/scenarios, alongside Roadmap and Impact Analysis under Planning) lets you compose a change set — retire / introduce / reconnect — evaluate its second-order effects against the live graph in a safe dry-run, then optionally commit.

What good looks like

  • Significant initiatives recorded as entities, linked to what they deliver/retire/enable.
  • A roadmap leadership can read without a translation layer.
  • Each major initiative's architectural footprint visible from the assets it touches.
  • Retirement initiatives cross-checked against impact analysis before they're committed.

A note on integrations

For teams that run delivery in Jira, a curated (filtered, not full) sync of architecture-relevant epics into initiatives is a planned tier feature — designed for orgs with consistent epic hygiene, not a firehose import. Not built today.