4.流于形式的沟通 1.客户不会用C,难道就会用UML吗？ 48 2.项目文档真的可以用甲骨文来写 50 3. 最简沟通…53 4. 为不存在的角色留下沟通的渠道 …57 5.流于形式的沟通 60 5.失败的过程也是过程 1.做过程不是做工程… 63 2. 做过场 65 3.实现，才是目的… 65 4.过程不是死模型 66 5.“刻鹄类鹜”与“画虎类狗” 69 6.工程不是做的，是组织的 71 6.从编程到工程 1.语言只是工具… 73 2. 程序… 75 3. 方法 75 4. 过程 76 5. 工程 78 6. 组织 80 7. BOSS 82 8.上帝之手 844. 流于形式的沟通 1. 客户不会用 C，难道就会用 UML 吗？·············· 48 2. 项目文档真的可以用甲骨文来写 ······················· 50 3. 最简沟通 ··························································· 53 4. 为不存在的角色留下沟通的渠道 ······················· 57 5. 流于形式的沟通 ················································ 60 5. 失败的过程也是过程 1. 做过程不是做工程············································· 63 2. 做过场······························································· 65 3. 实现，才是目的 ················································ 65 4. 过程不是死模型 ················································ 66 5. “刻鹄类鹜”与“画虎类狗” ·························· 69 6. 工程不是做的，是组织的·································· 71 6. 从编程到工程 1. 语言只是工具 ···················································· 73 2. 程序 ·································································· 75 3. 方法 ·································································· 75 4. 过程 ·································································· 76 5. 工程 ·································································· 78 6. 组织 ·································································· 80 7. BOSS································································· 82 8. 上帝之手 ··························································· 84