Budgeting: Agile Release Train (ART) Funding Views 3.1.0 | Targetprocess - Enterprise Agility Solution

Budgeting: Agile Release Train (ART) Funding Views 3.1.0

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) Budgeting: Connection to Agile Release Trains (ARTs) (3bd5f3c7-ce05-44c8-8b2d-02863522e5c1) Budgeting: Connection to Teams (29090431-bb10-4f5a-b472-99db69200d93) - if you would like to calculate Proposed Budget based on

Trusted by Agile teams at show more

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)
  • Budgeting: Connection to Agile Release Trains (ARTs) (3bd5f3c7-ce05-44c8-8b2d-02863522e5c1)
  • Budgeting: Connection to Teams (29090431-bb10-4f5a-b472-99db69200d93) - if you would like to calculate Proposed Budget based on Team Work Allocations and Expenses

It can be extended by the following solutions (if you prefer Proposed Budget to be calculated automatically for Teams or ARTs and roll up to Agile Release Trains Proposed Budget):

  • Proposed Budget based on Work Allocations (b82de5e7-4b6e-48b0-aa7c-c533d423711a)
  • Budgeting: Proposed Budget Manual Entry (85007fc5-c6ca-40d6-8420-6eb5a10fc052)

It can't be used together with the following solution (as there only one vertical can be Funded):

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

It shouldn't be used together with the following solution:

  • Budgeting: Agile Release Train (ART) Proposed Budget and Actuals Views (af5a5550-b908-455c-ac8b-6f9f79adcd42)

Can be used together with the following solutions (if you would like to see Proposed Budget and Actuals for Portfolio Epics, Products, Value Streams, Solution Trains or Teams):

  • Budgeting: Portfolio Epic (Project) Proposed Budget and Actuals Views (5a0acc91-50f7-4d65-be2f-154fc6cec394)
  • Budgeting: Product Proposed Budget and Actuals Views (ae4872be-1088-403f-b058-9f69c62271bd)
  • Budgeting: Value Stream Proposed Budget and Actuals Views (a3c905dd-ad13-4496-ac3d-c54890fa057e)
  • Budgeting: Solution Train Proposed Budget and Actuals Views (1e4bd6c1-9838-410f-9b9b-7c974bfdfec8)
  • Budgeting: Team Proposed Budget and Actuals Views (b7b13408-957b-4e7f-8464-774dc105131f)

The following diagram represents a visualization of these requirements:


Solution Overview

The solution enables the views for a case when you fund Agile Release Trains (ARTs) and should be installed when you use the parameter "Work": "People Funding" in the Budgeting: Structure solution. The views in the solution are designed to support Portfolio Stakeholders and Agile Release Train (ART) Leaders in the activities related to portfolio investment planning, funding Agile Release Train (ART), and tracking actual labor and non-labor expenses through the months, quarters, and years.  

There are the following phases of a budgeting process:

  • Budget Target - describes the company's initial idea of distributing funds across Portfolios and defining guardrails (Run vs Grow, CapEx vs OpEx).
  • Budget Proposal - describes budgets proposed by Agile Release Train (ART) Leaders based on the funds needed to complete work planned for an Agile Release Train (ART).
  • Budget Approval - comparing the numbers in a Budget Target and Budget Proposal reflects the final decision on the investment into each Portfolio.
  • Actuals - shares information about labor and non-labor expenses related to a Portfolio and Agile Release Trains (ARTs).

While every company process slightly differs from another, all the activities fit one of these processes.

Solution Flow

Step 1: Set Budget Targets

Budget Target describes the company's initial idea of distributing funds across Portfolios and further between Agile Release Trains (ARTs). It's done based on the company vision and strategy for the following year's top-down. It answers the following questions:

  • How much do we plan to invest in each Portfolio?
  • How will this be distributed across Agile Release Trains (ARTs)?

Portfolio Owners usually perform budget targeting. Their main goal is to split the Target Budget across different Portfolios, define guardrails, and set what percentage of capitalization should be headed to, as well as the grow and run targets.

Portfolio Owners will handle planning on the Budget Targets dashboard, where you enter a Target Budget for a Portfolio and then for each Agile Release Train (ART).

Target CapEx and Opex (Percentage) define desired capitalizable and non-capitalizable expenses. Target Grow and Run (Percentage) – desired Run vs Grow expenses percentage on a Portfolio and for each Agile Release Train (ART). 

