知识卡片
团队轴看全程责任
团队轴比较个人协作、专业分工、跨功能团队与构建运行一体责任。服务团队覆盖设计、测试、发布和支持,平台能力可集中复用。要观察真实交接和决策权,不能只将Ops成员放进开发组就认定责任已闭环。
这张卡片看不懂?
这张卡片的反馈已满 10 条,暂时无法继续提交。
已有反馈 · 0 / 10 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Chapter 5. Knowing Thyself: The Cloud Native Maturity Matrix Tool · 查看原书依据
Traditionally, developers/engineers have been responsible for building software and then handing it off to the operations team for deployment. A DevOps team joins the two in a single team capable of designing and building applications as part of a distributed system, and also operating the production platform/tools. Across the organization, each team has full responsibility for delivering an individual set of microservices and supporting them. DevOps teams typically include planning,
参考来源
- 位置:《Cloud Native Transformation》第05章《Knowing Thyself: The Cloud Native Maturity Matrix Tool》(来源项目a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Cloud Native Transformation/_epub-src/OEBPS/ch05.xhtml)
- 结论依据:原文对本卡对象的定义、区别或前后条件给出直接解释,支持本卡的核心论点:团队轴比较个人协作、专业分工、跨功能团队与构建运行一体责任。本卡进一步说明用途及适用边界;原文过强的保证另在正文限界。
- 原始内容:Traditionally, developers/engineers have been responsible for building software and then handing it off to the operations team for deployment. A DevOps team joins the two in a single team capable of designing and building applications as part of a distributed system, and also operating the production platform/tools. Across the organization, each team has full responsibility for delivering an individual set of microservices and supporting them. DevOps teams typically include planning,