知识卡片

普通读书笔记卡 · 1841.h.3.c.1.a.2

团队设计考虑认知负荷

理解等级:高级

按业务能力组队还需考虑领域规则和技术复杂度的总认知负荷。一个团队承担过多支付方案或复杂子系统时,端到端责任可能超出能力。可用流对齐、赋能、复杂子系统和平台团队分担负担,同时保留清晰协作接口。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Putting Evolutionary Architecture into Practice · 查看原书依据

      In their model, using stream-aligned teams maps to our recommendation of aligning teams around “Business Capabilities” with a small caveat: team design must also account for cognitive load. A team with an excessive cognitive load, either from a complex domain area or from a complex set of technologies, will struggle to deliver. As an example, if you have ever worked with processing payments, there is

    参考来源

    - 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第09章《Putting Evolutionary Architecture into Practice》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch09.html;段落定位:team design must also account for cognitive load) - 结论依据:原文对“团队设计考虑认知负荷”的定义或案例,支撑“按业务能力组队还需考虑领域规则和技术复杂度的总认知负荷”的归纳。据其上下文,一个团队承担过多支付方案或复杂子系统时,端到端责任可能超出能力。 - 原始内容:In their model, using stream-aligned teams maps to our recommendation of aligning teams around “Business Capabilities” with a small caveat: team design must also account for cognitive load. A team with an excessive cognitive load, either from a complex domain area or from a complex set of technologies, will struggle to deliver. As an example, if you have ever worked with processing payments, there is