User Demand and Allocation 3.0.1 | Targetprocess - Enterprise Agility Solution

User Demand and Allocation 3.0.1

Requires the following solutions to be installed: User Availability in Periods (e66dfd23-316f-4cc7-9604-63097fe99d67) Demand and Allocation Core (19c387f1-4dce-428d-b2a6-fec0b2312bd8) Can be used together with the following solutions: Team Demand and Allocation (868e93a9-2211-4b45-b207-4399b3e9d9ce) Agile Release Train (ART) Demand and Allocation (5094bc62-d370-47a5-af4c-45d53ce63e68) It

Trusted by Agile teams at show more

Requires the following solutions to be installed:

  • User Availability in Periods (e66dfd23-316f-4cc7-9604-63097fe99d67)
  • Demand and Allocation Core (19c387f1-4dce-428d-b2a6-fec0b2312bd8)

Can be used together with the following solutions:

  • Team Demand and Allocation (868e93a9-2211-4b45-b207-4399b3e9d9ce)
  • Agile Release Train (ART) Demand and Allocation (5094bc62-d370-47a5-af4c-45d53ce63e68)

It can be extended by the following solution:

  • User Demand and Allocations by Job Profile and Skills (7cb3d0e4-7ba2-4a9c-9ae8-d69a202ac54d)
  • Man Days instead of Percentage (7adef4e5-e819-4a95-9985-cc3664f6f737)


Solution Overview

The solution allows tracking the upcoming demand of People (individuals) for existing and forthcoming InitiativesProjects, or any other Work Items, seeing people's availability, and balancing the available and allocated capacity within a specific Period (such as Week, Month, Quarter, Year or Custom Period). Such demand and capacity management approaches are applicable for high-level planning when no work estimates are provided yet, and no lower-level items, such as Features or User Stories, exist. Planning is happening to roughly understand how much capacity is needed for work to be done and find the right people to do the work. It also allows tracking if people are going to be overloaded or see who is available to spread the load.

The solution is installed by default for Portfolio Epics (so we create User Work Allocations for Portfolio Epics and track capacity based on this). However, we can connect the capacity solution to any other entity you prefer to do capacity planning for.


Solution Flow

There are the following entities are enabled by the solution:

  • Work Allocation – represent work demand defining for how long (Planned Start and Planned End dates) and for which Percentage (%) we need a User to work on an item. We can define a specific person (Connected User) or create a work allocation without a person if we don't know who it will be or if it doesn't matter at the moment. There can be multiple work allocations for the same person with different % during different Periods.
  • Demand - represents demand for a specific Period, i.e. if capacity planning is happening based on a Month Period and a work allocation is planned for 3 months, then the system will automatically create 3 Demands for each Month within this Work Allocation - one Demand for each Period.

1. Define Demand for a Portfolio Epic

To plan capacity and allocations of people, Project Managers or Initiative Owners first should create Work Allocations for a Portfolio Epic, defining what users (or what capacity if a user is not known yet) they need to work on a work item. Work Allocations may not have a Connected User if there is no need for a specific person. It'll be possible to find an Available User later. Work Allocation can be created either from a Portfolio Epic detailed view or from the Portfolio Epic Demand view in the left menu.

Here you need to define:

  •  Status of Work Allocation (Requested or Approved, later it also can be Rejected. Work Allocations with Rejected status are not considered in User Capacity.)
  • Percentage (%) of capacity requested
  • Planned Start and End Dates
  • Connected User if known.

When a Work Allocation is created, it’ll be connected to the respective Periods (Weeks, Months, Quarters, Years or Period) based on its Planned Start/End Dates. Demands will be generated automatically for each respective Period. Demands inherit work allocation parameters, such as Capacity %Planned Dates, and a Connected User.

2. Process Unfulfilled and Overloaded Demand

There are several views for people responsible for fulfilling the demand, as well as ensuring that there won't be overloaded people.

New (Requested) Demand

On this screen you can see all the current and future Work Allocations in the Requested state. Here is a list of already allocated demands (Work Allocations with a Connected User), which need to be Approved, and Work Allocations with no Allocated User, where we need to find a person to allocate. In the Available User field you can find people available based on their current load and availability (%) for the needed duration (Planned Start and End Dates of Work Allocation). In Connected User field you'll see all the people in the company. You can choose a person from that list, however, a person might get overloaded when allocated to this Work Allocation.

Approved and Requested Demand to Process

There are cases when Work Allocations got Approved however there is no user allocated to it yet, or there are overloaded people. You can see such Work Allocations on the Approved Demand to Process view. Here you can resolve Overloads by choosing another Available User and also can allocate Users to the not fulfilled Work Allocations.

3. Allocation Status Dashboard

This dashboard helps to focus on Portfolio Epics with overloaded people allocated or going to be overloaded in future; see on a chart where in time these people are overloaded and make a change to fix overloads.

4. People Load Dashboard

This dashboard helps to focus on People overloaded across all the Portfolio Epics they work on, as well as see a chart in which Periods they are overloaded and make a change to fix overloads.

Note: After the solution installation, the system automatically adds extra Portfolios and Teams filters to both Dashboards. You need to delete them from the dashboards, as they won't apply correctly to the data on dashboards. To do that:

  • Click Actions -> Set up dashboard
  • Go to the Setup tab
  • Click Portfolios filter
  • Uncheck Show in the View header checkbox and save
  • Repeat for Teams filter

5. Work Allocation Roadmaps

There are two more views where we can see a roadmap of Work Allocations.

The first one shows Work Allocations by User, where we can focus on a specific User and see their Work Allocations across all the Portfolio Epics over time:

The second one shows Work Allocations by Portfolio Epic, where we can focus on a specific Portfolio Epic and see their Work Allocations for all the Users:


Solution Installation

Adjust Quick Add (needed only if you use 2 or more Demand and Allocation solutions – for Users, Teams and/or ARTs):

How to adjust Quick Add:

  • Go to Settings -> Quick Add
  • Select Work Allocation in the list
  • Delete Connected User
  • Add configurable drop-down for Connected User

Known Bug: Connected User, Team or Agile Release Train may not appear in Quick Add customizer. Please contact us to fix the issue.

Update Period Type (only needed if you use Weeks, Quarters, Years or Periods instead of Months)

The solution is installed for Months by default. However, if you prefer to use Weeks, Quarters, Years or Periods instead, you need to adjust the Configurable Dropdown User Allocation mashup and Reports in the solution.

1. Update Mashup

  1. Go to Settings -> Mashups
  2. Open Configurable Dropdown User Allocation mashup
  3. Update periodType value in the mashup from MonthPeriod to WeekPeriod, QuarterPeriod, YearPeriod or Period

2. Update Reports

There are two reports in the solution which need to be updated with the needed Period:

  • Portfolio Epic Allocation Status
  • People Load

To do that:

  • Clone the reports (if you do this for Custom Period, not needed for Weeks, Quarters and Years)
  • Open the report
  • Click Setup up Report button
  • Find the needed Period in Data fields
  • Replace Month Period on X axe on the report


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.