知识卡片
效率须朝向组织目标
团队可以技术上同向、交付很快,却离组织目标更远。架构有效性还包括运行成本、风险、可持续演进及实际用户价值。共享方向要说明组织在乎什么,才能判断某技术优化是否值得;局部吞吐增加不能单独证明整体进展。
这张卡片看不懂?
这张卡片已通过人工审查,不再接受失败反馈。
已有反馈 · 0 条
还没有人提交反馈。
在整书笔记中的位置
原书出处 · 1 处
- Testable CFRs and Technology Strategy · 查看原书依据
Effectiveness is when your software systems deliver impact for your organization. This impact isn’t simply the result of implementing the software features your organization asked for. Effectiveness is also deploying technology appropriately, realizing the value and benefits those features are intended to unlock, or failing fast when you learn that the value/benefit isn’t there. Effectiveness
参考来源
- 位置:《Facilitating Software Architecture》第09章《Testable CFRs and Technology Strategy》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch09.html)
- 结论依据:原文用同向划船却未向终点比喻,并列举impact、debt、cost、risk及用户需要。
- 原始内容:Effectiveness is when your software systems deliver impact for your organization. This impact isn’t simply the result of implementing the software features your organization asked for. Effectiveness is also deploying technology appropriately, realizing the value and benefits those features are intended to unlock, or failing fast when you learn that the value/benefit isn’t there. Effectiveness