Understanding Team Roles in Software Architecture: Business, Development, and the Need for a Technical Lead

A software project typically includes many members such as a project manager, architect, team lead, and developers, but only the architect, lead, and developers actually write code. Successful architecture depends on leveraging the relationships among these three roles and selecting the right people.

What is business? Business provides the essential basis for architectural design; a business‑control role must work together with the architect, and this role can be filled by one or several individuals.

When business stakeholders are not involved, developers often complain that designs are unreasonable—whether the issue lies in database schema, workflow, or other aspects—because the design conflicts with their understanding of the project.

What is development? Development is the actual coding, divided into framework construction and project‑specific implementation. A common misconception is that the architect should write the entire framework; in reality, the architect should only participate partially, and a technically strong team member should co‑create the framework, later handling questions and extensions from other developers.

This dedicated technical person helps alleviate complaints about poorly detailed frameworks, as a single voice cannot address all concerns, but a knowledgeable developer can explain and adjust the design, keeping the project on track.

The gap between theoretical architecture and real‑world practice is large: theory ignores personnel conflicts, skill predictions, and human emotions. In practice, negotiation, communication, and interpersonal skills are essential, and no single individual can fulfill all these roles without support.

Source: http://www.cnblogs.com/kiba/p/9207055.html