Slide 1

Slide 1 text

Platform Engineering at Viva Engage (Yammer) Diego Quiroga Principal Software Engineering Manager at Microsoft Stage C Ask questions using Slido November 7-8, 2023 - San Francisco

Slide 2

Slide 2 text

diego.quiroga@gmail.com @diegoquiroga linkedin.com/in/diego Diego Quiroga Cut my programming teeth on a TK90X (ZX Spectrum clone) 20+ years building things that talk HTTP(s) Platform Engineering at Viva Engage (Yammer) in Microsoft Based in Vancouver, Canada Previously: AWS, OLX, Google

Slide 3

Slide 3 text

What defines a Platform Team? What they do

Slide 4

Slide 4 text

Platform teams provide knowledge, support, and the building blocks that feature teams use to ship business-facing functionality at a faster pace

Slide 5

Slide 5 text

The mission of the platform team, should you choose to accept it, is enabling product teams to get things done

Slide 6

Slide 6 text

Product Team Infra Product Team Product Team DevExp Product Team Core X The mission of platform teams is enabling product teams to get things done

Slide 7

Slide 7 text

Platform Teams ● Must anticipate engineering needs ● Multitask between projects & support ● Work for engineering teams ● Hold a less tangible value proposition ● Have a larger blast radius in decisions ● Satisfy customer needs ● Deliver under time/capacity constraints ● Need to address tech debt ● Deal with conflicting priorities ● Must collaborate cross-team Feature Teams

Slide 8

Slide 8 text

Abstracting one level up and thinking of Interactions and Collaboration Models

Slide 9

Slide 9 text

Platform P F Self-service *x-as-a-service P F Dependencies *collaboration Ask Capability * ’Team Topologies’ equivalent sync async Ability to Scale Assistance P F Request Request Service provider *consulting

Slide 10

Slide 10 text

The Beat of a Very Busy Team

Slide 11

Slide 11 text

Contributing to new customer-facing features Supporting a heavy workload on-call In high demand for assistance and code reviews Attending ad-hoc consultations, often last-minute Finding a path forward.. Improving performance and reliability

Slide 12

Slide 12 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular and structured Office Hours 3. Promoted best ways to engage with the platform team What we did

Slide 13

Slide 13 text

˜430 answered in Qx 70% < 3 days Hacking Week!

Slide 14

Slide 14 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular and structured Office Hours 3. Promoted best ways to engage with the platform team What we did

Slide 15

Slide 15 text

No content

Slide 16

Slide 16 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular and structured Office Hours 3. Promoted best ways to engage with the platform team 4. Created paved paths with templates, and How-To guides What we did

Slide 17

Slide 17 text

No content

Slide 18

Slide 18 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular and structured Office Hours 3. Promoted best ways to engage with the platform team 4. Created paved paths with templates, and How-To guides 5. Used playbooks and coached the platform team What we did

Slide 19

Slide 19 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular, structured Office Hours 3. Promoted best ways to engage with the platform team 4. Created paved paths with templates, and How-To guides 5. Used playbooks and coached the platform team 6. Invested in troubleshooting tools to offload work What we did

Slide 20

Slide 20 text

No content

Slide 21

Slide 21 text

Reusability Sustainability

Slide 22

Slide 22 text

1. Tracked inbound requests, leveraged analytics 2. Formalized regular, structured Office Hours 3. Promoted best ways to engage with the platform team 4. Created paved paths with templates, and How-To guides 5. Used playbooks and coached the platform team 6. Invested in troubleshooting tools to offload work 7. Moved from one-off dependencies to reusable capabilities What we did

Slide 23

Slide 23 text

Our Team Today

Slide 24

Slide 24 text

Simplification: reducing changes required for new features Offloading non-critical tasks: running a Champions program Feature teams owning their QoS: training teams on reliability Increased visibility: for platform work impact and future plans What keeps us busy

Slide 25

Slide 25 text

Wrapping up: The Challenge of Capacity

Slide 26

Slide 26 text

● Practices, tools, and culture define platform teams ● Reduce toil, document, and promote self-service ● View requests as opportunities to empower others ● Showcase impact through compelling stories ● Always be creating more Capacity 5 things to remember

Slide 27

Slide 27 text

Thanks for listening! Questions? Continue conversation in Roundtable 7 at 3pm Stage C Ask questions using Slido