Often they don’t truly understand the thinking behind the strategy. They don’t engage the executors early and ask, ‘How will this actually work?’ The executors contribute to the trouble as well. They don’t bother to truly understand what it takes to implement the ideas. In the worst cases the strategists adopt an elitist, disconnected mindset: We’re the idea people, someone else will make it happen. What typically happens is an awkward hand-off between the two. “Unfortunately, it’s far from common practice. I suspect that managers creating or maintaining an organizational structure that separates strategy and execution believe that individuals on each side will behave rationally, build relationships, and communicate effectively in order to get their work done.
Architects get frustrated by their “adversarial” development teams. Developers get frustrated with the “out of touch” architects. Up-front decisions made by architects become painful for the implementation team. The longer architects stay in their role decoupled from implementation, the less qualified they are to judge the maturity and risk profile of new tools, processes, and paradigms. The executors’ dirt-in-the-fingernails view on the ground is much different from the strategists’ high-minded view from the air.” I agree with Doug-especially as relates to software projects-that: Creating a Chasmĭoug Sundheim’s article Closing the Chasm Between Strategy and Execution insightfully describes the risks and dysfunction I’ve observed when architects work on a distinct team separate from the development team. During execution, the development team checks in with an architect at specific checkpoints or when the constraints defined by the architect are challenged. The development team inherits constraints defined by the architect. An architect usually works on a team of architects who are responsible for early application architecture design, approval at points during development, and approval before production launch.
The corporate ladder for software developers can lead to the software architect job. Separation of Architecture & Implementation A product development organizational structure where software architects work on a team separate from the development team can be a recipe for dysfunction, reduced quality, and poor morale.
0 kommentar(er)
