Right now teams can only provide one value for people on their team which applies to the who planning scenario. For example, if i have 5 team members, then i set 5 people on my team. But if i am starting the year with 5 but then have planned 2 headcount to be added in june, i dont have a flexible way to indicate that i have 5 people from jan to may and then 7 from june through december, and have the capacity report take that variable team size into account. We have to fudge it either way, either too little or too much capacity which is awkward when looking across an entire workspace or product line.
You can now schedule team changes to more accurately visualize team workload on the capacity report in Aha! Roadmaps — increasing your confidence that the team will be able to deliver on time.
This is one of the last things missing to move planning off of XLS. Same scenario - team size varies over the course of the planning year, as members come/go or TBHs are added. Separate teams w/ their own start end dates are clunky, and carry the overhead of having to add and them to a capacity estimate. Similar to how we enter monthly capacity estimates, having a monthly team capacity option would be ideal.
Example: Team A has...
Jan: 20 people
Feb: 20 people
March: 22 people (new hires!)
April: 22 people
...etc.
Having the same problem here. Thinking the best way to manage is using teams and a later start date for the new resources. Do you have any better ideas on a workaround?