Overloaded Specialists in a Self-Managing Team
A seven-person product team is six weeks into an eight-week release. Two specialists, security and data, are assigned to 11 of 14 open tasks. Daily stand-ups show 30% of time going to unplanned production support, and velocity has fallen from 42 to 28 story points per two-week cycle. The team agreed to self-assign work, but the project manager notices three tasks sit unclaimed while the specialists start new ones. The product owner wants to add two more features to meet a launch promise. The team's working agreement says WIP limit is two items per person, but it is not being followed. The project manager's manager suggests direct task assignment. The team is co-located two days a week and remote three days. One specialist has announced leave in the final week.
1. What intervention should the project manager make without taking over task assignment?
Read the worked answer
Facilitate the team to see its own system. Put the work board and WIP limits on the wall and in the remote tool. Ask the team to mark the 30% unplanned support work visibly, then discuss why specialists are starting new items while three tasks are unclaimed. Possible causes include unclear task ownership, missing skills, and support work that only specialists can do.
The project manager should protect specialist capacity by pairing, documenting support procedures, or routing simple support away from the team. Revisit the working agreement with the team and ask what it will change for the next cycle. Coach the team to pull work within WIP limits and to escalate blockers. Do not assign tasks directly unless the team cannot self-correct after a clear intervention. The aim is to fix the bottleneck, not to look busy.
2. How should the project manager respond to the product owner's request for two more features?
Read the worked answer
Make capacity visible. With a velocity of 28 story points and two weeks left, the team has limited room, and the specialist leave reduces it further. Ask the product owner to size the two features and compare them with the remaining release scope. Present options: defer the new features, swap them for lower-value existing scope, or accept a date change. Adding people late is usually a cost and risk increase, not a quick capacity gain.
The project manager should not silently accept the request, and should not simply say no. Use the dynamic plan: what can be delivered, what must be dropped, and what decision is needed. If the product owner insists on a launch promise that exceeds capacity, escalate to the sponsor with the trade-off stated plainly.
3. What should the project manager say to the manager who suggests direct task assignment?
Read the worked answer
Explain the boundary: the team has agreed to self-manage, and direct assignment would remove ownership and hide the real bottleneck. It might produce short-term output, but it would not fix the specialist overload or the unplanned support load. Agree a test: the project manager will facilitate one cycle of WIP discipline and support-work visibility. If the team still cannot self-correct, the project manager will intervene more directly and report back.
Ask the manager for help removing the systemic cause, such as production-support demands or missing skills. Keep the conversation factual, not defensive. The project manager is accountable for the team's ability to deliver, not for choosing every task.