Example dashboard page templates

Hansoft includes example dashboard page templates that you can use as a starting point to create your own dashboards.

To add a dashboard page from an example template, click + to the right of the dashboard page tabs, select New page from template, and select a template. You can modify the charts and item views to meet your needs. See Editing dashboard charts and item views.

Template name Contains charts that can:
Art Help art producers on art asset creation teams understand the current workload, how much work is assigned, any issues, and remaining work.
Kanban Team Help team members understand velocity throughput and ongoing issues if your team uses Kanban as a planning method.
Milestone Track an individual milestone or release and help team members see how much work remains and when all the work tagged for a release may be finished.
Portfolio Help team members understand the full portfolio of projects in Hansoft, giving useful cross-project information to understand progress, challenges, and opportunities across the organization.
Product Owner Help product owners understand the quality and state of their product backlogs.
Quality Assurance Help testers and QA leads understand the current state of the bug backlog in Hansoft.
Sprint Summary Help Scrum Masters see a summary of sprints they are working in together with the teams.

This page template contains a set of charts primarily used by teams involved with art asset creation. It is designed to help an art producer understand the current workload, how much work is assigned, any issues, and remaining work.

Charts

Charts and item views included Shows: Chart type or item view Filters used Columns selected (item view only) Dimensions used Measures used Changes to make see your data
Current workload How much work remaining and duration each assignee has. Useful to understand the current balance of work within the team. Bar <none> <not applicable> Assigned to column Work remaining, Duration columns Click the Assigned to dimension and select people on your team.

Remove either the Work Remaining (Agile) or Duration (Gantt schedule) measure depending on how you plan. If you keep Duration, you may want to filter out Completed items.
Assigned vs. not assigned How much work remains to be assigned. Useful if you have too many assets to create and you need to find someone to assign the remaining work to. Pie <none> <not applicable> <none> Assigned (Number of items), Not assigned (Number of items) Use a project filter or report filter for a sub project to only see parts of the plan you care about.
Blockers All items that are blocked. Useful to help prioritize where to spend your time today to resolve impediments. Item view Blocked Assigned to <none> <none> Modify the report filter to only include the project/sub projects you manage.
Remaining tasks per user group How many items are assigned to each user group (for example, character artists, animators, etc.). It filters out Completed items to give you a view into the future balance of work. Bar <none> <not applicable> User groups, Status column Number of items Click the User groups dimension and select only groups you manage.

If your team uses Kanban as a planning method, this page template provides a set of charts that give you a common starting set of metrics to understand velocity throughput and ongoing issues.

Charts

Charts and item views included Shows: Chart type or item view Filters used Columns selected (item view only) Dimensions used Measures used Changes to make see your data
Cumulative Flow Diagram A cumulative flow diagram of how work is progressing. This chart is fundamental to understanding the relationship between lead times and work in progress.

It may take a day or two for snapshot data to be available because this chart uses the Historical data dimension.
 Area <none> <not applicable> Historical data, Status column Number of items Use a report filter to only include items in your Kanban.
Work by board lane How many items are in each lane on the Kanban boards in Hansoft. Useful to understand how much work in progress you have if you use multiple lanes. Bar <none> <not applicable> Board Lane column Number of items Click the Board Lane dimension and select the lanes you use.
Blocked All items that are blocked. Useful to help prioritize where to spend your time today to resolve impediments. Item view Blocked Assigned to <none> <none> Modify the report filter to only include the project/sub projects you manage.
Throughput (Completed per week) How many items are completed over time. Useful to see throughput over time. Bar <none> <not applicable> Historical data, Status column Number of items Use a filter to only include the projects/sprints where you team manages its Kanban.
Work by board column How many items are in each column on the Kanban boards in Hansoft. Useful to understand how much work in progress you have in each column. Bar <none> <not applicable> Board Column column Number of items Click the Board Column dimension and select the columns you use.
Items by assignee and board column How much work each individual has across Kanban board columns. Useful to understand who is highly specialized in work in one area versus dividing work across different steps. Bar <none> <not applicable> Assigned to, Board Column columns Number of items Click the Assigned to dimension and select people on your team.

This page template contains a set of charts to track an individual milestone or release. It can help you understand how much work remains and when all the work tagged for a release may be finished.

Charts

Charts and item views included Shows: Chart type or item vi ew Filters used Dimensions used Measures used Changes to make see your data
Status (Estimated days) Estimated days for each status. Bar <none> Status column Estimated days column Filter based on the milestone you want to track (for example, use the Releases/milestones dimension).

Change the Estimated days measure to another measure if you are using Points, for example.
Release burndown A release burndown. Useful to help estimate when a milestone may be finished. Bar <none> Historical data Release burndowns column Click the No release burndown selected measure and select the milestone to track.

This page template contains a set of charts to help you understand the full portfolio of projects in Hansoft. It is designed to give you useful cross-project information to understand progress, challenges, and opportunities across the organization.

Charts

Charts and item views included Shows: Chart type or item view Filters used Dimensions used Measures used Changes to make see your data
Project size by status How large all projects are and their current status. Useful to see where the action currently is in the organization. Bar <none> Projects, Status column Number of items <none>
Milestone status Status for all milestones across all projects. Useful to get the big picture of milestone status. Bar <none> Releases/milestones, Status column Number of items Filter out any milestones that are not relevant at the portfolio level.
Workload by user group Work remaining across the user groups across all projects. Useful to see how much is planned for each group of users. Bar <none> User groups Work remaining column Filter out any user groups that are not relevant at the portfolio level.

