Developer Experience Survey

Understand precisely what’s holding your developers back and which improvements would yield the highest value for the team.

Prep time

90m

Run time

45m

Persons

3+

People working together at the table

Prep time

90m

Run time

45m

Persons

3+

Summary

  • Select your vital signs.

  • Run a developer experience survey and analyze data.

  • Discuss the results and document an action plan to improve developer experience.

What you will need

  • Survey tool

  • Digital collaboration tool

  • Whiteboard

  • Post-its

How to create an effective developer experience survey

Understand precisely what’s holding your developers back and which improvements would yield the highest value for the team.

What is a developer experience survey?

Developer experience is how developers feel about, think about, and value their work. Unlike other quantitative metrics that measure the systems enabling developer productivity, experience can only be measured by asking people qualitative questions about their feelings. Surveys are an effective way to gather sentiment data about the developer experience.

At Atlassian, we believe the most effective approach to measuring developer productivity is to use a combination of quantitative and qualitative data. This combination gives us a more contextual understanding of the friction faced by developers.

Why run the developer experience survey play?

Asking developers how satisfied they are with their ability to be productive within their codebases, the tools they use, and the overall software development lifecycle (SDLC) provides tremendous insights and acts as a means to measure overall progress in improving the day-to-day life of the developer.

You can use this data to identify bottlenecks and prioritize improvements to the developer experience.

When should you run a developer experience survey play?

We recommend running the Developer Experience Survey Play at least twice each year if you are happy with your success metrics but need to maintain a pulse on vital signs, or quarterly if you are actively working on improving your developer experience.

5 benefits of a developer experience survey play

  • Surveys allow us to measure things that are otherwise unmeasurable.

  • Survey data provides missing context for quantitative vital signs.

  • Running the survey on a semi-annual or quarterly basis enables you to track improvements over time.

  • Surveys provide an opportunity for input directly from each engineer making them feel heard.

  • Creating rituals around the survey provides an opportunity for teams to discuss the developer experience at least 4 times a year (culture impact).

Still have questions?

Start a conversation with other Atlassian Team Playbook users, get support, or provide feedback.

Plays you may like

Goal-setting

Objectives and Key Results (OKRs)

Define what objectives to achieve, and track progress with measurable key results.

Decision-making

DACI Decision-Making Framwork

Assign clear roles to ensure effective collaboration and accountability during the decision-making process.

Decision-making

Project Trade-Off Analysis

Compare the benefits and costs of different options in a project.

Goal-setting

Modeling Strategic Focus Areas

Build and align on your organization’s strategic focus areas.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.

Stay up to date

Get the latest Plays and work life advice when you sign up for our newsletter.