Dashboards and Graphical Reports
Dashboards
Dashboards help to aggregate information from various sources and show it in a single place. In Targetprocess you can create as many dashboards as you want: for a single team, for QA, for development tracking, etc. Let's review some cases:
Team Dashboard
Shows everything that is important for a single team. New entities assigned to a team, latest comments by team members, burn down chart for the current iteration, cycle time trend for bugs and user stories, and latest closed bugs.
QA Dashboard
Focuses on bugs. How many bugs were closed each week? What new bugs have been added recently? Are there any open blocking bugs? What bugs took too much time to fix?
Support Dashboard
Aggregates information about Help Desk / Product Support / IT Support activities. Do we resolve issues faster? Do we have changes in the incoming requests' trend? What new requests were added recently?
Custom Graphical Reports
Reports should be used to see aggregated data and progress over time. So far you can create line charts, bar charts and scatterplots. Facets are supported as well, so you can group information by various categories and compare projects, teams, features, see trends in cycle time, quality and many other areas. Here are some real usage cases:
Cycle Time trends
Here we see average cycle time trends for two projects. For the QA Area project cycle time is increasing, and this is not a good trend. For the TP3 project it is almost flat.
Feature Portfolio
Every circle represents a single feature. Color shows Kano model categories, Y axis defines sales forecast and X axis – implementation duration. So we can see what features are better to start next.
Problematic User Stories
See what user stories have more bugs.
User Story Effort and Cycle Time by Teams
This report is quite complex but very informative. It shows user stories (circles) for every team for the last four months. Each small chart shows Effort vs. Cycle Time correlation. You see what teams create larger user stories, what team completes stories faster, and what team has less consistent estimates.
We are eager to hear feedback about these features and are going to improve them in the next couple of months based on your real needs.