知识卡片
周期时间限制反馈速度
本书周期时间从开发者开始工作计到功能进入生产,与包含排期等活动的前置时间区分。周期越短,可获得反馈和尝试新一代的频率越高;原书写v∝c与其文字方向矛盾,不应照录。可用周期阈值触发对验证成本和发布流程的重新权衡。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Evolutionary Architecture Pitfalls and Antipatterns · 查看原书依据
Cycle time is therefore a critical metric in evolutionary architecture projects—faster cycle time implies a faster ability to evolve. In fact, cycle time is an excellent candidate for an atomic, process-based fitness function. For example, developers set up a project with a deployment pipeline with automation, achieving a cycle time of three hours. Over time, the cycle time gradually increases as developers add more verifications
参考来源
- 位置:《Building Evolutionary Architectures Automated Software Governance, 2nd Edition》第08章《Evolutionary Architecture Pitfalls and Antipatterns》(来源项目:a19c7933-4eda-4176-aebd-30fe7e1ad292;源文件:extracted/Building Evolutionary Architectures Automated Software Governance, 2nd Edition/_epub-src/OEBPS/ch08.html;段落定位:Cycle time is therefore a critical metric)
- 结论依据:原文对“周期时间限制反馈速度”的定义或案例,支撑“本书周期时间从开发者开始工作计到功能进入生产,与包含排期等活动的前置时间区分”的归纳。据其上下文,周期越短,可获得反馈和尝试新一代的频率越高;原书写v∝c与其文字方向矛盾,不应照录。
- 原始内容:Cycle time is therefore a critical metric in evolutionary architecture projects—faster cycle time implies a faster ability to evolve. In fact, cycle time is an excellent candidate for an atomic, process-based fitness function. For example, developers set up a project with a deployment pipeline with automation, achieving a cycle time of three hours. Over time, the cycle time gradually increases as developers add more verifications