Queries or views are suitable for the general evaluation of your project results. You can use Earned Value Analysis, Cumulative Flow Diagram or dashboards to evaluate activities.
A query displays your project data in tabular form and always shows the current project status. They are based on query types and can be adapted at any time. For example, requirements are displayed flat in a list or via a detailed query with the corresponding test cases or refinements. You can use queries if you want to edit individual elements, create dependencies or filter according to self-defined criteria. You can configure commands for queries, which you can then use directly in the query to create additional content. Queries can be generated in documents or exported as MS Excel documents.
Hierarchical queries (Version 5.2 and higher)
These queries are suitable for displaying dependencies and relationships between the individual project elements. This makes it possible to see at a glance from which goals requirements have been derived and which test cases check these requirements. You can also use the queries to map a package hierarchy or parts of it.
Views display project data in the form of backlogs, dashboards, or tables. They can also be used to edit individual elements or create dependencies. Unlike queries, views cannot be generated in documents or exported as MS Excel documents.
For communication with management, decision-relevant information and current key figures are required at various planning levels – for example, for an entire project or a single release. To be able to draw conclusions about the status and progress of the work, we recommend that you compile the desired information and key figures in dashboards. The dashboards then show you at a glance, but from different perspectives, how your project is doing.
Cumulative flow diagram
In addition to the dashboard, the cumulative flow diagram is another view that gives you a quick overview of the editing status of your requirements.
Earned Value Analysis
Earned value analysis is a project controlling method in which the performance of a project or an individual activity is determined on the basis of project key figures. Plan costs, actual costs and earned value are used as key figures.
The precedence diagram is a graphical representation of your project activities, represented abstractly by nodes. You can use the network to see which time reserves you have and to what extent the project will be delayed if dependent activities take longer than expected.
With the help of the Kanban board you can see and organize all requirements that are assigned in a sprint, release or team. The kanban board is divided into columns that represent the states that the requests go through until they are completed.