There are two methods of counting contributor activity
Velocity-based method
Records completed work.
Work is evaluated based on:
Issue count
Story point estimates
Credit is attributed to the assigned contributors.
Investment Hours Method
Tracks the time spent as tickets are actively worked on.
Monitors contributor activity in issue tracking tools or commit actions in code tools.
e.g. Jira and Github
Credits a developer's contributions even if they are not assigned to the issue.
Overview of the presentation of data
A simple, public example of an Investment Hours R&D Capitalization report
A simple, public example of an Velocity R&D Capitalization report
Data granularity
Each row represents a contributors activity on a given issue in a given month
In its simplest form a row contains the following data
Basic velocity example row
Contributor | Issue ID | Issue Name | Issue State | Capitalizable? | Month | Story Points |
Xander | ALL-4 | Update firmware | Done | Yes | February | 3 |
Basic investment hours example row
Contributor | Issue ID | Issue Name | Issue State | Capitalizable? | Month | Hours Invested |
Xander | ALL-4 | Update firmware | Done | Yes | February | 16.1 |
Describing parent container to facilitate roll up
Issues often belong to parent containers which may in term belong to another parent.
e.g. Initiatives contain Epics which contain Issues
Including these parents allows for easier roll up of data
Velocity with parent issues
Contributor | Initiative ID | Initiative Name | Epic ID | Epic Name | Epic Capitalizable | Issue ID | Issue Name | Issue State | Month | Story Points |
Xander | INIT-3 | Support Delivery Drivers | ALL-1 | Driver Tracking | Yes | ALL-4 | Update firmware | Done | January | 3 |
Investment hours with parent issues
Contributor | Initiative ID | Initiative Name | Epic ID | Epic Name | Epic Capitalizable | Issue ID | Issue Name | Issue State | Month | Hours Invested |
Xander | INIT-3 | Support Delivery Drivers | ALL-1 | Driver Tracking | Yes | ALL-4 | Update firmware | Done | February | 16.1 |
Identifying capitalizable work
Users can indicate work is capitalizable at any level
e.g. If an issue has a capitalizable custom field value of “Yes”
e.g. If an issue is contained in an epic with a capitalizable custom field value of “Yes”
Users can use a complex capitalization trigger
e.g. If an issue is contained in an epic with a capitalizable custom field value of “Yes” and that issue is not of the “Spike” type.
Describing contributors to facilitate roll up
Contributor tags can be included in your report to allow you to group data by team, role or any other characteristic that is
Velocity with parent issues and contributor tagging
Contributor Role Tag | Contributor | Initiative ID | Initiative Name | Epic ID | Epic Name | Epic Capitalizable | Issue ID | Issue Name | Issue State | Month | Story Points |
Rascals | Xander | INIT-3 | Support Delivery Drivers | ALL-1 | Driver Tracking | Yes | ALL-4 | Update firmware | Done | January | 3 |
Investment hours with parent issues and contributor tagging
Contributor Role Tag | Contributor | Initiative ID | Initiative Name | Epic ID | Epic Name | Epic Capitalizable | Issue ID | Issue Name | Issue State | Month | Hours Invested |
Rascals | Xander | INIT-3 | Support Delivery Drivers | ALL-1 | Driver Tracking | Yes | ALL-4 | Update firmware | Done | February | 16.1 |
Measuring effort using velocity
There are three methods of attributing velocity to assignees:
Full credit to current assignee
Full credit to all assignee
Split credit among all assignees
Calculating time using investment hours
User Interface (Development in Flight; Delivery February 2025)
.png?version=1&modificationDate=1734553720589&cacheVersion=1&api=v2&width=960&height=720)
Select the Method you want to use to generate your capitalization report.
Define the characteristics of capitalizable work.
Select the columns of information that you want included in the report.
Select the timeframe you want to report.
Review and Redownload past reports.