Capacity for teams currently allows you to create teams and add detailed estimates to records. However, we have a challenge with the way a team's capacity is calculated.
We have cross-functional teams, which include people in product management, QA, engineering, etc.
Each person I add to a team in Aha! contributes to the team's overall capacity. But this is only useful if every person is in the same role.
A team with 6 engineers, 3 testers, and 1 PM, might - for example - show as having 400 hours of weekly capacity. In reality, they have 240 hours of engineering, 120 hours of testing, and 40 hours of product management capacity. This distinction is critical as we create more tactical plans.
A workaround for this is to create teams organized by role. This is absolutely doable for high-level plans and can be a useful view. However, this is an ineffective way to communicate to our stakeholders who is actually doing the work.
We would like the teams in Aha! to match the cross-functional teams we have at our organization. To do that, we need a way of designating a team's capacity by skill and estimating effort accordingly.
One solution I've found is to add different teams for the various skillsets.
Red Team - Front End
Red Team - QA
Red Team - Designers
this would also be a great way for us to indicate which features could or could not be implemented within a certain team as opposed to having a generic (e.g.) DB team when you don't know which scrum team the DB people actually belong to.