Common Misconceptions about Software Architecture – Part III

“Architecture is the work of a single architect.”
“A great architecture is the work of a single architect. ” Fred Brooks wrote this in 1975.
Granted, there are some great examples of this: But in practice, geniuses are rare, and in many organizations good architectures are most often the work of a small group of people working as a team.
The architecture team acts as a team as defined by Katzenbach and Smith A team is a small number of people with complementary skills who are committed to a common purpose, performance goals, and approach for which they hold themselves mutually accountable.
So the architecture team is not a committee, meeting every Tuesday at 15:00; it is not a problem clearinghouse; it is not an ivory tower, a resting place for successful but tired designers.
Especially for complex systems, a well-chosen architecture team is needed to bring the right mix of domain and software engineering experience, and the right mix of design specialties (hence minimizing the [my favorite architecture] effect mentioned above). The architecture team needs significant flexibility in composition and structure. Some of the architects may become the architects of subsystems, once those have been defined.
However, it is important to have a clearly designated team leader: a lead software architect who can drive the effort, arbitrate, resolve conflicts, and bring timely closure to project tasks.
Philippe Kruchten

گزیده:
«موفقيت» به دست‌ آوردن چيزی است که دوست‏داری و «خوشبختی» دوست داشتن چيزی است که به دست ‌آورده‌ای.