Where could Sigrid help me in my role?

Sigrid is aimed at organizational roles that deal with concerns around system health, code quality and their business consequences. Depending on your role you can answer different types of questions. The different roles we distinguish are described here. Specific uses are described in the portfolio-level overview page and the system-level overview page.

Role: Executive/portfolio manager for portfolio/trend views

High-level overviews of the software landscape’s composition and quality help you take inventory of your landscape’s health, or risk profile. This gives direction to future plans.

To get started with Sigrid, you may want to begin by exploring the dashboard of the portfolio overview. From here, the maintainability details on portfolio level will take you through system maintainability on the landscape level.

To look into the workflows that Sigrid offers you as an executive/portfolio manager, you can read the dedicated workflows section.

Role: Enterprise Architect for both portfolio views and deep dives

Similarly to manager roles, Sigrid helps you as an EA with an overview of the current and desired state of the landscape. From experience, we know that EAs tend to go into technical deep dives to look for (historical) explanations in addition to the portfolio-level pages mentioned above.

Note that metrics can be compared to objectives. By translating business goals to system metric objectives, you have objective metrics to measure against. To start an analysis of system-level metrics, start at the system-level overview.

To look into the workflows that Sigrid offers you as an Enterprise Architect, you can read the dedicated workflows section.

Role: Product Owner for system development progress and planning

To gauge development progress and expected remaining demands, you are interested in indications of how predictable code development is. When progress and trend lines are your main interest, go to the maintainability detail page and code evolution known as “delta quality”.

To look into the workflows that Sigrid offers you as a PO, you can read the dedicated workflows section.

Role: Developer for direct feedback on how to improve your code

Wherever Sigrid highlights code quality hotspots, you want to drill down into the details to understand where and why issues occur. The typical scenario is to focus on code that scores low in maintainability. Typically that code is recognized by developers as tough to modify. Sigrid’s detailed metrics can show what kinds of complexity lie beneath.

The metric details of interest mostly follow from the system maintainability page. These include architecture/component dependencies, a prioritized list of refactoring candidates and a code-tree view in the Code Explorer or alternatively, the technical monitor.

To look into the workflows that Sigrid offers you as a developer, you can read the dedicated workflows section.