Here's a law dating back to the 1970s:
Conway's Law: Any organization that designs a system will produce a design whose structure is a copy of the organization's communication structure.
More than 25 years ago, a book called The Psychology Of Computer Programming talked at length about this kind of thing.
For example, a compiler's internal structure will likely be split along lines dictated by the existing expertise and political structure, rather than some structure purely dictated by technological considerations.
However, many technologists tend to frame their view of the world using technical considerations in preference to political/organisational considerations. The upshot can be that people attempt to defend the structure of a software project in technical terms because they think that other drivers of the structure aren't (or shouldn't be) relevant. If, instead, there was a wider recognition that it's perfectly OK for non-technical considerations to be the most important shaping factor on the structure of software, rational debate about the structure would be easier; for instance, people would address broken software structure by addressing the underlying organisational mismatch, rather than searching for purely technical fixes.
It's worth keeping this principle in mind when a technological goal seems strangely hard to accomplish. Look at how the effort is being organised, and how well it fits with the people who are actually supposed to do the work. Is it something that requires a high degree of inter-team co-ordination in an environment where autonomy is highly prized? Or, conversely, is it something that requires initiative and a number of prototyping runs in an environment where blaming behaviour is common, and failure attracts censure? In either of those two cases, you've got a problem.
Instead of banging your head against a brick wall, look at how you can orient things to align with the setting you're working in. If autonomy is highly prized, keep the shared infrastructure as loose and minimal as possible, and bend over backwards to encourage participation (or it won't happen). If control and blaming are more the order of the day, use the hierarchy for what it's good at, and get skunk-works set up to do the more experimental stuff, providing a separate safe environment for the riskier failure-prone part.
No comments:
Post a Comment