What is the point of having shared teams? I don't think they serve any definitive purpose and for that reason, I wouldn't recommend to use it, but please let me know if I'm missing something.
First of all, lets say I have a shared team with developer A and developer B in it, both of which have 40hrs weekly hours. Now lets say I have 2 plans - Plan A and and Plan B.
I can add the shared team to both plans, and in each of the plans, both dev A and B have 40hrs available per week. But now if both plans run at the same time, Portfolio treats it as if each dev has 80 hrs available, and doesn't flag anything.
So let's say both plans involve work that will be done at the same time, and dev A and B both are allocated to them (via the shared team) because they can switch back and forth between the two plans. But lets say for now I want dev A working on plan A and dev B working on plan B.
So for plan A, I keep dev A at 40 hours and set dev B to 0 hours.
And for plan B, I keep dev B at 40 hours and set dev A to 0 hours.
But the moment I commit these changes, they get reflected across all plans, so really whichever commit I end up doing last is what ends up being allocated globally. In this case, if I updated plan B last, dev B will have 40 while A will be 0, for both plans.
Ok, so purpose of shared teams is not to share hours where reducing hours in one plan can allow increasing hours in another plan. Or if you have 40hrs in each plan, then you're essentially overbooking that developer. But Portfolio doesn't see it this way.
Ok then maybe the purpose of shared teams is to specify vacation, exceptions, general hours of availability. But you can do this from the 'People' tab anyway (under the 'Managed shared teams' section).
So why use shared teams at all when you can't really share a team across plans without overbooking members, and you can configure availability via the People tab?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.