Requires the following solutions to be installed:
- Working Days (7fe5edc0-360f-4fca-9eec-05d754a89fe8)
- Team Rate (9c1a0d08-1456-45d3-bae2-c0895e373cc6)
- Team Actual, Average and Forecasted Velocity (7b7bfbb1-fef5-4109-a149-6400883ac9e4)
---------------------------------------------------------------------------------------------------------------------------------
Solution overview
The solution enables the calculation of Cost per Point for a Team. Cost per Point is calculated as Team Cost per period divided to a completed effort (or Team Velocity) during the same period. This metric allows to forecast the cost of new Features, Epics and Portfolio Epics when estimations are done, and team cost is available.
After the solution installation, you'll see a new tab Cost per Point on a Team view. Here you'll see a list of Cost per Point records (respective to each Team Iteration) with Actual and Forecasted Cost per Point.
- Actual Cost per Point will be calculated as a Team Cost / Team Actual Velocity (both values for the period of a Team Iteration)
- Forecasted Cost per Point will be calculated as Team Cost / Team Forecasted Velocity
Team Cost is calculated as Team Iteration Working Days * DailyHours * Team Hourly Rate
Forecasted Cost per Point is used to estimate the Forecasted Cost of work items (Features, Epics or any other), while Actual Cost per Point can be used to track the current Cost per Point during a Team Iteration.
Solution Installation
Set Budgeting Portfolio ID in Automation Rules
To make Cost per Point information available to a limited group of people, we need to hide them in a separate Portfolio (Project) called Budgeting (or use any other name which suits your organization). All the Cost per Point records will be kept in this project by default. By assigning people to this project, you will provide access to the Cost per Point details. People who don't have access to the Budgeting Portfolio (Project) won't see anything on the Cost per Point tab on a Team view. To do that:
- Copy a "Budgeting" portfolio ID (if not created yet)
- Go to Settings -> Automation Rules
- Replace the Project ID parameter in the following rule:
- Cost Per Point creation - main rule
- Save the rules
Update the solution parameters (optional)
There are several additional parameters which can be updated in the solution:
- "RateCF": "Hourly Rate" - the name of a custom field, which contains information about a Team Hourly Rate. If it differs in your account, please update it in the rules.
- "DailyHours": 8 - if your standard number of Hours per Day differs from 8, please update it with the correct number
To do that:
- Go to Settings -> Automation Rules
- Open the following rules one by one:
- Cost Per Point creation - main rule
- Cost Per Point update - main rule
- Update the parameters
- Save the rules
Calculate Working Days for Team Iterations
If you had Team Iterations in system at the moment when you install the solution, and you would like to calculate Cost per Point for them, we need to calculate Working Days for those Team Iterations. To do that:
- Go to Settings -> Automation Rules
- Open the following rule:
- Initial - Calculate working days for existing entities
- Make sure it use Team Iteration and Start/End Dates as parameters
- Click Save and Trigger button
Create and calculate Cost per Point for existing Team Iterations
When the solution is installed, you may already have existing Team Iterations in the system. To create respective Cost per Point records for these Team Iterations, please do the following:
- Go to Settings -> Automation Rules
- Enable and open the following rule:
- Trigger Cost Per Point creation for existing Team Iterations
- Click Save and Trigger button
Cost per Point records will be generated for all the existing Team Iterations and Teams.
Note 1: Going further, when a new Team Iteration will be created, then a respective Cost Per Point will also be created for this Team Iteration automatically with the same Planned Start/End Dates and inherit Team Iteration Actual and Forecasted Velocity.
Note 2: If you don't have a Team Rate available for the dates of a Team Iteration, then Cost per Point won't be calculated, so to calculate it for the past Team Iterations, adjust Planned Start Dates for Team Rates.
---------------------------
Version 2.0
Still have a question?
We're here to help! Just contact our friendly support team