知识卡片

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

跨职能减少等待

理解等级:中级

跨职能团队具备设计、实现、测试和运营产品所需的角色,让常见问题获得本地反馈。它不保证每个团队都配满专职专家,稀缺技能可以在多个团队间共享。目标是消除无必要的排队和责任转移,而非取消专业能力。

这张卡片看不懂?

已有反馈 · 0 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

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

      Domain-centric teams tend to be cross-functional, meaning every product role is covered by someone on the team. The goal of a domain-centric team is to eliminate operational friction. In other words, the team has all the roles needed to design, implement, and deploy their service, including traditionally separate roles like operations. But these roles must change to accommodate this new structure, which includes the following

    参考来源

    - 位置:《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;段落定位:The goal of a domain-centric team is to eliminate) - 结论依据:原文对“跨职能减少等待”的定义或案例,支撑“跨职能团队具备设计、实现、测试和运营产品所需的角色,让常见问题获得本地反馈”的归纳。据其上下文,它不保证每个团队都配满专职专家,稀缺技能可以在多个团队间共享。 - 原始内容:Domain-centric teams tend to be cross-functional, meaning every product role is covered by someone on the team. The goal of a domain-centric team is to eliminate operational friction. In other words, the team has all the roles needed to design, implement, and deploy their service, including traditionally separate roles like operations. But these roles must change to accommodate this new structure, which includes the following