5teveH wrote:
His mind-set is 100% that of a developer He has that "blind spot".
What you are describing is a business problem. Titles have nothing to do with it. The basic hierarchy is - Customer - Requirement/business cases - Architecture - Design - Implementation - Test - Delivery - Repeat steps as necessary. And there are other factors that influence that. - Providing a solution that is robust, fast, etc. - Updating old code - Security - Making sure that something is delivered so money can be made to pay the bills. - etc The roles that any one person might successfully fulfill depend on their own experience and their coworkers skill as well. An 'architect' might be able to fulfill the first 4 roles but not be great at the detail work needed for the levels under that. A developer might seem to have adequate knowledge of both the business and the code but fail when the business changes. Of course failures can come from many places. I know of specific case where a service was created, delivered and successfully used but a contract very early in the company history guaranteed they could not make enough money to keep going. In another case a design or perhaps implementation decision lead to a multi-billion dollar company failing in less than a year due to a security problem. Or a developer that was handed a detailed design and decided to ignore it producing a solution that did not meet the business needs the design dealt with. This is all impacted by complexity. A single man shop would need to provide all of that. But when a company has thousands of employees single employees just cannot learn everything needed to manage all roles. I have worked at companies where test automation was handled by a team of employees.
