On a software team with a software architect and a project manager, should the architect report to the project manager? Or should the architect report to the project manager's superior?
I have difficulty coming up with pros and cons for both options. The only things I could find were:
- the architect and project manager may hold conflicting opinions (but not which ones), and
- an example where the architect reports to the project manager (but not why).
Since the architect guards quality, and the project manager guards time and budget, there are bound to be conflicts. But how is this best reflected in the reporting hierarchy, and why?
To clarify my question:
- the question is not company-specific. See @Marv's comment for explanation.
- It's hard to give a short definition of a software architect. To summarize Simon Brown: a software architect is responsible for the technical aspects of the software project, and coaches the team's developers. I do not mean a tech lead, which is a role combining architecture and project management.
- there doesn't seem to be disagreement on what a project manager does.
- the Project Management.SE site does not seem suitable, as it's about project management, not organization of business.