One of the more common coordination models is the Service Provider model. When a team is a Service Provider, they:
- Have valuable skills they offer other teams.
- Are a dependency for those other teams. They do work for those teams.
- Do their work per ticket, per project, or per initiative. When their work is over, they either do work for someone else or work on their own priorities.
The Service Provider model is one of the least effective coordination models in software engineering teams. There are some legitimate reasons to use this model, but you should avoid it unless you’re aware of the tradeoffs.