Cycle time is the key to minimizing the total time it takes to develop, release, and learn from software. Shortening cycle times allows teams to build the right thing faster through continuous delivery, deployment, and learning from frequent customer feedback. This requires changing development practices and organizational structures to enable small batch sizes, automation, and rapid feedback loops.

1. ——Cycle time is the key
乔梁@百度.项目管理部

2. 乔梁
百度项目管理部 ，高级架构师
InfoQ 敏捷社区， 特约编辑
《持续集成》专栏作者
CruiseControl的贡献者
持续集成与发布管理工具Go 的项目经理
2011年Jolt Excellence Award
中文站：www.continuousdelivery.info

3. Agenda
Delivery & Discovery Cycle
Structure Changes
 Principle and Practice

4. Develop Release
How long? for
Pray
customer

5. Organization Structure
Business Engineering Quality Assurance Operations
Dev BUG!!! Script!
I got an
complete!!! #@!$%#@ Installation!
idea!!!
Monitoring!
Value Stream

6. continuous integration
6
Check-in Dance 1 4
5
2 4’
3
Team work

7. devops
Agile101
Continuous
Integration
Value Stream

8. Delivery
Develop Release
How long?
Iterate Learn
Discovery

9. code.flickr.com
http://code.flickr.com

10. How about others?

11. An Avatar-Based Social Network and 3D Virtual World

14. What is in the cycle?
Delivery
Develop Release
Iterate Learn
Discovery

15. Minimize total time through loop
Learn Faster Build Faster
Split Tests Unit Tests
Customer Interviews Usability Tests
Customer Development Continuous Integration
Five Whys Root Cause Incremental Deployment
Analysis Free & Open-Source
Customer Advisory Board Components
Falsifiable Hypotheses Cloud Computing
Product Owner Cluster Immune System
Accountability Measure Faster Measure Faster Just-in-time Scalability
Customer Archetypes Refactoring
Split Tests Funnel Analysis
Cross-functional Teams Developer Sandbox
Clear Product Owner Cohort Analysis
Semi-autonomous Teams Minimum Viable Product
Continuous Deployment Net Promoter Score
Smoke Tests
Usability Tests Search Engine Marketing
Real-time Monitoring Real-Time Alerting
Customer Liaison Predictive Monitoring
From 《Lean Startup》, Eric Ries

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

17. Why

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

19. reliability & stability
 Reduce risk of release

20. How

21. Continuous Delivery
always write production-ready code
Everyone collaborate throughout lifecycle
Faster feedback loops
Lower-risk, more reliable releases

22. It might change the structure

23. devops
Agile101
Continuous
Integration
Value Stream

24. service-oriented business model
Treat these service as products
products/services
IaaS

25. service-oriented business model
products/services
IaaS
service desk

26. Therefore
Teams can measure cost and value delivered per
product
Teams can rationally determine what to prioritize their
product backlog
Teams can self-manage using the lean startup
methodology
Architecture group responsible for regulating and
monitoring system-level attributes

27. Organizational change
 Product Team
 Architecture group
 Operations
 Business

28. Is it enough?

29. Is it enough?
Maybe … …

30. Small batch

31. Single branch

32. Automation testing

33. Automation deployment

34. One-click release

35. Everything is code

36. Reality simulating

37. Pipeline monitoring

38. Stop the line

39. How about big features

40. Feature toggle

41. Branching by abstraction

42. How about
“Deployment Time”

43. Canary release

44. Canary release

45. Blue-green deployment

46. Blue-green deployment

47. Database migration

48. Dark launching

49. It is not impossible,
but it is difficult

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

51. What would you get

52. What would you get

53. What would you get

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