Over the next few days I will write a number of posts on AppTracker's reporting ability. This will cover Testing reports, Processes & Time reports, Blueprints reports and other handy reports all built into AppTracker.
AppTracker contains very powerful and detailed set of reports that can be used to manage a software migration project from start to finish. Our reports can be run on all applications or any subset of applications allowing you to analyse and filter the application portfolio by Blueprint, process, vendor, packager etc, or any combination of these options!
There are three types of reports in AppTracker; Test Reports, Metric Reports and Inventory Reports.
Provide the ability to manage the testing and quality of the deliverables within the project. This is especially useful when trying to manage the process interfaces between teams such as the discovery team and an outsourced packaging company. By managing the quality throughout the workflow it is possible to substantially reduce costs and improve productivity.
Allow a project manager to see how a project is progressing over time. By providing weekly or bi weekly snapshots of the workflow its possible to see if a project or process is stalling and whether team members need to be refocused to concentrate on difficult areas.
Provide the ability to extract information from the extensive application knowledge base. This knowledge base can be dynamically defined and extended by the administrator as requirements come into the project. It then becomes possible to ask questions such as "show me all the applications used by Marketing", "Show me all the applications that connect to ServerX", "Show me all applications that failed quality step Y"
All of the reports can be printed directly to a printer or exported to Excel, word CSV and other standard formats for further manipulation.
The AppTracker Dashboard is the first screen that everyone will see when the open AppTracker. It shows three charts. Users can configure this view for the processes or package types they are most interested in.
- A snapshot of the current processes and the number of applications in each.
- A pie chart of the breakdown of application types that are in the system, e.g. msi, app-v, citrix.
- A progress history of applications moving through the various processes since the beginning of the project.