Introducing Atlassian Compass: Solving the problem of information search for developers

9min Snip

00:00

Play full episode

Summary

Transcript

Episode notes

This chapter provides a thorough description of Atlassian's developer experience platform called Compass, which aims to solve the problem of developers spending too much time searching for necessary information. It outlines the four ways in which Compass helps engineering teams and mentions various companies already using Compass to improve their developer experience.

This week we’re joined by Preeti Kota, the Head of Engineering for Compass at Atlassian. Preeti walks us through Atlassian’s journey with developer experience: including how they measure DevEx, and how they drive improvements through efforts at both the organization and team levels. Preeti also talks about how this journey has led to the development of Atlassian’s newly released internal developer portal, Compass.

Mentions and links:

Learn about Compass, Atlassian’s newly released internal developer portal
Connect with Preeti on LinkedIn
Atlassian’s CTO, Rajeev Rajan, on the key to unlocking developer productivity

Discussion points:

(1:43) Where Atlassian’s journey with developer experience began
(5:36) Who is championing the focus on DevEx at Atlassian
(9:30) How the company arrived at their level of investment in DevEx
(13:47) Defining developer experience
(18:19) How the program for improving developer productivity is structured
(21:19) The Developer Productivity Champions group
(23:53) Two metrics in focus: Self-serve documentation and self-serve dependency maintenance
(25:56) How Atlassian surveys developers
(29:59) Types of projects the centralized teams tackle
(31:19) Getting buy-in for investing 10% time toward DevEx projects
(33:13) How leaders get teams to feel they have permission to invest 10% of their time toward DevEx projects
(36:19) The backstory behind Compass, Atlassian’s new product
(38:10) What Compass is, who it’s for, and how it is unique