Why One Skilled Developer Is Crucial for Effective Architecture Design

In a software team there are many members such as project manager, architect, team lead, and developers, but only the architect, lead, and developers write code. To deliver an architecture you must leverage the relationships among these three roles and assign the right people.

What is business?

Business is the primary basis for architecture design; a business‑control role must work together with the architect, and this role can be a single person or a group.

For example, developers often complain that a design is unreasonable, leading to resistance or refusal to code. This happens when the design contradicts the developers’ understanding of the project. If the design is created together with the business‑control role, such friction is greatly reduced.

What is development?

Development is actual coding, which consists of framework coding and project implementation coding. A common misconception is that the architect must write the entire framework. In reality the architect should only participate partially; a technically strong team member should co‑author the framework, while the architect focuses on higher‑level concerns.

This dedicated developer also handles questions and extensions of the framework, providing technical growth for that person and saving the architect’s time.

Why is this person needed? When developers criticize the framework for being vague, the architect’s explanations often fall flat. A developer who can address both technical and business concerns can keep the project moving smoothly.

The gap between theoretical architecture and reality is large: theory ignores personnel conflicts, skill predictions, and human emotions. Real projects require negotiation, communication, and interpersonal skills that no single person can provide. Successful delivery depends on collaborative leadership and technical support.

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