Engineering Investment
Metrics showing effort allocation and financial investment, including development costs, hosting, and incidents. Customizable by requirement.
Insights into where your effort is going
Connect your engineering systems to TargetBoard to enable the metrics shown below for your organization. To fully enable CAPEX and other financial data or estimates, additional data will be required. Reach out to your Customer Success Manager to discuss in detail.
Note that the metrics list provided below is demonstrative only, and that custom metrics, calculations and data points are created based on individual customer requirements.
Financial Investment
Capitalization FTEs | Summary of Full Time Equivalent effort in months of salary for all dev-items closed during the reporting period, both capitalized and not capitalized (filterable). |
Capitalization Cost | Total development cost for all dev-items closed during the reporting period, based on employee salary and FTE effort. |
Development Cost | Total development cost, based on employee salary and FTE effort, for all dev-items completed up to the end of the report period. Useful for understanding the overall investment in a project, initiative, or epic. |
Hosting Cost | Total monthly hosting cost of AWS resources for billing cycles taking place during the reporting period. |
Post Mortem - Avg Incident Cost | Average financial cost of incidents detected during the reporting period. |
Post Mortem - Total Incident Cost | Total financial cost of incidents detected during the reporting period. |
Effort Investment
Use the metrics below and break them down based on your priorities and organization structure (eg: by Label, Team, Initiative etc.) to see where you're investing your resources. Using stacked or grouped bars can be particularly helpful to breakdown data across two dimensions simultaneously and answer questions like 'How much of each team's time is spent resolving bugs?'
# New Story Points | Aggregation of all story points attached to new dev-items created during the reporting period. |
# New Dev-items | Count of how many new dev-items were created during the selected date range. |
# Closed Story Points | Aggregation of story points attached to all dev-items which were placed in the Done status category during the reporting period (this includes statuses such as Cancelled and Won't Do). |
# Closed Dev-items | Count of all dev-items which were placed in the Done status category during the reporting period (this includes statuses such as Cancelled and Won't Do). |
# Done Dev-items | Count of all dev-items which were completed successfully during the reporting period (this generally excludes statuses such as Cancelled and Won't Do and is defined during onboarding). |
# New Bugs | Count of new bugs created during the reporting period. |
# Closed Bugs | Count of all bugs closed under any status during the reporting period. |
Cycle Time | Average time from a dev-item entering an in development status for the first time until that item is closed. Can also be configured to calculate based on median or percentiles. |
Pull Request Cycle Time | Average time taken from first commit in a branch until the final merge of the pull request. |
Dev-items Time in Status | Shows the average amount of time for dev-items to spend in each workflow status between creation and closure. Highlights bottleneck and common delays. |
How did we do?
Human Resources
Technical & Customer Support
