Architects and Project Managers: Part 1

Scott Berkun runs mailing list on project managment. Each week there's a new topic whihc is discussed by the mailing list members. This week's topic touches the issue of architects and project managers:

I'm wondering how to behave when there is an architect that has "signing authority" on what the developer group does, and abuses that authority to go into micro-details, thereby both destroying the developers joy of creation and professionalism, since they are not allowed to learn on their own the consequences of their designs/choices.

The problem is he's (probably as usual for architects) very smart technically, not that much EQ-wise, and very important to the organization.

How do we keep the architect, but change his attitude?

This brings several interesting questions:

• How do we, as architects, know we cross the boundary between steering the project in the right technical direction to "destroying the developers joy of creation and professionalism"?
• Assuming this PM is right, what's the best way to defuse the situation?
• And in wider scope, how do you balance and divide the responsibilities between the project manager and the software architect?

I am interested in hearing what you have to say so I'll wait a few days and tell you my opinion next week. :-)

Posted by Arnon Rotem-Gal-Oz at 04:09 AM  Permalink