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

1. Agile Tour ——西安
Develop Release
Iterate Learn

2. 乔梁
百度项目管理部 ，高级架构师
InfoQ 敏捷社区， 特约编辑
《持续集成》专栏作者

3. me
中文站：www.continuousdelivery.info

4. Agenda
 Business Driven & Capability
 Principle & Practice

5.  88％的CEO认为，企业敏捷是成功的关键因素。
 其中，一半以上的人认为，敏捷不只是重要，而
且是核心竞争力。
Source: The Economist, Special Report on Agility. March 2009

6. 进一步提高业务响应能力的主要障碍是：
– 冗长的决策过程
– 部门目标与优先级之间的冲突
– 避免承担风险的文化
– 以及“筒仓式”的信息孤岛
Economist Intelligence Unit：”Organizational agility:
How business can survive and thrive in turbulent times”

7. code.flickr.com
http://code.flickr.com

8. How about others?

9. Team size: 50
Cycle time: 15min
Frequency : 50 times

12. Large Organizations

13. Why?

14. Develop
Release
Pray for
customer

15. Develop Release
Iterate Learn

16. Learn Faster Build Faster
Measure Faster Measure Faster

17. constant flow of new features into production
incremental release of small changes

18. Benefit?

19. Build the right thing
Problem
Every business idea is
a hypothesis until you
Hypothesis
get feedback.
Idea #1 Idea #3
Idea #2

20. reliability & stability
 Reduce risk of release

21. real progress
 DONE means release
scope
dev
test
released
A
B

22. Continuous Delivery is great, but
Taking the plunge is scary as hell

23. How

24. Continuous Delivery
always write production-ready code
minimize the lead time from idea to live

25. Another Story

26. Context
a
complex
software
ecosystem

27. Context
一个复杂的软件生态系统

28. Context
 7+ Modules
 10 years c/c++ legacy code
 Few automation tests for a single Module
 Deploy on 170+ boxes
 7 Devs + 2 QAs

29. 6 months ago
 three months big-bang release
 lots of hot-fix and argent requests

30. now
 three weeks release
 few hot-fix

31. Actions

32. Deployment Pipeline
Module level
A Compile quick
Subsystem System Staging Production
B Compile quick
quick quick slow
……………
E Compile quick

33. Small batch

34. Single branch

35. Automation testing

37. Automation deployment

38. One-click release

39. Everything is code

40. Reality simulating

41. Pipeline monitoring

42. Stop the line

43. How about big features

44. Feature toggle

45. Branching by abstraction

46. How about
“Deployment Down Time”

47. Canary release

48. Canary release

49. Blue-green deployment

50. Blue-green deployment

51. Database migration

52. How about
“performance-issued Featrue”

53. Dark launching
Dark launching

54. It is not impossible,
but it is difficult

55. What you can do
Automation Practice People
Automation Practice People
Automation Practice People

56. What would you get

57. What would you get

58. What would you get

59. 微博: http://weibo.com/Tony1130
博客: http://blog.csdn.net/Tony1130
邮件: qiaoliang.email@gmail.com
中文站：www.continuousdelivery.info