知识卡片
架构团队不能抽走应用团队的设计与领域能力
若最强设计者都转入架构或基础设施团队,应用团队可能缺少把战略落实到模型和代码的能力;若战略团队又缺少最懂领域的开发者与领域专家,方案也会失去业务判断。
原书因此要求每个应用团队有强设计者,制定战略的团队具备领域知识,并让有效的战略团队与有效的应用团队配对。兼职架构团队或增聘设计者是作者提出的可能办法,并非固定组织模板。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- 原书第17章|Six Essentials for Strategic Design Decision Making · 查看原书依据
It is essential to have strong designers on all application teams. It is essential to have domain knowledge on any team attempting strategic design. It may simply be necessary to hire more advanced designers. It may help to keep architecture teams part-time. I'm sure there are many ways that work, but any effective strategy team has to have as a partner an effective application team.
参考来源
- 位置:《Domain-Driven Design: Tackling Complexity in the Heart of Software》第140章《Six Essentials for Strategic Design Decision Making》(源文件:_epub-src/0321125215_ch17lev1sec5.html)
- 结论依据:六项要点之四:原文分析能力抽离与领域经验缺失的双重问题,给出团队能力配置要求。
- 原始内容:It is essential to have strong designers on all application teams. It is essential to have domain knowledge on any team attempting strategic design. It may simply be necessary to hire more advanced designers. It may help to keep architecture teams part-time. I'm sure there are many ways that work, but any effective strategy team has to have as a partner an effective application team.