Man Days instead of Percentage for Work Allocations v2 | Targetprocess - Enterprise Agility Solution

Man Days instead of Percentage for Work Allocations v2

Requires the following solutions to be installed: User Capacity Demand and Allocation (6d990828-2bd0-45af-afaf-e68d45b6a148) – if you need it only for User Allocations Team Capacity Demand and Allocation (64f866ef-fdcf-41cb-b6e6-bb56330fc4d1) – if you need it only for Team Allocations Both

Trusted by Agile teams at show more

Requires the following solutions to be installed:

  • User Capacity Demand and Allocation (6d990828-2bd0-45af-afaf-e68d45b6a148) – if you need it only for User Allocations
  • Team Capacity Demand and Allocation (64f866ef-fdcf-41cb-b6e6-bb56330fc4d1) – if you need it only for Team Allocations
  • Both mentioned above solutions are required – if you need it for User and Team Allocations together

Can't be used together with the following solution:

  • Hours instead of Percentage for Work Allocations (e2a03d28-d3c9-4577-a993-1b82db3b805c)

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

Solution Overview

The solution is an extension of User and/or Team Capacity Demand and Allocation solutions and allows entering required Man Days (or MD) to do work instead of Percentage. The Percentage will be calculated for a User based on User Weekly Hours, and for a Team based on Users in a Team Weekly Hours, and based on the Hours set for a Man Day in the solution configuration. By default one Man Day is equal 8 Hours.

User Weekly Hours are defined on a User View:

After the solution installation and configuration (see below), you'll be able to enter the required MD instead of Percentage when creating a Work Allocation:

A Percentage will be calculated based on the assumption that a Man Day takes 8 Hours and people work 5 Days a Week, excluding Weekends from Working Days calculation. It'll be calculated using this approach for Work Allocations with no Connected User or a Connected Team.

When you allocate a Connected User, it'll take their Weekly Hours and Time Offs (Vacations, Public Holidays and Sick Leaves) into Percentage calculation. Likewise, allocating a Connected Team will take into account Users in a Team Weekly Hours and User Involvement in a Team into Percentage calculation.

In case you'd like to use any other number of Hours in a Man Day, you need to adjust the automation rules with the correct number of Hours, see the Solution Configuration section below.

You'll also see new fields on User/Team Availabilities showing how many Total MD a User/Team has in a Period, how many of them are Reserved by Work allocations or by a Time Off, as well as how many Available MD are left:

image of Availabilities inner list with MD

The fields are calculated using the following formulas:

  • Total MD for a User = Period.WorkingDays * User.WeeklyHours/5/ManDayValue (8 hours by default)
  • Total MD for a Team = Period.WorkingDays*Users.Sum(WeeklyHours/5 * User.Involvement%/100)/ManDayValue (8 hours by default)
  • Reserved MD = Demands.Sum(MD) excluding Time Off Demands
  • Available MD = Total MD - Reserved MD

Everything else will work the same as in User and/or Team Capacity Demand and Allocation solutions.

Targetprocess Image

Solution Configuration

Percentage Field

As with this solution Percentage will be calculated automatically, you need to make this field system for Work Allocations. You can do this in the following way:

  • Go to Settings -> Custom Fields
  • Select Work Allocations in the filter
  • Open Percentage field
  • Make it System

Automation Rules Adjustment

Several automation rules need to be adjusted to make the solution work correctly for the scenarios when you only use the User Capacity Demand and Allocation solution, the Team Capacity Demand and Allocation solution or Both solutions.

  • Go to Settings -> Automation Rules.
  • Open the following rules one by one:
    • Work Allocation Percentage calculation based on MD (Man Days)
    • Recalculate Work Allocation Percentage based on MD (Man Days) when a Team is updated
    • Recalculate Work Allocation Percentage based on MD (Man Days) when a User is updated
  • Set the following parameters correctly:
    • workingHours – it's set as 8 hours for a Man Day by default; change it if your Man Day day takes less or more working hours,
    • onlyActiveUsers – this parameter is applicable to Team Capacity Percentage only. It'll calculate only Active Users in a Team when True; it'll consider Active and Inactive Users when False.
    • AllocationType – set Team when using Team Capacity Demand and Allocation solution only; set User when using User Capacity Demand and Allocation solution only; set Both, when using both solutions together.

Process Existing Work Allocations

Suppose you already have Work Allocations in the system and would like to calculate Percentage based on MD entered. In that case, you need to trigger the Initial - Calculate working days for Work Allocations rule. To do that:

  • Go to Settings -> Automation Rules
  • Enable and Open Initial - Calculate working days for Work Allocations rule
  • Click Save and Trigger Now button

Note 1: Please keep in mind that all the Percentages entered manually before will be re-calculated, so only do that if you want to re-calculate them.

Note 2: The rule, if enabled, will be executed every 7 days to re-calculate Woking Days. So you need to disable it if you don't want your past work allocations to be re-calculated.

Solution Views

To use the solution, you can use all the same views for the solution as created for User Capacity Demand and AllocationTeam Capacity Demand and Allocation or User and Team Capacity Demand and Allocation Connector. Just add the MD unit to all the views next to the Percentage unit to see the MD required for Work Allocations.

You can do this in Actions -> Set up view -> Customize Cards.

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.