Crafting the Ultimate Toolkit for API Platform Teams: What You Are Missing
0 likes•26 views
The document outlines the key components for building an effective API platform team toolkit, focusing on the three P's: people, processes, and products. It emphasizes the evolution of DevOps to platform engineering while discussing the importance of understanding customer needs and continuous improvement through feedback. The presentation also highlights the increasing velocity of development attributed to dedicated platform teams and the significance of a product mindset in platform engineering.
Crafting the Ultimate Toolkit for API Platform Teams: What You Are Missing
- 1. Platform Summit 2023 Crafting the ultimate toolkit for API Platform teams: What you are missing
- 2. Budhaditya Bhattacharya Developer Advocate, Tyk Your friendly speaker India, Singapore, USA (Durham) ● Product education, community engagement, and open-source ecosystem expansion ● Programme instructor - API platform engineering fundamentals programme ● Host - All About APIs podcast ● Host - API hangout, GraphQL Hangout ● Curator - API Platform engineering newsletter ● Horror movies & musicals
- 3. 02 03 04 05 01 Why we need a platform toolkit The 3 Ps - People The 3 Ps - Process The 3 Ps - Products Q&A Agenda What’s in store for you
- 4. Why we need a platform toolkit
- 5. Philosophy of DevOps EVOLUTION OF DEVOPS “You build it, you run it!” Amazon CTO, 2006 Move fast, break things, do more with less.
- 6. The DevOps expectation PHILOSOPHY OF DEVOPS ● Increased velocity ● Reduced friction ● Shortened feedback loops ● Optimised flow to deliver end-to-end business value ● Continuously experimenting, learning and improving Source: The Three Ways: The Principles Underpinning DevOps
- 7. Reality of DevOps EVOLUTION OF DEVOPS
- 8. 80% Incomplete DevOps journey 15 years into the DevOps revolution, 80% of organizations feel they are only about halfway through their DevOps journey Source - 2023 Puppet State of Platform Engineering report
- 9. Developer fatigue REALITY OF DEVOPS Increased cognitive load = lower productivity ● Bogged down by infra work ● Shifting left on everything ● Too many tooling choices ● No focus on docs, self service, DevEx
- 11. 68% Development velocity Increased development velocity due to platform teams - 2023 Puppet State of Platform Engineering report Source - 2023 Puppet State of Platform Engineering report 80% Gartner forecast By 2026, 80% of software engineering organizations will have created a platform team Source: Gartner’s platform engineering forecast
- 12. But wait… THE BIG PICTURE Will history repeat itself? DevOps —> Platform engineering —> ???
- 13. The platform team toolkit: The three P’s
- 14. The people THE PLATFORM TEAM’S TOOLKIT
- 15. Platform as a product mindset THE PLATFORM TEAM’S TOOLKIT 01 People 02 03 Processes Products Shift in organisational culture - combining principles of product management with platform engineering Product => IDP Customer => Developers Not just an off the shelf, one and done platform - constantly evolving, growing, streamlining based on user needs
- 16. Team composition (roles) A Product Owner Engineers/ developers Solution architect Advocate/evangelist UX/ DX researcher
- 17. How teams connect THE BIGGER PICTURE API Platform teams API Product developers API Product consumers Feedback Feedback Don’t look at your platform team in isolation
- 18. The processes THE PLATFORM TEAM’S TOOLKIT
- 19. Jobs to be done JTBD A theory, framework and perspective on why consumers buy/adopt a product Source: What is Jobs to be Done (JTBD)?
- 20. Why you should care JTBD ● Reveal your customers’ true needs and desires. ● Develop products that meet needs of customers better ● Helps forecast how your product will fare on the market. ● Inform product marketing messaging, and guide business decisions better
- 21. Identifying Jobs to be Done JTBD 01. Pains Identify unmet customer needs. What pain points do my customers have in common? What do they currently lack? 02. Gains Determine customers’ desired outcomes What is it we are helping customers do or helping them avoid 03. State, test, refine Articulate the pains and gains into clear statements. Use them to build products, test them with customers and refine based on reaction/emotion/feedback.
- 22. Platform teams Job titles Platform manager, Head of platforms /platform engineering, platform engineer, staff engineer, DevOps, SRE Architect and build a performant, secure API platform Scale the API platform across the org Govern & optimise the platform JTBD
- 23. Introducing the ADDR API design process
- 24. ● Aim to reduce friction, cognitive load or both ● May not be a platform at all - documentation, searchable knowledge base ● Emphasis on self-service ● Keeps things streamlined Thinnest Viable Platform AGILE DELIVERY
- 25. Communication and feedback 01 02 03 People Processes Products Communicate goals and objectives clearly, within and across teams - create an internal product/platform roadmap Measure effectiveness of platform - communicate success stories Provide clear route for feedback and communicate how they will be factored into the platform - eg. community forum THE PLATFORM TEAM’S TOOLKIT
- 26. The products THE PLATFORM TEAM’S TOOLKIT
- 27. Product/ platform capabilities THE PLATFORM TEAM’S TOOLKIT Discoverability Security Observability Enabling Integrations
- 28. Product capabilities THE PLATFORM TEAM’S TOOLKIT Discoverability Developer portal Security OAuth, IDP, OPA Observability Open Telemetry Enabling Integrations APIs
- 29. Bringing it all together THE PLATFORM TEAM’S TOOLKIT API Management
- 30. Developer happiness ULTIMATE DESIRED OUTCOME Following the “golden path” ● Standardisation around choices ● Integrated toolchains via APIs ● Automation of infrastructure delivery ● Focus on self service, delivery and DevEx