What a Good Platform Looks Like and How to Get There @ Large Financial Organization, Oct 2024

This talk presents a case study of what a good digital platform might look like (Adidas) and another on the steps to get there (SAP).

Transcript

1. TeamTopologies.com @TeamTopologies What a Good Platform Looks Like & How to Get There Manuel Pais co-author of Team Topologies Large Financial Organization - 9 October 2024
2. Team Topologies Organizing business and technology teams for fast flow Matthew Skelton & Manuel Pais IT Revolution Press, 2019 teamtopologies.com/book Over 175.000 copies sold
3. “fast flow means multiple ongoing streams of value to customers via software-enriched services done rapidly, safely, and sustainably” 3
6. What are common Platform “problems”? 7
7. ⚠ A mandated platform increases the cognitive load on teams (i.e. slows them down) 8
8. 9 Ticket-based approach at odds with application scale
9. Functional silos 10 Infra CI/CD Monitoring Deployment Poorly integrated related services
10. 12 Confusing APIs
11. 13 Service unavailable or too slow
12. What is a Platform? 14
13. “A digital platform is a foundation of self-service APIs, tools, services, knowledge and support which are arranged as a compelling internal product.” – Evan Bottcher, 2018 15 Source: https://martinfowler.com/articles/talk-about-platforms.html
14. What Good Looks Like 17
15. Case Study 18
16. Case Study 19 https://www.youtube.com/watch?v=ARaJwB0i8Mc Circa 2020 • Platform work linked to business results • Apps from zero to live in 2 days (vs 6 months in the past) • Cycle time (from commit to production) ◦ 3 days → 1 minute • Deployment frequency ◦ once every 6 weeks → 3 times per day
17. Case Study 20 https://videos.itrevolution.com/watch/431737448/
18. 21 Platform engineering (group) has long term funding
19. 22 Photo by Tim Mossholder on Unsplash The platform acts as an engine for fast flow by increasing the capacity & speed of engineering teams
20. Case Study 23 https://videos.itrevolution.com/watch/431737448/
21. 24 Organized around streams / services clearly identified and owned by dedicated teams
22. Case Study 25 https://videos.itrevolution.com/watch/431737448/
23. Case Study 26 https://videos.itrevolution.com/watch/431737448/
24. 27 Platform teams expected to intentionally adopt & alternate their interaction modes (with internal teams)
26. 29 Invest in building trust early, “plant the seed” for platform adoption later
27. Case Study 30 https://videos.itrevolution.com/watch/431737448/
28. 31 Internal metrics on adoption, user satisfaction, and reliability to stay on track
29. 32 https://www.youtube.com/watch?v=XwaRKcjkAAo
30. 33 https://www.youtube.com/watch?v=XwaRKcjkAAo BIZ LANGUAGE
31. 34 Business metrics (direct and indirect) that clearly show the platform value
32. How To Get There 35
33. Case Study SAP [Enterprise Software] 36
34. Case Study “Adhering to legal regulations of over 180 countries… while running for decades at customers on-prem” 37 Dirk Lehmann - Platform Engineering XXL DevOpsDays 💖 https://devopsdays.org/
35. Case Study 38
36. Case Study “everyone from dev to delivery under one organization reduced a lot of friction (…) and we have a prod mgmt team because we are building a product” 39
37. Case Study 40 “goal of the platform is to relieve development teams from cognitive load due to common, painful tasks” 🎉
38. ⏳ ⏳ Blocking Non- Blocking Security Compliance
44. 47 5 tickets / 10 days self-serve / 2 hours
45. teams & interactions over tools & functionality adoption & engagement over mandates & standards rich customer experience over technical prowess open to change and collaborate to discover user needs unblocking internal customers via self-service patterns aiming for superlinear impact with sublinear growth Platform Manifesto platformmanifesto.is
46. 49 Copyright © Team Topologies Ltd 2024. All rights reserved. teamtopologies.com/ platform-engineering “Platform Engineering as a Way of Thinking and Team-of-Teams Design”