Capacity view is not flexible

Who would benefit?

All team members as we use the velocity view for assignments and epic prioritization.

What impact would it make?

The view would be more realistic and not padded

How should it work?

Aha calculates used and available capacity for each resource based either on the epic sizing or individual requirements sizing but not both.

1. What if there is an epic assigned but some of the major requirements under that epic are assigned to another resource? Today the sizing for the entire epic impacts the available capacity for the epic owner only.

2. For a requirements owner , how can that resource's available and used capacity be updated to reflect that?

3. If an epic is not assigned but the individual requirements are assigned and sized, how would this work?

4. If the velocity view is based on the sizing of requirements, then requirements should become mandatory for every epic regardless of size with an assigned owner and a sizing as mandatory fields along with date range.