• Like
  • Save
Programmer Anarchy (Chinese Mandarin)
Upcoming SlideShare
Loading in...5
×
 

Programmer Anarchy (Chinese Mandarin)

on

  • 830 views

 

Statistics

Views

Total Views
830
Views on SlideShare
830
Embed Views
0

Actions

Likes
2
Downloads
17
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Programmer Anarchy\nLondon, UK\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Performance\n
  • Why is Forward working?\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin Framework Cynefin框架\nFather is Dave Snowden\nPublished in Harvard Business Review, 2007\nA Leader's Framework for Decision Making 领导如何做决定\nEarly publishing starting in 2000 from work at IBM 2000年在IBM工作时开始发表\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Cynefin框架\nCause成因\nEffect有效\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\nDisorder无序\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Effective Organizations有效的组织\nSimple简单\nComplicated繁复\nComplex复杂\nChaotic混乱\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • Agile Manifesto敏捷宣言\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • XP Values极限编程的原则\nFeedback反馈\nCommunication沟通\nSimplicity简单\nCourage勇气\nRespect尊重\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Best Practices最佳敏捷实践\nNot Used没有被用到\nStand ups站立会议\nStory narratives用户故事\nRetrospectives敏捷回顾\nEstimates估算\nIterations迭代\nMandatory pairing强制结对\nUnit tests单元测试\nAcceptance tests验收测试\nRefactoring重构\nPatterns设计模式\nContinuous integration持续集成\n
  • Agile Impact敏捷的影响\nTrust between Customer and Developer 客户和开发之间的信任\n(Mutual) Trust 互信\n\n
  • Agile Impact敏捷的影响\nTrust between Customer and Developer 客户和开发之间的信任\n(Mutual) Trust 互信\n\n
  • Agile Impact敏捷的影响\nTrust between Customer and Developer 客户和开发之间的信任\n(Mutual) Trust 互信\n\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • waterfall瀑布式\nWHY?为什么?\nLarger systems更大的系统\nHigher expectations更高的期望\nVolatile commercial environments多变的商业环境\netc...等等\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Cultural Chasm (or translate "Cultural Gap")文化差异\nAgile敏捷\nLean精益\nKanban看板\nFrequency of interaction频繁迭代\nProcess impact流程影响\nFewer roles (& titles!)更少的角色\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • Role impact对角色的影响\nmanagement管理层\nproject manager项目经理\niteration manager迭代经理\nbusiness业务部门\ncustomer客户\nBA业务分析师\nQA测试\ndevelopment研发团队\narchitect架构师\nprogrammer程序员\nUI designer界面设计\nDBA DBA\ndeveloper开发\n
  • \n
  • \n
  • \n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Agile Roles Reduced Again敏捷角色的减少\nCustomer客户\nProject manager项目经理\nBusiness analyst业务分析师\nDeveloper开发\nQuality assurance / tester测试\nManager of programmers研发经理\n
  • Programmer Anarchy无政府主义的编程\nDeveloper-Driven Development工程师驱动开发\nOpen Source Business开源业务\nLean Startup Movement\n
  • Programmer Anarchy无政府主义的编程\nDeveloper-Driven Development工程师驱动开发\nOpen Source Business开源业务\nLean Startup Movement\n
  • Programmer Anarchy无政府主义的编程\nDeveloper-Driven Development工程师驱动开发\nOpen Source Business开源业务\nLean Startup Movement\n
  • Programmer Anarchy无政府主义的编程\nDeveloper-Driven Development工程师驱动开发\nOpen Source Business开源业务\nLean Startup Movement\n
  • Programmer Anarchy无政府主义的编程\nDeveloper-Driven Development工程师驱动开发\nOpen Source Business开源业务\nLean Startup Movement\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Why Anarachy为什么要无政府主义\nEMPOWERMENT权力模型\nSomebody ‚Äúgives‚Äù it某人会给\nSomebody can ‚Äútake it away‚Äù某人会拿走\nLeads to ‚ÄúCan I ... ?‚Äù我能么?\nANARCHY无政府主义\nNobody to ask没人问\nCan‚Äôt stop someone else不能限制别人\nDisagreements expected期待不同意见\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Matching Work and Devs开发和工作的结合\nStories用户故事\nProjects项目\nDevs开发\nWho?谁?\nStand Up站立会议\nResource Rumble噪音\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Story Tyranny用户故事的“暴政”\nAgile Side Effect敏捷副作用\nDevelopment driven by stories用户故事驱动开发\nStories small用户故事要小\nPriority set by customer客户安排优先级\nStory-level estimates and metrics故事级估算和统计\nProblem问题\nDevelopers become disconnected from business problem (Drones)开发与业务问题绝缘\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • Business Decisions Shift业务决定的转换\nanarchy无政府主义\nCustomer客户\nDeveloper开发\n
  • \n
  • \n
  • \n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Example: 例子\nEnergy Revolution 能源革命\nPrior system: 之前系统\n.NET with SQLServer .Net和SQLServer\nNew system: 新系统\nRuby, Clojure, C++\nMySQL, MongoDB\nHAML, SASS\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Ruby for energy calculation - big improvement!使用Ruby来做能源计算-巨大的改善\nRewrote in Clojure 用Clojure重写\nRewrote in Clojure (again) 再次用Clojure重写\n\nQuestion: 问题 \nWhat manager would let them to do it?管理者会让他们做这些事情么?\nHence: 从而得出\nNo manager!不需要管理者\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Example: 例子:\nClick Tracking 记录点击\nOld system: 老系统\nRuby-based, Ruby\n32 servers with 40% utilization 32个服务器,40%利用率\nNew system: 新系统\nNode.js, \n22 servers with 10% utilization 22个服务器,10%利用率\nand lower latency并且更低的延迟\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Cultural Enablers 文化的改变\nFear is the mind killer 恐惧是思考的杀手\nSound finances 赚钱\nLike risk 喜欢冒险\nDeveloper focused 开发工程师中心\nClarity of success 清晰的成功定义和展示\nRespected peers 互相尊重的队友\nDo or not do, 做或不做\nthere is no try 没有尝试\nExperimentation drives innovation 试验驱动创新\nIf you are not failing 没有尝试\nyou are not trying 没有失败,\nThe greatest barrier to success is the fear of failure 成功的最大障碍是恐惧失败\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Trust with collocation 合作中的信任\nResults, not blame 注重结果,不要埋怨\nSmall, short-lived applications 小的,短生命周期的应用\nContinuous deployment 持续部署\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Reality Check 现实检查\nDifferent extent of Anarchy by team 无政府状态的不同团队发展演绎\nTalent, experience, apprehension 才华,经验,悬念\nAnarchy exists in how Anarchy is implemented 无政府状态存在于不同的实现\nEven our best Anarchists ‚Äúask‚Äù on occasion 即时是最佳的无政府主义者也会偶尔提问\nCommercial success driving freedom 商业上的成功才能让你财务独立\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • Acknowledgements 致谢\nAnarchists 无政府主义者\nthe rest of the Search team 搜索团队\nEnablers 推动者\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Programmer Anarchy (Chinese Mandarin) Programmer Anarchy (Chinese Mandarin) Presentation Transcript

  • Fred GeorgeForward Internet Group fredgeorge@acm.org
  • Copyright © 2011 by Fred George. All rights reserverd. 2
  • 经历:Copyright © 2011 by Fred George. All rights reserverd. 2
  • 经历:Copyright © 2011 by Fred George. All rights reserverd. 2
  • Copyright © 2011 by Fred George. All rights reserved 3
  • 业Copyright © 2011 by Fred George. All rights reserved 3
  • 业Copyright © 2011 by Fred George. All rights reserved 3
  • 业 £3m £7m £13m £27m £55mCopyright © 2011 by Fred George. All rights reserved 3
  • 业 £3m £7m £13m £27m £55m £0.5m £0.7m £1.0m £3.9m £10.0mCopyright © 2011 by Fred George. All rights reserved 3
  • £100m 业 £3m £7m £13m £27m £55m £0.5m £0.7m £1.0m £3.9m £10.0m £15mCopyright © 2011 by Fred George. All rights reserved 3
  • Copyright © 2011 by Fred George. All rights reserverd. 4
  • 为 ForwardCopyright © 2011 by Fred George. All rights reserverd. 4
  • Copyright © 2011 by Fred George. All rights reserved 5
  • FrameworkCopyright © 2011 by Fred George. All rights reserved 5
  • Framework✦ Father is Dave Snowden✦ 2007 发 业评论 ✦ 领导✦ 2000 IBM 时 发Copyright © 2011 by Fred George. All rights reserved 5
  • Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • FrameworkCopyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • Framework 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • Framework  简单 Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • Framework 杂 ?  简单 ? ? Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • Framework 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 6
  • Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • 组织 杂 简单Copyright © 2011 by Fred George. All rights reserverd. Cynefin Framework by Dave Snowden 7
  • Copyright © 2011 by Fred George. All rights reserved 8
  • ✦ Individuals and interactions over processes and tools✦ Working software over comprehensive documentation✦ Customer collaboration over contract negotiation✦ Responding to change over following a planCopyright © 2011 by Fred George. All rights reserved 8
  • ✦ Individuals and interactions over processes and tools ✓✦ Working software over comprehensive documentation ✓✦ Customer collaboration over contract negotiation ✓✦ Responding to change over following a plan ✓Copyright © 2011 by Fred George. All rights reserved 8
  • Copyright © 2011 by Fred George. All rights reserved 9
  • 编 则✦ 馈✦沟✦ 简单✦✦Copyright © 2011 by Fred George. All rights reserved 9
  • 编 则✦ ✓ 馈✦沟 ✓✦ 简单 ✓✦ ✓✦ ✓Copyright © 2011 by Fred George. All rights reserved 9
  • Copyright © 2011 by Fred George. All rights reserved. 10
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试✦ 顾 ✦✦ ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 10
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试✦ 顾 ✦✦ ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 10
  • Copyright © 2011 by Fred George. All rights reserverd. 11
  • : 户 发 间Copyright © 2011 by Fred George. All rights reserverd. 11
  • Copyright © 2011 by Fred George. All rights reserved. 12
  • Copyright © 2011 by Fred George. All rights reserved. 12
  • 为 ✦ 统 ✦ ✦ 变 业环 ✦Copyright © 2011 by Fred George. All rights reserved. 12
  • Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 13
  • /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 13
  • SCRUM XP /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 13
  • /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 13
  • ✦ 频 ✦ ✦ /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 13
  • Copyright © 2011 by Fred George. All rights reserverd. 14
  • 对 层 Agile Roles 业务 发团队Copyright © 2011 by Fred George. All rights reserverd. 14
  • 对 项 经 经 层 Agile Roles 业务 发团队 户业务 员 师 测试 设计 DBA 师Copyright © 2011 by Fred George. All rights reserverd. 14
  • 对 项 经 经 层 Agile Roles 业务 发团队 户业务 测试 发 师Copyright © 2011 by Fred George. All rights reserverd. 14
  • Fortune 50 story /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 15
  • Fortune 50 story /Copyright © 2011 by Fred George. All rights reserved. Idea from Mark Durrand, uSwitch 15
  • Copyright © 2011 by Fred George. All rights reserved 16
  • ✦ 户✦项 经✦ 业务 师✦ 发✦ 测试Copyright © 2011 by Fred George. All rights reserved 16
  • ✦ 户 ✓✦项 经✦ 业务 师✦ 发 ✓✦ 测试Copyright © 2011 by Fred George. All rights reserved 16
  • ✦ 户 ✓✦项 经 X✦ 业务 师 X✦ 发 ✓✦ 测试 XCopyright © 2011 by Fred George. All rights reserved 16
  • ✦ 户 ✓✦项 经 X✦ 业务 师 X✦ 发 ✓✦ 测试 X✦ 发经 XCopyright © 2011 by Fred George. All rights reserved 16
  • Copyright © 2011 by Fred George. All rights reserved. 17
  • 师驱动 发Copyright © 2011 by Fred George. All rights reserved. 17
  • 师驱动 发 业务Copyright © 2011 by Fred George. All rights reserved. 17
  • 师驱动 发 义 编 业务Copyright © 2011 by Fred George. All rights reserved. 17
  • Copyright © 2011 by Fred George. All rights reserved. 18
  • 为 义?Copyright © 2011 by Fred George. All rights reserved. 18
  • 为 义?✦ ✦ 给 ✦ ✦Copyright © 2011 by Fred George. All rights reserved. 18
  • 为 义?✦ ✦ 义 ✦ 给 ✦ 问 ✦ ✦ ✦ ✦ 见Copyright © 2011 by Fred George. All rights reserved. 18
  • Copyright © 2011 by Fred George. All rights reserverd. 19
  • 发 结 户 发Copyright © 2011 by Fred George. All rights reserverd. 19
  • 发 结 户 发 议Copyright © 2011 by Fred George. All rights reserverd. 19
  • 发 结 项 发 “ ”Copyright © 2011 by Fred George. All rights reserverd. 19
  • 发 结 项 发 谁 “ ”Copyright © 2011 by Fred George. All rights reserverd. 19
  • Copyright © 2011 by Fred George. All rights reserved 20
  • : 户 “ ”Copyright © 2011 by Fred George. All rights reserved 20
  • : 户 “ ”✦ 户 驱动 发✦ 户✦ 户 级✦ 级 统计Copyright © 2011 by Fred George. All rights reserved 20
  • : 户 “ ”✦ 户 驱动 发✦ 户✦ 户 级✦ 级 统计 问题: 发 业务问题绝缘Copyright © 2011 by Fred George. All rights reserved 20
  • Copyright © 2011 by Fred George. All rights reserverd. 21
  • 业务 转换 / 义Copyright © 2011 by Fred George. All rights reserverd. 21
  • 业务 转换 户 发 / 义Copyright © 2011 by Fred George. All rights reserverd. 21
  • 业务 转换 户 发 户 发 / 义Copyright © 2011 by Fred George. All rights reserverd. 21
  • 业务 转换 户 发 户 发 户 发 / 义Copyright © 2011 by Fred George. All rights reserverd. 21
  • Copyright © 2011 by Fred George. All rights reserverd. 22
  • forwardtechnology.co.uk 7 40 1076Copyright © 2011 by Fred George. All rights reserverd. 86 577 22
  • Copyright © 2011 by Fred George. All rights reserved 23
  • :Copyright © 2011 by Fred George. All rights reserved 23
  • :✦ 统 ✦ .Net SQLServerCopyright © 2011 by Fred George. All rights reserved 23
  • :✦ 统 ✦ .Net SQLServer✦ 统 ✦ Ruby, Clojure, C++ ✦ MySQL, MongoDB ✦ HAML, SASSCopyright © 2011 by Fred George. All rights reserved 23
  • Copyright © 2011 by Fred George. All rights reserved 24
  • :Copyright © 2011 by Fred George. All rights reserved 24
  • :✦ Ruby 计Copyright © 2011 by Fred George. All rights reserved 24
  • :✦ Ruby 计✦ ClojureCopyright © 2011 by Fred George. All rights reserved 24
  • :✦ Ruby 计✦ Clojure✦ ClojureCopyright © 2011 by Fred George. All rights reserved 24
  • :✦ Ruby 计✦ Clojure✦ Clojure 问题: 让 们 这Copyright © 2011 by Fred George. All rights reserved 24
  • :✦ Ruby 计✦ Clojure✦ Clojure 问题: 让 们 这 :Copyright © 2011 by Fred George. All rights reserved 24
  • Copyright © 2011 by Fred George. All rights reserved 25
  • : 记录 击Copyright © 2011 by Fred George. All rights reserved 25
  • : 记录 击✦ 统 ✦ Ruby, 32 务 40%Copyright © 2011 by Fred George. All rights reserved 25
  • : 记录 击✦ 统 ✦ Ruby, 32 务 40%✦ 统: ✦ Node.js, 22 务 10% , 迟Copyright © 2011 by Fred George. All rights reserved 25
  • Copyright © 2011 by Fred George. All rights reserved. 26
  • 变Copyright © 2011 by Fred George. All rights reserved. 26
  • 变 杀Copyright © 2011 by Fred George. All rights reserved. 26
  • 变 赚钱 欢 险Copyright © 2011 by Fred George. All rights reserved. 26
  • 变 赚钱 欢 险 发 师 义 队Copyright © 2011 by Fred George. All rights reserved. 26
  • 变 , 赚钱 尝试 欢 险 试验驱动创 尝试, 发 师 败 义 队Copyright © 2011 by Fred George. All rights reserved. 26
  • 变 , 赚钱 尝试 欢 险 试验驱动创 尝试, 发 师 败 义 队 败Copyright © 2011 by Fred George. All rights reserved. 26
  • Copyright © 2011 by Fred George. All rights reserved. 27
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试✦ 顾 ✦✦ ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 27
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试✦ 顾 ✦✦ ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 27
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试✦ 顾 ✦✦ 结 ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 27
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试 ,✦ 顾 ✦ 应✦ 结 ✦ 设计✦ ✦ 续✦ 结对Copyright © 2011 by Fred George. All rights reserved. 27
  • 实✦ 议 ✦单 测试✦ 户 ✦验 测试 ,✦ 顾 ✦ 应✦ 结 ✦ 设计✦ ✦ 续✦ 结对 续Copyright © 2011 by Fred George. All rights reserved. 27
  • Copyright © 2011 by Fred George. All rights reserved 28
  • 现实检Copyright © 2011 by Fred George. All rights reserved 28
  • 现实检✦ 态 团队发 绎 ✦ 华 经验 悬 ✦ 态 实现✦ 时 义 问✦ 业 让 财务Copyright © 2011 by Fred George. All rights reserved 28
  • Copyright © 2011 by Fred George. All rights reserved 29
  • 谢Copyright © 2011 by Fred George. All rights reserved 29
  • 谢✦ 义 ✦ Andy Kent ✦ Paul Ingles ✦ Mike Jones ✦ 团队Copyright © 2011 by Fred George. All rights reserved 29
  • 谢✦ 义 ✦ Andy Kent ✦ Paul Ingles ✦ Mike Jones ✦ 团队✦ 动 ✦ Carl Gaywood and Neil HutchinsonCopyright © 2011 by Fred George. All rights reserved 29
  • Copyright © 2011 by Fred George. All rights reserved. 30
  • PROGRAMMER ANARCHYCopyright © 2011 by Fred George. All rights reserved. 30
  • Copyright © 2011 by Fred George. All rights reserved. 30