知识卡片

普通读书笔记卡 · 3401.a.1.b.1

团队交接增加等待风险

理解等级:中级

软件与基础设施分属两个实例管理团队时,一个涉及双方的变更会多次交接,每次都可能等待、误解或返工。简单系统可用全栈团队共同负责工作负载和基础设施,减少跨队依赖;系统扩大后,则需通过服务化边界等方式管理交接。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • 核心基础设施交付工作流 · 查看原书依据

      This value stream shows quite a few handoffs between the software and infrastructure teams. Each of these handoffs is an opportunity for delay, waiting for someone in the other team to become available. It’s also an opportunity for a failure and rework. For example, the software team may discover that its software fails to deploy

    参考来源

    - 位置:《Infrastructure As Code》第14章《核心基础设施交付工作流》(来源项目:book-sources;源文件:extracted/Infrastructure As Code/_epub-src/OEBPS/ch14.html) - 结论依据:原文说明软件与基础设施分属两个实例管理团队时,一个涉及双方的变更会多次交接,每次都可能等待、误解或返工;本卡据此解释其用途及适用边界。 - 原始内容:This value stream shows quite a few handoffs between the software and infrastructure teams. Each of these handoffs is an opportunity for delay, waiting for someone in the other team to become available. It’s also an opportunity for a failure and rework. For example, the software team may discover that its software fails to deploy