Transform your developer experience with Atlassian Compass

Hello and welcome to today's webinar on transforming developer experience with Compass. Today we're going to talk a little bit about the crisis of modern development, why we actually need to talk about transforming the developer experience, what DevOps is all about, and what the development workflow looks like in an ideal environment. Then we jump right into the Atlassian Compass demo, and we will end with a Q&A session where you can ask questions. This webinar will be recorded, and you will find it on our website later on.

My name is Jan Szczepanski, I'm the head of product and partner marketing here at Eficode, and I'm joined today by Marko Klemetti, our CTO. Thank you very much, Marco, for being with me today. To introduce Eficode briefly, we are an international consultancy company building the future of software. Currently, we have 300 million euros in revenue, working with 650 professionals across 10 different countries. In the last 12 months, we've been serving 1,600 customers across various industries. The key industries we usually work with include finance, insurance, industrial embedded environments, transportation, and technology media and telecom.

When we talk about transforming the development experience, something might not be right. Imagine a developer wanting to deploy a single feature but having to juggle with at least 15 different tools. Instead of focusing on coding, they lose hours in meetings, debugging pipelines, and painstakingly navigating through buggy files and searching for documentation in various tools like Confluence, SL, email, Jira tickets, and mob boards. This phenomenon, known as tool sprawl, forces teams to manage up to 90 different tools, greatly increasing complexity and cognitive load. Harvard calls this the business trap. Custom developers feel productive while fixing pipelines, but is that having a real impact?

We've had DevOps now for nearly 20 years, and what we've seen happening across industries is that there are literally thousands of different tools that can be used to improve the developer pace and help them in their daily work. Organizations have implemented these tools into use in different teams, leading to a maintenance burden. Many researchers now show that most teams spend more than half their time just maintaining the tooling instead of focusing on core business or actual development of features for users. The people behind the code also suffer; two out of five IT professionals report a high risk of burnout, and more than 40% of those affected are considering leaving their organization in the next six months. Burnout is not just a marginal issue; it's costing organizations billions of dollars every year, and this crisis needs a solution.

DevOps was revolutionary until it created a new problem: complexity. Teams now need experience with Kubernetes, Terraform, and Argo just to ship code. Essentially, DevOps teams are now driving tool creation, which has led to confusion about who to ask when needing something, whether it's a new pipeline, a security tool, or documentation. Imagine being a developer in your company today and needing to start coding. The key parts of functioning DevOps practices include automation and healthy practices to manage existing software effectively. This is where we really increase the cognitive load on developers unless we build automation and healthy DevOps practices.