Report views

Future state visualisation

To visualize what possible changes your transformations will affect in the future, go to reports containing a timeline. These are the Landscape, Matrix, and Portfolio. (Soon also in the roadmap)

Select those projects that have the transformations you want to observe. (You don't need to select every project of the hierarchy just select the parent - if you know you want to see the full impact of the project.)

600

To see what changed between two points in time, use shift + click to compare. If you only want to see what changed, use the option in the report settings (see video).

When you select one or more projects, a timeline appears. It contains all of the project milestones and begins with the earliest date (among all projects) and ends with the most recent date. If no date is found, then the fallback is one year.

:arrow-forward: For Projects, the start date is defined in the lifecycle with the phase: Active and the end date with the phase: End of life.
:arrow-forward: For Transformation Items the start date is defined in the lifecycle with the phase: In implementation and the end date with the phase: Finished or Rejected.

Roadmap Reports

Dependency lines shown in the roadmap indicate the relations that exist between the projects, such as "Required by/Requires" and "Blocked by/Blocks"

Roadmaps are an essential tool in planning business transformations as they provide a visualization of the time aspects of your projects and initiatives - such as, when does a project start and what are the important milestones.

Roadmap Reports - Visualizing changes over time

Roadmaps are an essential tool in planning business transformations as they provide a visualization of the time aspects of your projects and initiatives - such as when a project start and what are the critical milestones.

The roadmap, in combination with BTM, provides a way to visualize the impacts that are planned using transformations over time. Whereas other reports allow you to jump only to certain points of time in the future to visualize the to-be state, the roadmap adds the time dimension to it.

With that, you can see how certain aspects of your landscape change over time due to the selection of one or more Projects (or Transformation Items).

Use case

Q: What phase is the drilldown Fact Sheet's lifecycle in when the relation is active?

A: Relation data is visualized in combination with the drilldown FactSheet's lifecycle. It is now possible to display - not only activeFrom/activeUntil relation data - on a lifecycle, but all relation activity changes, which are caused by planned transformations.

By default, relation activity data on drilldown lifecycles are now displayed as follows:

  • Inactive parts of the drilldown’s lifecycle are cut off.
  • Parts of the drilldown’s lifecycle that exceed the parent lifecycle are cut off as well.
  • On drilldown Fact Sheets without defined lifecycle phases a “n/a” lifecycle will be displayed. All above mentioned options will apply to this “placeholder” lifecycle as well.

How to use it

Presets

On top of the roadmap, there is a project selector button. Here you can choose the set of projects for which you want to see the impacts on your items in the roadmap.

📘

Information

As of Q4 2022 the visualization of changes over time in the roadmap only works for changes on relations, which will be visualized when using drilldowns.

Drilldown settings

Enable users to achieve a cleaner view when it comes to showing drill-downs:

  1. Restrict to parent: If enabled, the bars in the drill-down are restricted to the time range of the parent lifecycle and do not clutter the roadmap beyond that.

  1. Display inactive time range: The drill-down bar can have inactive time ranges in relation to its parent (e.g., when “Active from” or “Active until” are set on the relation). If this setting is enabled, those inactive parts are displayed as a hatched bar. If this setting is disabled, the inactive parts are not shown at all, which further cleans up the roadmap view.

Additional settings

In the settings modal, you can only see Fact Sheets that are actually affected by the projects you have selected with the project selector.

Step 1: Open the settings modal

Step 2: Enable the setting as shown below

Sidepane

If you click on a Fact Sheet in the report, the side pane will open with an additional section that displays all the projects that affect that Fact Sheet

Visualizing dependencies

In LeanIX you are able to model dependencies between Projects (or Transformation Items) that will be displayed on the roadmap reports.

There are two types of dependencies that can be used:

  1. Requires / Required By
  2. Blocks / Blocked By

Requires/RequiredBy

The required dependency is used to express that in order to finish one project, it requires another project to be finished as well. Both projects can run in parallel, but the required project has to finish before the project that requires it.

Visualization in the roadmap

  • The dependency is displayed via an end-to-end line
  • If the dependency is met, the line will be grey. If the dependency is not met, the line will be red.

Use Cases

To finish a project that introduces a new application, the application has to be configured. The configuration happens in another project. So the required relation can be used to define that the application introduction project requires the configuration project to be finished before it.

Blocks / Blocked By

The Blocks dependency is used to express that in order to start one project, it requires another project to be finished. The projects cannot run or start in parallel, but the blocking project has to finish before the project that is blocked can be started.

Visualization in the roadmap

  • The dependency is displayed via a start-to-end line.
  • If the dependency is met, the line will be grey. If the dependency is not met, the line will be red.

Use Cases

To start a project that introduces a new application, the application has to be purchased first. The purchasing happens in another project and needs to be done in order to start the introduction (configuration, training, etc).