apidays Australia 2023 - Enable Faster Delivery With Collaborative Platform Teams, Leoren Tesaluna & Justin Bugeja, Wesfarmers OneDigital

apidays Australia 2023 - Platforms, Products, and People: The Power of APIs
October 11 & 12, 2023
https://www.apidays.global/australia/

Enable Faster Delivery With Collaborative Platform Teams
Leoren Tesaluna, Senior Platform Engineer at Wesfarmers OneDigital
Justin Bugeja, Cloud Engineer at Wesfarmers OneDigital

------

Check out our conferences at https://www.apidays.global/

Do you want to sponsor or talk at one of our conferences?
https://apidays.typeform.com/to/ILJeAaV8

Learn more on APIscene, the global media made by the community for the community:
https://www.apiscene.io

Explore the API ecosystem with the API Landscape:
https://apilandscape.apiscene.io/

Transcript

1. Enable faster delivery with collaborative platform teams Justin Bugeja Leoren Tesaluna
3. 2 Hello! Justin Bugeja Platform Engineer Leoren Tesaluna Senior Platform Engineer leoren-tesaluna justin-bugeja
4. est 2022
5. 4 Let’s talk platform
7. Secure Reliable Compliant
8. 7 “Platform team creates all infrastructure and tooling”
9. 8 “Platform team creates all infrastructure and tooling” = misunderstanding , time wasted
10. 9 “Platform team creates all infrastructure and tooling” enables
11. 10 Partnership with Developers
12. 11 Communicate & Understand
13. Team Resource Comments Purchase Team uses CFN Account Team uses CDK Features Team uses CDK Data Team Deployed manually ECS SQS Lamba S3 SQS EC2 ECS Lambda S3 S3 Lambda SQS ECS
14. What did we try first?
15. 14 Patterns
16. Platform Team Dev Teams Dev Team’s AWS account S3
17. 16 • Templates are abstracted • Cloudformation is unfamiliar to some developers
18. What was our context at OneDigital?
20. Unfamiliar to devs Declarative = confusing
21. Declarative = confusing Unfamiliar to devs
23. Construct == Building blocks
24. Storage
25. Storage
26. Storage
27. Storage
28. Storage
29. Construct Storage
30. 29 • Reduce duplication • Reduce cognitive load • Sustainable support model • Standardised tooling
33. What happened?
34. Too much abstraction!!
35. Too few constructs!!
36. We were still a bottleneck We had to change
37. • Be transparent • Remove abstractions • Don’t gatekeep • Allow developers to contribute
38. 37 Cloudkit created by OneDigital
39. But how were we going to get developers involved?
40. We needed to change the culture
41. InnerSourcing culture
42. innersourcecommons.org/learn/books/
43. 42 “...InnerSource involves changing the philosophy of working and of leveraging and empowering the developers within your organization."
44. Community of Trusted Committers
45. We had to start small
46. Grow organically
47. 46 Communicate and collaborate
48. • Communities of practice (AKA Guilds) • Engineering huddle s • Showcases
49. Pair with early adopters
51. 50 Pattern
52. Constructs
53. 52 Constructs Pattern
55. Keep the engagement going
59. 58 • Training videos • Temporary team-embedded engineers • Bootcamps
60. 59 Self-paced training materials
61. Celebrate!
62. 61 Recap • Communicate with customers • Platform transparency • Innersourcing culture • Keep the engagement going
63. How can you get started?
64. 63 Developers - Engage with Platform Platform - Look for Patterns Delivery - Consider InnerSourcing
65. 64 Platform teams should not be gatekeepers but rather, enablers
66. 65 Thank you ! Justin Bugeja Leoren Tesaluna justin-bugeja leoren-tesaluna