We update hourly rates on an annual basis. The Teams we define span Scenarios so we need to be able to define an hourly rate by Scenario for a Team. This functionality will enable flexibility in cost reporting and forecasting.
Chris Brooks
almost 6 years ago
in Capacity planning
0
Future consideration
I want the ability to estimate in allocation percentages. For example: I'm planning 2H 2020 feature planning I want to say that 50% of Sally's time is dedicated to a specific initiative. I want to create that initiative, give it a date range of 2H...
Nathaniel Collum
almost 6 years ago
in Capacity planning
2
Future consideration
We have different teams that work around the clock in the each release. I need to be able to track per release the capacity so I can visualize each team individually and as a whole.
We use initiatives to track progress at a high level. The initiatives contain master features and features. Each feature is estimated in story points and no 2 features are the same size. In the current scenario, if I have 10 features within an ini...
samir karandikar
over 6 years ago
in Capacity planning
3
Future consideration
We're adopting a more flexible release strategy that is feature/initiative driven, not time boxed. It would be great to be able to generate a burndown chart for an initiative (even better: overlay several initiatives) so we can project/monitor our...
Choose unit to display estimate values in pivot tables
If a feature or requirement has an estimate of 5 days, then the corresponding estimate will count as 40 hours in the pivot table (for example when the requirement's estimated effort is summed as the cell value). This can result in figures that are...
Guest
about 10 years ago
in Capacity planning
11
Future consideration