Proposed Budget based on Work Allocations | Targetprocess - Enterprise Agility Solution

Proposed Budget based on Work Allocations

Requires one of the following solutions to be installed: Work Allocation Forecasted Hours and Cost based on User Rates (c28a99dc-352b-4587-9d6d-d7142c6dd1f2) (if you use User Rates) Work Allocation Forecasted Hours and Cost based on Team Rates (4e4e5065-4ed5-4b94-a709-b0627dad922a) (if you use Team Rates)

Trusted by Agile teams at show more

Requires one of the following solutions to be installed:

  • Work Allocation Forecasted Hours and Cost based on User Rates (c28a99dc-352b-4587-9d6d-d7142c6dd1f2) (if you use User Rates)
  • Work Allocation Forecasted Hours and Cost based on Team Rates (4e4e5065-4ed5-4b94-a709-b0627dad922a) (if you use Team Rates)

Requires the following solution, if you'd like to have Work Allocations connected to Products:

  • Work Allocations connection to Product (5663621f-3fed-4723-8466-2a1b04750a7c)

Requires the following solutions to be installed:

  • Budgeting: Structure (7f7b1fec-480b-4011-9b4c-262cbc20303a)
  • Budgeting: Automation Rules (a04a5dce-362f-499e-b168-1bf4621b53de)
  • Budgeting: Metrics (877ad475-d0bc-4509-af72-11b5a6934895)

Requires at least one of the following solutions to be installed:

  • Budgeting: Connection to Portfolio Epic (Project) (bda287bd-b86b-40cc-9a2d-4da2026bbf43)
  • Budgeting: Connection to Value Streams (c7baca53-831f-47a3-af4a-3f6965d21b58)
  • Budgeting: Connection to Solution Trains (d0b9ef51-c3b3-40ec-a668-75ae8274e8b5)
  • Budgeting: Connection to Agile Release Trains (ARTs) (3bd5f3c7-ce05-44c8-8b2d-02863522e5c1)
  • Budgeting: Connection to Teams (29090431-bb10-4f5a-b472-99db69200d93)
  • Budgeting: Connection to Product (4f6b967a-0e8d-4a3c-a12c-35d16f45be53)

Requires at least one of the following solutions to be installed:

  • Budgeting: Portfolio Epic (Project) Funding Views (448b04d0-59ed-4e7b-9fc5-11a5796d020d)
  • Budgeting: Product Funding Views (01fa67a3-faaa-477b-b057-8135cab12443)
  • Budgeting: Value Stream Funding Views (0c7bed70-45bd-4d7e-a72e-4bd100e08f0e)
  • Budgeting: Solution Train Funding Views (7284f89d-34f2-4016-a85c-c9c02e790d3e)
  • Budgeting: Agile Release Train (ART) Funding Views (741b1f77-0471-46b1-a39f-353337e3afc4)

Can't be used together with the following solution:

  • Proposed Budget based on Headcount (22c6f9f4-9d5e-49d3-b9cc-c3bc025d245b)
  • Budgeting: Proposed Budget Manual Entry (85007fc5-c6ca-40d6-8420-6eb5a10fc052)

The following diagram represents a visualization of these requirements:

Note: The solution only works if you use Month Period for planning Work Allocations. It doesn't support Week, Quarter or Year periods.

----------------------------------------------------------------------------------------------------------------

Solution Overview

The solution allows calculating Proposed Budget for Portfolio Epics, Products, and People based on User or/and Team Allocations, representing what budget is needed to cover labor expenses. It'll connect Work Allocations monthly Forecasted Cost (via Demands) to Monthly Budgets of a Portfolio Epic, Products, and People so that you can see Monthly, and then Quarterly and Annual Proposed Budget considering all the created Work Allocations. It also distributes Forecasted Costs between Run/Grow and CapEx/OpEx categories based on the entered values.

When creating a new Work Allocation, you'll have to see CapEx and Run Percentage values defining which part of a Work Allocation should be put into which financial bucket.

The values will be calculated based on the entered percentage and distribute the Total Allocated Cost between those categories:

Further, the Demands created for Work Allocations will be connected to respective Portfolio Epic and/or Product and/or Connected Team / ART Monthly Budgets and roll up to Quarterly and Annual Budgets. Therefore, the total across all the Work Allocations will represent the Proposed Budget of a Portfolio Epic and/or Product and/or Connected Team/ART for each Month, Quarter, and Year, so you can make a data-driven decision on what Budget to approve for each Portfolio Epic and/or Product and/or Connected Team and a Portfolio in the upcoming Budgeting Year.

Note: Please keep in mind that when the solution is installed after you have used a system for some time and you have already had Work Allocations created, you'll need to set the correct CapEx (Percentage) and Run (Percentage) values for existing Work Allocations to get the numbers calculated into Proposed Budget. You can create a metric that will set the same values for all the Work Allocations or manually on each Work Allocation.

Solution Configuration

Configure the solution for other entities having Budgets

The solution will default connect the Work Allocation Demands to Portfolio Epic, Product, and Connected Team/ART BudgetsIf you do budgeting on e.g Portfolio Epic only you need to adjust several rules in the solution and delete Product and Connected Team from the parameters. To do that:

  • Go to Settings -> Automation Rules
  • Open the following automation rules:
    • Connect Demands to Work Allocation parent Budgets - main rule
    • Manual trigger - connect Demands to Work Allocation parent Budgets
  • Click JSON
  • Leave the needed entity names, for example, PortfolioEpic in the BudgetParents parameters
  • Click Save button

  • Open the following automation rules:
    • Trigger - connect Demands to a newly created Budget
    • Trigger - connect Demands to Work Allocation parent Budgets when Work Allocation is updated
  • Delete not needed entity names, for example, Product and Connected Team in the trigger line
  • Then click JSON
  • Leave the needed entity names, for example, PortfolioEpic in the BudgetParents parameters
  • Click Save button

Connect existing Work Allocations to Monthly Budgets

If you were using Work Allocations before installing the solution, you need to connect existing Work Allocations (their Demands) to Portfolio Epic and/or Product and/or Connected Team Monthly Budgets. To do that:

  • Go to Settings -> Automation Rules
  • Open the following automation rule:
    • Manual trigger - connect Demands to Work Allocation parent Budgets
  • Enable the rule
  • Click Save and Trigger button

-----------------------

Version: 3.0

Integrations

See how Targetprocess aligns and empowers business and IT with the help of powerful integrations.

Targetprocess facilitates enterprise agility at all levels by enabling both Business and IT to work in one holistic solution. To help ensure value flow visibility and collaboration across the entire enterprise, Targetprocess allows a powerful set of integrations covering use cases for different levels and roles within organization.

For Transparency above the Team Level 
 
EXPAND 2 INTEGRATIONS

Azure DevOps
Azure DevOps
Add Targetprocess on top of the team level tool: get visibility on Product and Portfolio level.
Atlassian Jira Software
Atlassian Jira Software
Ensure free data flow from Jira to Targetprocess for greater visibility for all team members.

For Continuous Integration and Continuous Delivery 
 
EXPAND 6 INTEGRATIONS

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
GitLab
GitLab
Automatically link branches and merge requests to Targetprocess entities.
GitHub
GitHub
Automatically associate branches and pull requests with Targetprocess entities.
Phabricator
Phabricator
Link code revisions with any Targetprocess entity.
Bitbucket
Bitbucket
Automatically associate branches and pull requests with Targetprocess entities.
Jenkins
Jenkins
Connect Targetprocess entities with work items, reflect issues back as Bugs or User Stories.

For Product Management, ITSM, Sales and Marketing to Stay on the Same Page 
 
EXPAND 5 INTEGRATIONS

Miro
Miro
Centralize unstructured communication on Miro’s online whiteboard inside Targetprocess.
Microsoft Project Server
Microsoft Project Server
Provide visibility into high-level goals and details about implementation for all teams.
Salesforce
Salesforce
Synchronize customer service, sales, the PM office, and development teams.
Zendesk
Zendesk
Allow all team members to collaborate on shared artifacts from customer service tickets.
ServiceNow
ServiceNow
Collaborate on shared work items, consolidate reporting across the entire organization.