Target Budget In Scope for Portfolio is a sum of Agile Release Train (ART) Target Budgets. It's used to see if we distributed the total Portfolio Budgets properly and didn't over or under-plan it. It will be highlighted in red if the sum of Agile Release Train (ART) Target Budgets will be more than a Portfolio Target Budget, meaning we have planned to distribute more funds than available.

You can also enter the numbers on a Portfolio Annual Budget detailed view -> Budgeting tab:

Agile Release Train (ART) Leaders will see and can update the information about Target Budget of a specific Agile Release Train (ART) on an Agile Release Train (ART) Annual Budget view.

Step 2: Budget Proposal

Budget Proposal is provided based on the information about funds needed to complete work (Portfolio Epics) planned for a Agile Release Train (ART) in the upcoming Year

 It answers the following questions:

  • What resources are needed to complete work planned for an Agile Release Train (ART)?
  • What are the forecasted funds for Labor Costs and necessary Non-Labor Expenses?

There can be different ways of calculating a Proposed Budget for an Agile Release Train (ART): based on Team or ART Work AllocationsHeadcountPortfolio Epic estimates, or other parameters (using additional solutions), or manually entered in this solution if the numbers come from another system or are approximately guessed by Agile Release Train (ART) Leaders.

Note: For now, only the Proposed Budget based on Work Allocations for Teams and/or ARTs is supported. It'll be calculated for each Team/ART and rolled up to a Solution Train and a Value Stream (if they exist).

The Proposed Budget consists of a Proposed Labor Budget and a Proposed Non-Labor Budget (defines expected non-labor expenses, such as SoftwareHardware, etc.).

Budget Proposal - Labor

The Proposed Labor Budget usually reflects how much money is needed for labor expenses. You can use the following solution to do that:

  • Proposed Budget based on Work Allocations (b82de5e7-4b6e-48b0-aa7c-c533d423711a), where Project Managers would create Team and/or ARTs Work Allocations, defining the needed people for a project, desired period and percentage.

Calculated Costs will be distributed across Portfolio Epic Monthly Budgets and roll up to Quarterly and Annual Budgets. Thus, we'll see the Proposed Labor Budget on a Portfolio Epic Annual Budget

Further, by selecting which Portfolio Epics are taken in scope, we'll form Agile Release Train (ART) Proposed Labor Budget.

Budget Proposal - Non-Labor

The Proposed Non Labor Budget will be formed based on the Expenses Proposed amount. First, you'll create the estimated Non-Labor Expenses (for Teams or ARTs depending on what is the lowest level of Budgets you have), defining the needed amount. The Expenses will be connected to the respective MonthQuarter and Year and be shown as a total Annual Proposed Non-Labor Budget.

Step 3: Budget Approval

Comparing Target Budget and Proposed Budget for each Portfolio on a Budget Approval dashboard, Portfolio Owners decide if they will go with the initial Target Budget or increase/decrease and distribute it differently across Portfolios. 

Further, the budget is distributed across Agile Release Trains (ARTs). In the Approved Labor Delta and Approved Non-Labor Delta fields, you can see the difference between a budget approved for the Portfolio and the total budget approved for Agile Release Trains (ARTs) in the Portfolio so that you know you approved the correct total budget across Agile Release Train (ART).

There can be a situation where an Agile Release Train (ART) Proposed Budget is much higher than a Portfolio Target BudgetPortfolio Owner needs to decide whether we will go with the suggested scope and increase a Portfolio Budget or decrease the scope by removing some Portfolio Epics.

Step 4: Actuals

Costs represent Labor Costs and Expenses represent Non-Labor Expenses. They will be aggregated from ART or Team Costs (based on the lowest level in the Budgeting hierarchy you use)

The total Actuals will be aggregated for each Agile Release Train (ART) and a Portfolio by Month, Quarter, and Year and can be viewed on the Actuals dashboard. Here you can focus on a specific YearPortfolio or select a Agile Release Train (ART) to focus on the details.


Version 3.0


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 

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 

Azure DevOps
Azure DevOps
Automatically associate branches and pull requests with Targetprocess entities
Automatically link branches and merge requests to Targetprocess entities.
Automatically associate branches and pull requests with Targetprocess entities.
Link code revisions with any Targetprocess entity.
Automatically associate branches and pull requests with Targetprocess entities.
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 

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.
Synchronize customer service, sales, the PM office, and development teams.
Allow all team members to collaborate on shared artifacts from customer service tickets.
Collaborate on shared work items, consolidate reporting across the entire organization.