back
1 comments
The team name seems ridiculous, a non-starter, but it's not the actual name.

> The team that owns the common code is then responsible to explore code across the feature teams to be refactored, improved, and better aligned, for the sake of maintainability and scalability. The work essentially is like managing tech debt. Hence it is not really a misnomer to call that group the tech debt management group.

> Anyway, the focus of this article is not to define the name for the group — you may name it core, infrastructure, or architecture — but to lay out the struggles of such a group and explore ways to aid it.