DevOpsCon 2016: Interview Matthew Skelton
summary
Argues that one size fits none: different team topologies and interaction patterns suit different goals, from tight discovery collaboration to clear platform boundaries. Gives a concrete example: a platform such as Pivotal Cloud Foundry that is built so application teams can deliver without constant ops interaction. Recommends start small and iterate on one product stream with senior buy‑in, expects early failures, measures whether the platform reduces collaboration cost and speeds delivery.
AI-written summary · about
chapters (4)
related talks
46mBeyond DevOps: How and Why Companies Converge on Platform Models
11mInterview of Dimitri Baeli
28mDevOps, 12-Factor, and Platform Engineering
39mPlatform Engineering as a (Community) Service
47mDevOps is for Product Engineers, too.
08mDevOps, 12-Factor and Platform Engineering
47mDevops, microservices and platforms, oh my!
14mKeynote: Open Source & Operational Excellence