waltz
waltz copied to clipboard
finos
Documentation: improve landing page screenshots
Description
Attach screenshots - make sure all internal data is masked!
Resourcing
We intend to implement this task
Report Grids provide end-users with the ability to define a custom, tabular report. Grids are centered around a subject entity type, currently either:
- APPLICATION
- CHANGE_INITIATIVE
From that subject entity type users can define additional data to include and Waltz will generate the appropriate access code to retrieve that data and display it in the grid. As can be seen above, the grids understand when values are backed by specific schemes allowing additional coloring and formatting to be applied.
A wide variety of data items are supported in the grid, including:
- Basic attributes on the subject (lifecycle phase, planned retirement, ...)
- Assessment values
- Taxonomy ratings
- Involvements (people)
- Costs
- Complexity measures
- Statistic outcomes
- Survey Statuses
- Survey Answers
- Group membership
- Aliases and Tags
- Owning Organisational Unit details
Grids can be exported to xslx, csv and json. We are currently experimenting with an approach to allow the data to be exported in an OData format, for consumption by systems like Tableau.
The source of the subjects depends upon the users current vantage point. This allows the grid to be used against a custom subset of the portfolio or against all subjects.
Grids also support filtering and can even be linked to App Groups, providing a periodic snapshot of all subjects which satisfy the filter conditions. This feature is used to create automatically refreshing lists of items, for example all apps which are high criticality, in production and have not yet completed a survey.
These two views show the upstream and downstream flows in and out of a system. The flows are broken down by data type and colored according to the Flow Classification Rules (aka Authority Statements).
The first view provides a 'complete picture' - but can get very large and complex. The second view is designed to be a simpler representation where users are encouraged to explore the diagram to get more detail.
Bank on a Page
This view is the Bank on a Page diagram. It is being actively developed and allows administrators to create a diagram based on a taxonomy (in this example we are using a capability model).
Each part of the diagram links to a taxonomy item. The linkage of diagram parts to model elements allows Waltz to determine which application (or change initiatives) are aligned to each diagram element.
We are building out a collection of interactive overlays which can then be used to provide details about those applications. The example above shows the number of applications incorporating future commissions and decommissions.
The Statistics view in Waltz allows for basic stats to be recorded against applications. Each value is also given an outcome which allows the results to be 'bucketed' for use in the pie chart and line chart. The stats are used for a variety of purposes including:
- Data Quality metrics (apps without flows etc)
- OSS Vulnerability counts (incl. licence vulnerability)
- DORA stats to chart development efficiency
We are combining the DORA stats with an agile tribe taxonomy to give users the ability to see DORA stats across agile teams.
@davidwatkins73 , this is great, would you be able to add some additional explanation for each screenshots. Regards Russell.
@RussellChumbley - done, take a look and let me know if things aren't clear