From 248 to 98 then 1

Transcription

1 From 248 to 98 then 1 Our pivot to continuous delivery Jean-Michel Lemieux Atlassian 1

2

3 14.91s

4 Why now?

5 "Continuous delivery is not a cowboy show. It puts you in charge of your production environment. The business can pick and choose what and when to deploy. If you think you ve nailed agile development, but aren t considering how to achieve continuous delivery, you really haven t even started." - ThoughtWorks Tech Radar.

6 Training Plan v1

7 248 to 98

8 248 to 98 Goal: shorten our release cycles

9 248 to 98 Goal: shorten our release cycles Success: better efficiency, better releases, roughly 90 days.

10 248 to 98 Goal: shorten our release cycles Success: better efficiency, better releases, roughly 90 days. Failure: crap releases, shipped on time no features, or no shortening of time. api/ integration madness.

11 Baseline JIRA Bitbucket GreenHopper Confluence Studio FE/CRU Bamboo Crowd 248 days 30 days 34 days 185 days 72 days 192 days 142 days 149 days

12 Recap

13 Training Plan v2

14 98 to 1

15 98 to 1 Goal: allow products to independently release to hosted (eg, production) every day

16 98 to 1 Goal: allow products to independently release to hosted (eg, production) every day Success: better efficiency, faster learning, happier/more customers.

17 98 to 1 Goal: allow products to independently release to hosted (eg, production) every day Success: better efficiency, faster learning, happier/more customers. Failure: crap releases, api/integration madness, slowing down because of too many balls in the air.

18 Approach

19 Approach Look at the entire system

20 Approach Look at the entire system If it s hard, do it more often

21 Approach Look at the entire system If it s hard, do it more often Measure and remove the waste everywhere

22 Approach Look at the entire system If it s hard, do it more often Measure and remove the waste everywhere OnSite

23 Approach Look at the entire system If it s hard, do it more often Measure and remove the waste everywhere OnDemand OnSite

24 Approach Look at the entire system If it s hard, do it more often Measure and remove the waste everywhere OnDemand Analytics / Monitoring Customer Feedback OnSite

25 System Breakdown Product Architecture Culture/Process Pipeline Analytics / Monitoring OnDemand Customer Feedback OnSite

26 System Breakdown Pipeline OnDemand Analytics / Monitoring Customer Feedback OnSite

27 System Breakdown The hosting platform (eg, production). Pipeline OnDemand Analytics / Monitoring Customer Feedback OnSite

28 System Breakdown The hosting platform (eg, production). Tools and processes to move products through to production. Pipeline OnDemand Analytics / Monitoring Customer Feedback OnSite

29 System Breakdown The hosting platform (eg, production). Tools and processes to move products through to production. Tools to monitor deployed products. Pipeline OnDemand Analytics / Monitoring Customer Feedback OnSite

30 System Breakdown The hosting platform (eg, production). Tools and processes to move products through to production. Tools to monitor deployed products. Tools to stage, test, and ensure we don t fuck the customer. Pipeline OnDemand Analytics / Monitoring Customer Feedback OnSite

31 System Breakdown Culture/Process OnDemand Analytics / Monitoring Customer Feedback OnSite

32 System Breakdown Culture/Process Development principles OnDemand Analytics / Monitoring Customer Feedback OnSite

33 System Breakdown Culture/Process Development principles Team structures OnDemand Analytics / Monitoring Customer Feedback OnSite

34 System Breakdown Culture/Process Development principles Team structures Planning process OnDemand Analytics / Monitoring Customer Feedback OnSite

35 System Breakdown Culture/Process Development principles Team structures Planning process Development process OnDemand Analytics / Monitoring Customer Feedback OnSite

36 System Breakdown Product Architecture OnDemand Analytics / Monitoring Customer Feedback OnSite

37 System Breakdown Product Architecture Technical coupling between products and addons. OnDemand Analytics / Monitoring Customer Feedback OnSite

38 System Breakdown Product Architecture Technical coupling between products and addons. UI Integration patterns/goals OnDemand Analytics / Monitoring Customer Feedback OnSite

39 System Breakdown Product Architecture Technical coupling between products and addons. UI Integration patterns/goals Shared services, APIs, and libraries OnDemand Analytics / Monitoring Customer Feedback OnSite

40 The Pipeline Pipeline of Unicorns

41

42 Geek details Split compute from storage. No disks in compute. RAM. Less power. 1s startup. Data centres only provides power and floor space. We own everything else. Ditch full virtualization used openvz. Partnered with an integrator. Shared mount to avoid rsync customers per rack. Deploy one set of binaries. Allows regional rollouts, daily upgrades, fast restarts and much more... dark features, plugins, manager nodes, backups...

43 Monitoring

44 Monitoring Visualization Collection Storage REST API Filtering Notification

45 Process and Culture

46

47

48

49

50

51 Process Changes Small shipable chunks. Decoupled from one another (includes marketing) Minimize hand-offs Product teams deploy themselves. X-team feature teams PM/Dev/Marketing Minimize branching, use dark features and plugins Upfront testing, done means done Metrics and goals for theme teams allows more asynchronous, measurable, craddle to grave.

52 Product Architecture

53 Architecture Principles

54 Architecture Principles Products

55 Architecture Principles Products Stay away from a mega-app Assume products are not hosted on the same physical infrastructure Use integration levels and make them optin and backwards compatible.

56 Architecture Principles Addons Products Stay away from a mega-app Assume products are not hosted on the same physical infrastructure Use integration levels and make them optin and backwards compatible.

57 Architecture Principles Addons Products Independant Deploy Rich UI Integration Independant Purchase Own User Licensing Remote Can t slow products Stay away from a mega-app Assume products are not hosted on the same physical infrastructure Use integration levels and make them optin and backwards compatible.

58 Cross Training

59 Cross Training Payed Beta

60 Cross Training MVP 1.0 Payed Beta

61 Cross Training MVP 1.0 Discounts Payed Beta

62 Cross Training MVP 1.0 Discounts Fast Releases Payed Beta

63 Cross Training Payed Beta MVP 1.0 Discounts Fast Releases Wrong Market?

64 Cross Training Killer Features Payed Beta MVP 1.0 Discounts Fast Releases Wrong Market?

65 248 to 98 to 1

66 248 to 98 to 1-7

67 Recap How do you compare? Someone is running in front of you Holistic systems thinking Needs a company wide pivot, decision making has to change Build your Unicorns (think 10x) Architecture is important to scale Share your principles and system view so that teams can self optimize and remove waste. Cross train Try several small experiments

68 Thank You!