Demand and capacity planning may happen by different periods. It can be Years for high level planning, Quarters, Months or even Weeks. It can also happen by a custom Period, such as Program Increment, Team Iterations, 2 Months period or any other.
We already supported Demand and Capacity Management by Years, Quarters, Months and Weeks. And we're happy to announce that now Demand and Capacity Management can be done by a Custom Period.
The solution introduces a new entity – Period, representing a custom time frame, usually used to organize Releases (Program Increments) or Team Iterations with the exact Planned Start/End Dates. This entity is required for the solutions related to planning people's availability and capacity, managing budgets, and tracking costs if it's happening not based on Weeks, Months, Quarters or Years but rather based on Team Iterations or Releases (Program Increments).
Demand and Allocation by Custom Period
The solution enables the possibility to do capacity planning by a Custom Period. It will work the same way as it works for Years, Quarters, Months and Weeks, but for a Custom Period, which is usually either Program Increment or Team Iteration; however, it can be any other preferred Period.
There are also new versions of Demand and Allocation solutions, which now support Custom Period.
- User Availability in Periods
- Team Availability in a Periods
- Agile Release Train (ART) Availability in Periods
- Demand and Allocation Core
- User Demand and Allocation
- Team Demand and Allocation
- Agile Release Train (ART) Demand and Allocation