  For traditional modular software systems, "high cohesion, low coupling" is a
recommended setting while it remains so for microservice architectures.
However, coupling phenomena commonly exist therein which are caused by
cross-service calls and dependencies. In addition, it is noticeable that teams
for microservice projects can also suffer from high coupling issues in terms of
their cross-service contribution, which can inevitably result in technical debt
and high managerial costs. Such organizational coupling needs to be detected
and mitigated in time to prevent future losses. Therefore, this paper proposes
an automatable approach to evaluate the organizational couple by investigating
the microservice ownership and cross-service contribution.
