Nasdanika Templates
    AI Roadmap

Roadmap Site

This is a template repository for roadmap web sites generated from Drawio diagrams with GitHub Actions and Nasdanika CLI Drawio Command.

It is created from the Drawio site template - see that template for the general information about Draw.io sites. The below documentation focuses on the roadmapping aspect.

The AI roadmap diagram is based on the roadmap slide from the AI Leadership Track: Gen AI, Agentic AI for Business Leaders Udemy course.

To get started go to the Template GitHub page and click “Use this template” in the top right.

Overview

This site has the following “implied” domain model: Roadmap (table) consists of Phases (columns) and Actors/Stakeholders (rows) with Deliverables in cells. All elements can have tooltips, documentation and status tags. Visibility of elements can be toggled by the clicking on the status nodes in the legend.

The diagram is not mapped to a semantic model and, therefore: * There is no cross-referencing * There are extra nodes in the navigation tree because the tree structure follows the containment structure of the diagram

This is a simple approach which allows:

  • Manage roadmap as code - version control, collaboration
  • Document roadmap elements
  • Build a hierarchy - deliverables can have their own roadmaps if needed
  • Toggle element visibility to focus on specific deliverable statues, e.g. “Off Track” or “Blocked”

Semantic mapping is the next step, which brings more structure and power. The roadmap model is work in progress and a link to it will be added to this site once it is ready.

Adding phases or stakeholders

  • Use the table “Arrange” tab to add a new row or column
  • Select an existing cell. In the Style tab click on the edit drop-down and select “Edit Style…”. Select style text and copy it to the clipboard.
  • Select new cells - all or one by one. In the Style tab click on the edit drop-down and select “Edit Style…”. Select the existing style text and press “Ctrl-V” to paste the copied style of the existing cell from the clipboard. Altenatively, add ;fontColor=none;noLabel=1;childLayout=stackLayout;horizontalStack=0;stackSpacing=5;stackBorder=5; to the end of the existing style string.
  • For new cells set the label to the phase name - copy/paste from the header cells.

Changing status

  • Change color
  • Open tags view and change the status tag

Integrations

You can use representation elements filtering to update status based on information in external sources.

Jira

If you are using Jira you can implement status update as explained in this section.

  • Add properties to deliverables:
    • jira-issues - a comma separated list of issues or a YAML list or map. By default the representation filter may pull the issue, its children and epic children. If using the YAML map this behavior can be customized. JQL for retrieving issue descendants recursively and epic children: issueFunction in childrenOf("<JQL subquery>") OR issueFunction in linkedIssuesOfRecursive("key = <issue key>", "is Epic of").
    • jql - JQL query
    • jira-filter - named filter.
    • jira-project - list of projects.
    • jira-board - jira board.
  • Read the above properties and pull information from Jira using Nasdanika Jira Client
  • Compute aggregated status:
    • Planned if all are planned
    • In progress if any issue is in progress and there are no blocked or off-track issues
    • Completed if all are done
    • Off Track - for every issue compute from target dates and issue status. The aggregated status is Off Track if there are no blocked issues and there is at least one issue off track
    • Blocked - if there is at least one blocked issue

Resources