When asked “What is your architecture?” most people immediately respond with how their software is laid out and what their plans are for improving parts of it. Rarely does anybody really think through their team and organizational architecture, and even more rarely do people understand how that may fundamentally impact how the software gets written and the product that comes out at the end.
How do you prevent your organization from killing your product, and how can each person contribute to make things better?
Video producer: http://chariotsolutions.com/