Agile Tour ——西安Develop        Release  Iterate        Learn
乔梁百度项目管理部 ,高级架构师InfoQ 敏捷社区, 特约编辑           《持续集成》专栏作者
me     中文站:www.continuousdelivery.info
Agenda Business Driven & Capability Principle & Practice
 88%的CEO认为,企业敏捷是成功的关键因素。 其中,一半以上的人认为,敏捷不只是重要,而  且是核心竞争力。 Source: The Economist, Special Report on Agility. March 2009
进一步提高业务响应能力的主要障碍是: – 冗长的决策过程 – 部门目标与优先级之间的冲突 – 避免承担风险的文化 – 以及“筒仓式”的信息孤岛     Economist Intelligence Unit:”Organizational ag...
code.flickr.com                  http://code.flickr.com
How about others?
Team size: 50Cycle time: 15minFrequency : 50 times
Large Organizations
Why?
Develop          Release          Pray for          customer
Develop     Release  Iterate    Learn
Learn Faster                                     Build Faster               Measure Faster   Measure Faster
constant flow of new features into productionincremental release of small changes
Benefit?
Build the right thing                                    ProblemEvery business idea isa hypothesis until you              ...
reliability & stability Reduce risk of release
real progress DONE means release                                        scope                                        dev ...
Continuous Delivery is great, butTaking the plunge is scary as hell
How
Continuous Deliveryalways write production-ready codeminimize the lead time from idea to live
Another Story
Context     a complex softwareecosystem
Context一个复杂的软件生态系统
Context 7+ Modules 10 years c/c++ legacy code Few automation tests for a single Module Deploy on 170+ boxes 7 Devs + ...
6 months ago three months big-bang release lots of hot-fix and argent requests
now three weeks release few hot-fix
Actions
Deployment Pipeline    Module levelA   Compile   quick                        Subsystem   System    Staging   ProductionB ...
Small batch
Single branch
Automation testing
Automation deployment
One-click release
Everything is code
Reality simulating
Pipeline monitoring
Stop the line
How about big features
Feature toggle
Branching by abstraction
How about“Deployment Down Time”
Canary release
Canary release
Blue-green deployment
Blue-green deployment
Database migration
How about“performance-issued Featrue”
Dark launchingDark launching
It is not impossible,   but it is difficult
What you can doAutomation   Practice       PeopleAutomation   Practice       PeopleAutomation   Practice       People
What would you get
What would you get
What would you get
微博: http://weibo.com/Tony1130博客: http://blog.csdn.net/Tony1130邮件: qiaoliang.email@gmail.com中文站:www.continuousdelivery.info
Discovery delivery agiletour-xian
Discovery delivery agiletour-xian
Discovery delivery agiletour-xian
Upcoming SlideShare
Loading in …5
×

Discovery delivery agiletour-xian

1,464 views
1,388 views

Published on

敏捷之旅——西安站演讲PPT

Published in: Technology, Sports
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,464
On SlideShare
0
From Embeds
0
Number of Embeds
626
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Discovery delivery agiletour-xian

  1. 1. Agile Tour ——西安Develop Release Iterate Learn
  2. 2. 乔梁百度项目管理部 ,高级架构师InfoQ 敏捷社区, 特约编辑 《持续集成》专栏作者
  3. 3. me 中文站:www.continuousdelivery.info
  4. 4. Agenda Business Driven & Capability Principle & Practice
  5. 5.  88%的CEO认为,企业敏捷是成功的关键因素。 其中,一半以上的人认为,敏捷不只是重要,而 且是核心竞争力。 Source: The Economist, Special Report on Agility. March 2009
  6. 6. 进一步提高业务响应能力的主要障碍是: – 冗长的决策过程 – 部门目标与优先级之间的冲突 – 避免承担风险的文化 – 以及“筒仓式”的信息孤岛 Economist Intelligence Unit:”Organizational agility: How business can survive and thrive in turbulent times”
  7. 7. code.flickr.com http://code.flickr.com
  8. 8. How about others?
  9. 9. Team size: 50Cycle time: 15minFrequency : 50 times
  10. 10. Large Organizations
  11. 11. Why?
  12. 12. Develop Release Pray for customer
  13. 13. Develop Release Iterate Learn
  14. 14. Learn Faster Build Faster Measure Faster Measure Faster
  15. 15. constant flow of new features into productionincremental release of small changes
  16. 16. Benefit?
  17. 17. Build the right thing ProblemEvery business idea isa hypothesis until you Hypothesisget feedback. Idea #1 Idea #3 Idea #2
  18. 18. reliability & stability Reduce risk of release
  19. 19. real progress DONE means release scope dev test released A B
  20. 20. Continuous Delivery is great, butTaking the plunge is scary as hell
  21. 21. How
  22. 22. Continuous Deliveryalways write production-ready codeminimize the lead time from idea to live
  23. 23. Another Story
  24. 24. Context a complex softwareecosystem
  25. 25. Context一个复杂的软件生态系统
  26. 26. Context 7+ Modules 10 years c/c++ legacy code Few automation tests for a single Module Deploy on 170+ boxes 7 Devs + 2 QAs
  27. 27. 6 months ago three months big-bang release lots of hot-fix and argent requests
  28. 28. now three weeks release few hot-fix
  29. 29. Actions
  30. 30. Deployment Pipeline Module levelA Compile quick Subsystem System Staging ProductionB Compile quick quick quick slow ……………E Compile quick
  31. 31. Small batch
  32. 32. Single branch
  33. 33. Automation testing
  34. 34. Automation deployment
  35. 35. One-click release
  36. 36. Everything is code
  37. 37. Reality simulating
  38. 38. Pipeline monitoring
  39. 39. Stop the line
  40. 40. How about big features
  41. 41. Feature toggle
  42. 42. Branching by abstraction
  43. 43. How about“Deployment Down Time”
  44. 44. Canary release
  45. 45. Canary release
  46. 46. Blue-green deployment
  47. 47. Blue-green deployment
  48. 48. Database migration
  49. 49. How about“performance-issued Featrue”
  50. 50. Dark launchingDark launching
  51. 51. It is not impossible, but it is difficult
  52. 52. What you can doAutomation Practice PeopleAutomation Practice PeopleAutomation Practice People
  53. 53. What would you get
  54. 54. What would you get
  55. 55. What would you get
  56. 56. 微博: http://weibo.com/Tony1130博客: http://blog.csdn.net/Tony1130邮件: qiaoliang.email@gmail.com中文站:www.continuousdelivery.info

×