知识卡片
面向开发的架构团队应与应用团队共同发现结构
另一种方式是由架构团队协调多团队共享的战略,包括大型结构、限界上下文边界和跨团队技术问题。它需以应用开发为中心,与开发团队平等协作,亲自参与模式发现、实验与提炼。
团队名称或组织图上的位置不能证明其有效;关键是其决策是否来自与应用团队的共同工作,而非与实际模型开发脱节。原书把它作为观察到的可行组织方式之一,并未规定所有项目必须采用。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第17章|Who Sets the Strategy? · 查看原书依据
When a strategy will be shared among several teams, some centralization of decision making does seem attractive. The failed model of the ivory tower architect is not the only possibility. An architecture team can act as a peer with various application teams, helping to coordinate and harmonize their large-scale structures as well as BOUNDED CONTEXT boundaries and other cross-team technical issues. To be useful in this, they must have a mind set that emphasizes application development. On an organization chart, this team may look just like the traditional architecture team, but it is actually different in every activity. Team members are true collaborators with development, discovering patterns along with the developers, experimenting with various teams to reach distillations, and getting their hands dirty.