Add a comment

 

Re: Why aren't software architects held accountable?

I share you vision but I verified a cultural misunderstanding by who take the decisions. When a project became complex, the roles and competence must be compliant with the complexity. Sometimes it's not important that the Project Manager has System Architect skills, other case require a Project Manger with that skill and in other case the Project Manager need a staff (System Architect, Software Architect, Operations,...). Recently we had a lot of discussion in a few company, we are doing a merge of technical staffs and I hear everyday the question that you pushed to us. But for every different staff the answer is different. I think that usually none recognize really the figure of a "System Architect" and rarely they are involved in project management. Many times I tried to analyze IASA and ACM library without results: there are NO accepted connection in a flowchart about role and responsability in doing correlations between System Architect and Project Management. Everywhere and everytime they are located in engineering staff, never like controller or manager. The most consolidated role is lead architect of architect or developer... but without responsibility on delivery and deploy. I see every day company spending tons of money only because no system architect are involved in designing and supporting the deployment. Best Regards Renato

Re: Why aren't software architects held accountable?


Title
Body
HTML : b, strong, i, em, blockquote, br, p, pre, a href="", ul, ol, li, sub, sup
Name
E-mail address
Website
Remember me Yes  No 

E-mail addresses are not publicly displayed, so please only leave your e-mail address if you would like to be notified when new comments are added to this blog entry (you can opt-out later).