知识卡片

普通读书笔记卡 · 4918.b.2.a.1.d

拆分后分别维护必要元素

理解等级:中级

各气泡有自己的论坛,时间避免冲突以便共享专家参加;ADR按叙事是否重叠决定共库或分库,历史不重写且仍可访问。原则先共用再按实际反馈演进,技术雷达保持全组织共享,CFR按组织或产品适用范围保留。不同元素不必一刀切全拆或全统一。

这张卡片看不懂?

已有反馈 · 0 / 10 条

    还没有人提交反馈。

    在整书笔记中的位置

    原书出处 · 1 处

    • Fitting the Advice Process Within Your Organization · 查看原书依据

      Each bubble should have its own forum time slot, invitees, and agenda. Each bubble’s forum should be convened by parties within that bubble. Care should be taken not to overlap their scheduling because some nonbubble advisers, at least those playing “expert” roles like InfoSec, will want to attend them all. Dividing ADRs When a new

    参考来源

    - 位置:《Facilitating Software Architecture》第17章《Fitting the Advice Process Within Your Organization》(来源项目 /Users/wangyi/claudecodeProject/bookBase/book-sources;源文件:extracted/Facilitating Software Architecture/_epub-src/OEBPS/ch17.html) - 结论依据:原文分别讨论forum/ADRs/principles/radar与跨泡CFR对齐。 - 原始内容:Each bubble should have its own forum time slot, invitees, and agenda. Each bubble’s forum should be convened by parties within that bubble. Care should be taken not to overlap their scheduling because some nonbubble advisers, at least those playing “expert” roles like InfoSec, will want to attend them all. Dividing ADRs When a new