知识卡片

普通读书笔记卡 · 1971.o.1.b.1.a.2.e

应用团队可在协作中形成跨团队战略

理解等级:高级

一种战略形成方式是让善于沟通且自律的应用团队,在开发中逐步发现共同结构,而非由更高权力的架构团队在应用开发前单向制定。实践中可由仍参与开发的人照看整体结构、协调讨论,但不独占创意。

多个团队共用结构时,可由代表组成非正式协作小组,评估提案后采纳、修改或暂缓。原书限定其较适合团队数量不多、愿意协调、设计能力相近且结构需求相容的情形。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 原书第17章|Who Sets the Strategy? · 查看原书依据

      This arrangement can work when there are relatively few teams, when they are all committed to coordinating with each other, when their design capabilities are comparable, and when their structural needs are similar enough to be met by a single large-scale structure.

    参考来源

    - 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第139章《Who Sets the Strategy?》(源文件:_epub-src/0321125215_ch17lev1sec4.html;单元01) - 结论依据:原文介绍应用团队自发形成结构、开发者中的协调者以及跨团队非正式小组的适用条件。 - 原始内容:Traditionally, architecture is handed down, created before application development begins, by a team that has more power in the organization than the application development team. But it doesn't have to be that way. That way doesn't usually work very well. [...] When a large-scale structure spans multiple teams, closely affiliated teams may begin to collaborate informally. In such a situation, each application team still makes the discoveries that lead to the idea for a large-scale structure, but then particular options are discussed by the informal committee, made up of representatives of the various teams. After assessing the impact of the design, participants may decide to adopt it, modify it, or leave it on the table. The teams attempt to move together in this loose affiliation. This arrangement can work when there are relatively few teams, when they are all committed to coordinating with each other, when their design capabilities are comparable, and when their structural needs are similar enough to be met by a single large-scale structure. - 转录说明:`[...]` 标明本节中非连续段落的省略;另一个涉及开发者兼任协调者的段落含 EPUB 异常破折号字节,此处未转录。