Change the measure from Work remaining if you are not using Agile planning.
Project burndowns (points) Burndown of points for projects over time in points.

It may take a day or two for snapshot data to be available because this chart uses the Historical data dimension.		 Area <none> Historical data. Projects Points Not done column <none>
Project burndowns (estimated days) Burndown of points for projects over time in estimated days.

It may take a day or two for snapshot data to be available because this chart uses the Historical data dimension.		 Area <none> Historical data, Projects Estimated days Not done column <none>
Work in progress over time Number of items in progress over time. Useful to understand the amount of multi-tasking across the organization. Bar <none> Historical data, Status column Number of items <none>

This page template contains a set of charts to help product owners understand the quality and state of their product backlogs.

Charts

Charts and item views included Shows: Chart type or item view Filters used Columns selected (item view only) Dimensions used Measures used Changes to make see your data
Detailed appropriately and prioritized How many estimated days are in each priority category. Useful to see if there is a balance where the higher priority items are smaller (more granular) and the lower priority are larger (more coarse). Bar <none> <not applicable> Product backlog priority column Estimated days <avg.> (Estimated days column) Change the Estimated days measure to another measure if you use different way to estimate your backlog, such as Points.

 
Estimated vs. not estimated How much of the backlog is estimated versus not estimated. Useful to understand how well the requirements are understood and how much refinement remains. Bar <none> <not applicable> <none> Estimated (Number of items), Not estimated (Number of items) Add a filter to select the project to include.
Backlog size over time How large the backlog is over time across the statuses. Useful to understand velocity and if your backlog is growing too large. Bar Backlog items <not applicable> Historical data, Status column Number of items Modify the report filter to only include backlogs for specific projects you manage.
Work in progress over time The number of items that are in progress over time. Useful to understand the amount of multi-tasking in the backlog. Bar Backlog items <not applicable> Historical data, Status column Number of items Modify the report filter to only include the product backlog items.
Blockers All items that are blocked. Useful to help prioritize where to spend your time today to resolve impediments. Item view Blocked Assigned to <none> <none> Modify the report filter to only include the project/sub projects you manage.
Epics & user stories status Status across user stories and epics. Useful to understand how much work remains in the backlog. Bar <none> <not applicable> Status column Epics (Number of items), User stories (Number of items) Add a filter to include only your product backlog.

This page template contains a set of charts to help testers and QA leads understand the current state of the bug backlog in Hansoft.

Charts

Charts and item views included Shows: Chart type or item view Filters used Dimensions used Measures used Changes to make see your data
Open bugs missing priority A traffic light that indicates how many bugs are missing a priority value. Helpful to trigger triage meetings to prioritize bugs. Traffic light Open Bugs Bug priority column Number of items Set the color bounds to numbers that make sense based on your bug database.
Open bugs missing severity A traffic light that indicates how many bugs are missing a severity value. Helpful to remind the QA team to set severity when adding bugs. Traffic light Open Bugs Severity column Number of items Set the color bounds to numbers that make sense based on your bug database.
Open bugs over time How many open bugs are in Hansoft over time. Bar <none> Historical data Open Bugs (Number of items) Change the measure to use your definition of Open Bugs.
Open bugs by person How many bugs are assigned to each person. Bar Open Bugs Assigned to column Number of items Change the measure to use your definition of Open Bugs.
Open bugs by status How many open bugs there are across various workflow statuses. Useful to understand if there are any bottlenecks. Bar Open Bugs Pipelines and workflows Number of items Click the Pipelines and workflows dimension, select Filter, and select the workflow statuses you want to see.

This page template contains a set of charts to help Scrum Masters see a summary of sprints they are working in together with the teams.

Charts

Charts and item views included Shows: Chart type or item view Filters used Columns selected (item view only) Dimensions used Measures used Changes to make see your data
Sprint work by type Work in a sprint by type. Useful to see where the team is spending time (on bugs, backlog items, etc.). Bar <none> <not applicable> Sprints/Iterations Number of items Click the Sprints/iterations dimension, select Filter, and select the sprint you are interested in.
Items not completed in sprint All items in the sprint that have not been completed. Useful to see what remains or where the commitment was not met. Item view Items not completed in sprint <none> <not applicable> <not applicable> Modify the report filter to only include items in the sprint you are interested in.
Items completed in sprint All items in the sprint that are completed. Useful to understand your successes. Item view Items not completed in sprint <none> <not applicable> <not applicable> Modify the report filter to only include items in the sprint you are interested in.
Bugs in sprints All bugs in the sprint. Useful to see what bugs are being fixed in the sprint. Item view Bugs in sprints <none> <not applicable> <not applicable> Modify the report filter to only include items in the sprint you are interested in.
Sprint burndown A sprint burndown to help you understand velocity and progress. Line <none> <not applicable> Historical data Sprint burndown Click the (No sprint burndown selected) measure and select a sprint.
Blockers All items that are blocked. Useful to help prioritize where to spend your time today to resolve impediments. Item view Blocked Assigned to <not applicable> <not applicable> Modify the report filter to only include the project/sub projects you manage.
Sprint allocations Sprint allocation bars (same as in the Planning view) to help you understand who may need help to complete their tasks. Bar <none> <not applicable> <none> Sprint allocations, Sprint capacity Click the measures and select the sprint to include the allocations for.