Platform as product: Serving the customer who serves the customer
Whether an organization is an established leader, or breaking new ground, the mantra is always that we need to move faster. And of course, we need to scale. Architectural and development practices abound that should get us there: agile engineering, microservices, DevOps and so on. But it is not just the our software that needs to scale, but also our approach to delivering it.
| Talk Title | Platform as product: Serving the customer who serves the customer |
| Speakers | |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | San Francisco, California |
| Date | November 14-16, 2016 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Whether an organization is an established leader, or breaking new ground, the mantra is always that we need to move faster. And of course, we need to scale. Architectural and development practices abound that should get us there: agile engineering, microservices, DevOps and so on. But it is not just the our software that needs to scale, but also our approach to delivering it. The DevOps revolution helped our teams solve cross-cutting problems faster by breaking down the barriers between teams. “Platform Thinking” takes up where DevOps leaves off by productizing unique cross-cutting technology and business capabilities as APIs for delivery teams to consume. At scale, we need to enable individual product teams to focus on delivering their products, not on delivering development or operations scaffolding. In this session, we will explore the characteristics of effective platforms and the importance of treating a platform as a product. Platform teams need to treat developers as customers, creating a focus on prioritizing what provides value to them. We give examples of organizational challenges that inhibit platform thinking and product management techniques that can help overcome organizational resistance and platform anti-patterns.
