Mobile release Vilnius, 10/2018

Transcription

1 Mobile release Vilnius, 10/2018

2 XING +1 k employees (30+ nationalities) +200 developer +40 product teams Founded 2003 as Open BC since listed company HQ Hamburg Professional network People, Jobs, News, Events +13 Mio users, DACH focus 2

3 How did it start

4 Development setup PO A P I +10 QA Logo: 4

5 Irregular releases for ios and Android Flexible Flexible Feature development Final testing Review Start Feature complete Public Release Submit/ Upload 5

6 Irregular releases for ios and Android Flexible Flexible Feature development Final testing Review Start Feature complete Public Release Submit/ Upload 6

7 Irregular releases for ios and Android Flexible Flexible Feature development Final testing Review Start Feature complete Public Release Submit/ Upload 7

8 Irregular releases for ios and Android Flexible Flexible Feature development Feature development Final testing Review Start Feature complete Public Release Submit/ Upload Feature complete 8

9 Facts Central product, development & release 2 ios / 2 Android devs Feature driven releases Few releases per year 9

10 Challenges Slow time to customer Mobile and API Teams- Bottleneck Too many stakeholders / topics 10

11 Team split

12 Development setup PO A P I +10 PO 12

13 Irregular releases for ios and Android Flexible Flexible Feature development Feature development Final testing Review Start Feature complete Public Release Submit/ Upload Feature complete 13

14 Why change? Increased mobile traffic +10 domain teams requirements API unleashing Scaling problems Duplicated domain knowledge Full-stack product thinking 14

15 Mobile Unleashing

16 Development setup PO A P I +10 PO 16

17 Release Train 17

18 Regular release trains for ios < 2 weeks 2-3 days 1 week approx. 1 week Feature development Final testing Pre-release Review process Start Feature complete Start prerelease Submit Public release 18

19 Regular release trains for ios < 2 weeks 2-3 days 1 week approx. 1 week Feature development Final testing Pre-release Review process Start Feature complete Start prerelease Submit Public release 19

20 Regular release trains for ios < 2 weeks 2-3 days 1 week approx. 1 week Feature development Final testing Pre-release Review process Start Feature complete Start prerelease Submit Public release 20

21 Regular release trains for ios < 2 weeks 2-3 days 1 week approx. 1 week Feature development Final testing Pre-release Review process Start Feature complete Start prerelease Submit Public release 21

22 Regular release trains for ios < 2 weeks 2-3 days 1 week approx. 1 week Feature development Final testing Pre-release Feature development Final testing Pre-release Review process Start Feature complete Start prerelease Submit Public release 22

23 23

24 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 24

25 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 25

26 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 26

27 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 27

28 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 28

29 Regular releases trains for Android < 2 weeks 2-3 days 1 week 2 days 5 days Feature development Final testing Beta testing Feature development Final testing Beta testing 20% 50% Start Feature complete Public Beta release 20% release 50% release 100% release 29

30 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

31 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

32 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

33 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

34 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

35 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

36 Prerequisites Test automation Unified tooling Team cooperation Patterns Team responsibility

37 Facts Distributed asynchronous product development 10 ios / 10 Android devs Centralized release per platform Development start > release 4 weeks cycle 37

38 Challenges Several versions simultaneously in roll out phase Different processes for ios and Android Mandatory tools/processes 38

39 Release Team 39

40 Development setup PO BE A P I +10 PO 40

41 Who is doing what? Platform teams + DST s: Releases Team: What (content) How (process) 41

42 Regular release trains for ios < 2 weeks 2-3 days > 1 week Feature development Final testing Pre-release Review process Start Feature complete Submit Public release 42

43 Regular release trains for ios < 2 weeks 2-3 days > 1 week Feature development Final testing Feature development Final testing Pre-release Review process Start Feature complete Submit Public release 43

44 Regular releases trains for Android < 2 weeks 2-3 days 2 days 4 days Feature development Final testing 20% 50% Beta testing Start Feature complete 20% release 50% release 100% release 44

45 Regular releases trains for Android < 2 weeks 2-3 days 2 days 4 days Feature development Final testing Feature development Final testing 20% 50% Beta testing Start Feature complete 20% release 50% release 100% release 45

46 Facts Distributed product development +30 ios / +20 Android Centralized unified release Development start > release up to 3 weeks 46

47 Challenges Releases Team responsibilities Automatic enforcement of rules HotFixes too easy? 47

48 Single team Unleashing Release team PO PO PO PO PO BE Central development Feature driven release Few releases per year Distributed development Regular release trains Platforms doing releases 4 weeks cycles Distributed development Regular release trains Central release team Unified processes 3 weeks cycles

49 Single team Unleashing Release team PO PO PO PO PO BE Central development Feature driven release Few releases per year Distributed development Regular release trains Platforms doing releases 4 weeks cycles Distributed development Regular release trains Central release team Unified processes 3 weeks cycles

50 Single team Unleashing Release team PO PO PO PO PO BE Central development Feature driven release Few releases per year Distributed development Regular release trains Platforms doing releases 4 weeks cycles Distributed development Regular release trains Central release team Unified processes 3 weeks cycles

51 Single team Unleashing Release team PO PO PO PO PO BE Central development Feature driven release Few releases per year Distributed development Regular release trains Platforms doing releases 4 weeks cycles Distributed development Regular release trains Central release team Unified processes 3 weeks cycles

52 Experiments continue 52

53 A lot of new challenges Global Improvements Red Global Improvements Hybrid content Delays Release: Bug found What to do? 53

54 Thank you for your attention 54

55 Links and References 55