How to deal with part time team members with split allocations.
The Person who is technically on your team (but also… Not Really)
You know exactly who I'm talking about.
On paper, such team members are part of the team. But in reality, they exist in a kind of permanent limbo: half here, half somewhere else.
This can be a UX designer who supports three teams simultaneously. This can also be a senior developer who is officially 50% on your team.
It’s not their fault, though.
They're usually trying their hardest to serve multiple teams while knowing, deep down, that they can't fully satisfy any of them.
The fault, if we're assigning it, sits somewhere in the organizational structure: the hiring problems, the company’s budget just can’t be stretched problems, etc.
In this post, I want to walk you through:
what's actually happening beneath the surface when you have split-allocation members on your team
why the standard Agile instinct to complain won’t work, and
what successful teams are doing to make it work in this situation
The goal of this post is to form a team that delivers with whatever setup it actually has.
Let’s get started.
Got an urgent question?
Get a quick answer by joining the subscriber chat below.
