Centralising the right things

Transcript

1. 1.

   @tombooth Centralising the right things Tom Booth

2. 2.

   @tombooth

3. 3.

   @tombooth tl;dr

4. 4.

   @tombooth Build a central team to empower and support others

5. 5.

   @tombooth Centralised Decentralised Re-centralised

6. 6.

   @tombooth Centralised Decentralised Re-centralised

7. 7.

   @tombooth

8. 8.

   @tombooth We weren’t one business, we were compe>ng func>ons

9. 9.

   @tombooth Protec>onism built through compe>>on

10. 10.

    @tombooth

11. 11.

    @tombooth Every 3 weeks, …

12. 12.

    @tombooth

13. 13.

    @tombooth Every 3 weeks, we had a wild ride of

    forgoHen changes
14. 14.

    @tombooth Opera>ons would get the blame for developer problems

15. 15.

    @tombooth

16. 16.

    @tombooth Why did their change break my code?

17. 17.

    @tombooth Centrally provided tools were very poor

18. 18.

    @tombooth GeLng features to our users was slow When we

    were centralised,
19. 19.

    @tombooth Change was complex because of poor design When we

    were centralised,
20. 20.

    @tombooth Func>onal ownership caused serious fric>on When we were centralised,

21. 21.

    @tombooth Centralised Decentralised Re-centralised

22. 22.

    @tombooth One team needs to own the whole service

23. 23.

    @tombooth

24. 24.

    @tombooth You have to embrace change

25. 25.

    @tombooth Deploying con>nuously is beHer for users

26. 26.

    @tombooth A team should own its own architecture and infrastructure

27. 27.

    @tombooth

28. 28.

    @tombooth Every team with their own direc>on, liHle shared

29. 29.

    @tombooth Solving the same problems, in the same way with

    different implementa>ons
30. 30.

    @tombooth Opera>ng at larger scale requires deeper knowledge

31. 31.

    @tombooth GeLng features to our users was slow When we

    were centralised,
32. 32.

    @tombooth Change is complex because of poor architecture When we

    were centralised,
33. 33.

    @tombooth Func>onal ownership caused serious fric>on When we were centralised,

34. 34.

    @tombooth The same problems were being solved repeatedly When we

    were decentralised,
35. 35.

    @tombooth No-one has the complete picture When we were decentralised,

36. 36.

    @tombooth We weren’t focusing on our users as much as

    we should When we were decentralised,
37. 37.

    @tombooth Centralised Decentralised Re-centralised

38. 38.

    @tombooth Retain ownership in the service teams

39. 39.

    @tombooth Iden>fy common paHerns in our infrastructure

40. 40.

    @tombooth Support common paHerns with great tooling

41. 41.

    @tombooth Always ask, how can we help each other?

42. 42.

    @tombooth Give teams room to experiment, do what’s best for

    them
43. 43.

    @tombooth Outside impressions maHer

44. 44.

    @tombooth

45. 45.

    @tombooth Help our owners, investors and auditors understand our services

46. 46.

    @tombooth Work together not apart

47. 47.

    @tombooth Work together on architecture

48. 48.

    @tombooth Work together on issues

49. 49.

    @tombooth Work together on bugs in produc>on at 3am

50. 50.

    @tombooth GeLng features to our users was slow When we

    were centralised,
51. 51.

    @tombooth Change is complex because of poor architecture When we

    were centralised,
52. 52.

    @tombooth Func>onal ownership caused serious fric>on When we were centralised,

53. 53.

    @tombooth The same problems were being solved repeatedly When we

    were decentralised,
54. 54.

    @tombooth No-one has the complete picture When we were decentralised,

55. 55.

    @tombooth We weren’t focusing on our users as much as

    we should When we were decentralised,
56. 56.

    @tombooth Build a central team to empower and support others