Team structure
There's a popular adage in software design called Conway's Law, which suggests that the design of software in any organization is influenced by the structure of teams in the organization and the way they communicate with each other. It makes perfect sense if you think about it. Software development teams often tend to work on isolated libraries and code bases (or at least, code areas) that talk to other libraries and code bases developed by other teams. In a sense, there's almost a one-to-one mapping between teams and the set of code assets they work on. This can be a valuable factor that influences where module boundaries are drawn and how modules designs begin to separate from one another. Each team works on one or more modules, ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access