It's a peopleware problem, more than a technical one. If there's no trust in the whole team, then all the design/architecture challenges are less important.
I've just read it today, a good post on this topic:
"We all know Conway’s law: “any piece of software reflects the organisational structure that produced it.”. In the same way, communications patterns between people affects the quality of the software. After 6 months working on a greenfield project I realised I could link all the areas with major technical debt to some unsolved personal conflicts in the team."
It's a peopleware problem, more than a technical one. If there's no trust in the whole team, then all the design/architecture challenges are less important.
I've just read it today, a good post on this topic:
"We all know Conway’s law: “any piece of software reflects the organisational structure that produced it.”. In the same way, communications patterns between people affects the quality of the software. After 6 months working on a greenfield project I realised I could link all the areas with major technical debt to some unsolved personal conflicts in the team."
http://bitlyfied.com/2013/12/19/happiness-and-other-technica...