Ask HN: Any guidelines or rules on managing large team with large codebase?

Was looking around on internet on how to set processes in place to bette manage a large team which works on a large codebase and deals with multiple business stakeholders to get. - Need to sort out both team structure & clean the code. - Was looking at clean code (SOLID principles) as guidelines to re-architecture codebase - And to organise team units around the independent modules they will work with

Would appreciate any leads on where can i find any reading material or experiences of folks having done such transitions & how they managed team incentives/KPI alignment to enhance overall productivity of the organisation...

tl;dr Need to move from (Messy team + Messy codebase) => (Clean team + codebase structure) for better productivity. Any guidelines or stories on this from experiences?