Developer Experience Assessment.

Why DevEx?

Developer experience is a measure of how smooth it is for someone to perform essential tasks needed to deliver software. Better Developer Experience leads to more flow. More flow leads to more productivity.

Our approach.

Preparation

Identify owner

The assessment owner has the mandate to drive the assessment and own the results from your side.

Define scope

Define a rough start and end for the assessment. Commonly we conduct planning interviews to set a structure for the assessment.

Start!

Based on the scope we begin the assessment with the investigation to research and learn about your current developer experience.

Investigation

Below are the methods we use to investigate your current developer experience. We use a combination of these methods to get a holistic view of your current state.

Value Streams

We facilitate Value Stream Mapping workshops with your development teams to understand their workflows, pains, waste and opportunities for increased flow.

Wardley Maps

We use Wardley Mapping to understand the interface between platforms and developers. It helps us reason about the cognitive load and platform evolution.

Gemba Walks

We do Gemba Walks to understand the current state of your development teams. We observe and ask questions to understand their daily routine and how we can improve it.

Developer Surveys

Ongoing surveys that provide actionable results help us gauge the effects of change and highlight teams that may need more support.

Report

Report

We prepare a report summarizing the investigation, the pain points (i.e. waste) and our own suggestions that we can think of. This is the first version of a backlog.

Feedback

A discussion about the assessment and report. It is important that you understand the report and are comfortable with the implementation.

Build - Measure - Learn

This is where the real work of implementing change begins. It is important to do it iteratively and our crew are here to assist.