How do Tempo Budgets and Tempo Planner integrate to each other

In this short tutorial we explain the resource management capabilities for both Tempo products (Tempo Budgets and Tempo Planner) and explain which use cases they solve. The article’s purpose is to clarify the boundaries of each product, where they work together and where their limitations are. It also focuses on common pitfalls and scenarios that are not supported.

1. Adding staff members in Tempo Budgets has only one purpose: to forecast project/Folio costs and to determine which staff costs to track in the Folio.

   Open

   

   That means:
   -> If a staff member is not allocated to a Folio, the worklogs of an employee/Jira user against a Jira issue that is within the scope of a Folio and within the time period of the Folio is not recognized as a financial cost in the Folio. That can be done by purpose. It is not an automated process so you will always need to check if any worklogs by employees are entered that do not belong to a Folio. It is not an automated process, which gives the Folio owner a better control of what cost should be realised and what shouldn‘t.
   -> The allocated staff members are used within Tempo Budgets to calculate/forecast the costs of the Folio based on the resource allocation. This cost scenario model is part of the forecast scenario called “Forecast based on known future costs”. You can read more about the forecasting model here.
   -> Allocated staff members are not reflected in Tempo Planner in any way.
   -> The staff members load progress bar shows the time against those issues where the staff member is assigned to. E.g. Team member A is assigned to Issue A and B that are within the scope of the Folio with a total of 100h remaining. Team mamber A has a total availability of 200h. The progress bar will display a 50% (100h/200h) allocation.

2. The “Planning” tab inside the staff section is supposed to be “read-only”. It is showing plans from Tempo Planner and is nothing more than an indicator what other obligations the staff members have from other initiatives (Jira issues or Jira projects).

   Open

   

   The planning view is not intended to do any planning on issues that are within the scope of Tempo Budgets. All resource planning needs to be done in Tempo Planner.

3. When you plan your costs within Tempo Budgets you have the option to import the allocated/planned hours from the Folio’s staff into Tempo Budgets.

   This is a one-time-action reflecting the plans of the resources at the time when this action is performed. Any future amendments and added plans in Tempo Planner are not reflected. However, any future added plans will be reflected if one creates a new baseline following the same steps as before, which is easy. One can create as many baselines as they need within the Folio.

4. Do your resource planning for your Folios in Tempo Planner. Behind each single Folio there is a Jira JQL filter. You can use this filter to plan on the resources allocated to your Folio. If you have not created a JQL filter as the basis for your Folio, Tempo Budgets will create one for you. All filters start with “Scope of …” and are by default private and limited to the user that has created the Folio. You can update the filter share settings for others to use too.

   You can add the filter into the issues panel of the resource planning overview. Filter the resources to your team/s and plan the issues accordingly. This will ensure other plans from other initiatives are recognised and brought to your attention.

5. Back in Tempo Budgets you will see the plans made in Tempo Planner. You can also easily view other allocations from other staff members with the time period and the total amount of time.

    

Related articles