...
Allstacks looks at all commit and card activity in connected tools to determine how each individual is spending their time over the course of each workday. This is done by measuring the time between each action. If Action A is performed at 1pm, and Action B is performed at 2pm, Action B will receive an hour of credit.
...
How is it calculated
...
Allocation is measured in full-time engineers/employees (FTEs). FTE’s is a calculation of the ratio of time spent on a given piece of work in a day multiplied by the average daily salary for engineers at your company. Each action taken on various pieces of work influences the ratio for each day. Our model is most accurate when your team’s work is performed in a tracking system like Git or Jira.
Calculation details
...
Investment hours looks at all the actions a contributor has in each day, and portions out an 8 hour day’s worth of credit across those actions according to how much time there is between each action. In a metric that shows the contributions of multiple team members grouped together, for example by milestone or team or issue type, the relevant hours from each individual will be added together to produce the total for the desired grouping. Allstacks follows links in your source tools, from commits up to their corresponding tickets up to those tickets' corresponding epics and initiatives. This linking allows you to group hours at whatever level you want.
Allocation is calculated the same way as Investment Hours, but adds in the concept of an hourly blended rate, so that instead of showing a number of hours on the y axis, you see a number of dollars. The default rate can be set in the organization settings page. To further refine the calculations, different rates can be set for different contributors using tags. The multiple rates option is hidden by default to ensure salary information is handled wisely, so talk to your customer success representative if you want to explore this option.
Calculation details
The calculations go as follows:
First, for any given day we find all actions a given user has. Actions include any commits or card activity that user has. Note: We skip weekends when considering a users FTE’s. This means that for any given week, a user can have a maximum of 5 FTE days. Then, we loop through the list of actions and run a calculation to find that actions FTE ratio.
...