Developers face the prospect of being more closely scrutinized to assess their productivity quotients in the year ahead. With the ever-present specter of AI code assistant technologies now offering programmers a route to eliminating the “donkey work” of provisioning, data preparation and application patching (and so on), our software professionals are now supposed to be able to get on with really useful value-added work.
But does this wider engineering epiphany mean we’ll start to separate the wheat from the chaff with a more mercenary management approach?
Certainly, we have already highlighted the suggestion that so-called “ghost developers” have the potential to ride the wave of team effort without contributing productive commits to the total code base in some scenarios. Given these factors – and the fact that we’re also supposed to care about developer wellbeing and happiness now more prevalently – what tools should we be aware of in this space?
A Unified Productivity Measure
DX Core 4 is a framework for measuring developer productivity that encapsulates and unifies DORA, SPACE and DevEx. Let’s break those down with a reminder.
Digital Operational Resilience Act (DORA) is a European Union directive designed to analyze and improve the digital operational resilience of financial entities and their technology suppliers, primarily from a security and cyber risk perspective.
The Satisfaction (and well-being), Performance, Activity, Communication (and collaboration) and Efficiency (and flow) SPACE framework measures software engineering team productivity by integrating various “dimensions” of productivity, such as the quality and impact of workers’ productivity ratings.
The DevEx framework (which itself was authored by some of the software luminaries who created SPACE) is designed to coalesce three key dimensions experienced by developers: Feedback loops, cognitive load and flow state. Project managers can choose a combination of selected metrics from those dimensions to focus on workflow elements that they think need productivity improvements.
How Many Measures Matter?
If at this point (and we promise to come back to DX Core 4) you’re thinking, how many productivity measures matter and do we actually need a productivity measure measurement tool, then that’s a reasonable train of thought. This selection pack of coding yardsticks has probably come about because, in truth, no single tool used in isolation will ever be enough.
As a collected group of software engineering gurus detail on webpages belonging to the Association for Computing Machinery (ACM) in line with the initial launch of SPACE, “The most important takeaway from exposing these myths [around developer work rates] is that productivity cannot be reduced to a single dimension or metric!. The prevalence of these myths and the need to bust them motivated our work to develop a practical multidimensional framework, because only by examining a constellation of metrics in tension can we understand and influence developer productivity. This framework, called SPACE, captures the most important dimensions of developer productivity: Satisfaction and well-being.”
So back to DX Core 4 and its approach to unified encapsulation, which comes from the authors of the DevEx and SPACE frameworks (you’d already guessed that part, right?), the team behind this approach says that engineering leaders are still spending months wading through dashboards and establishing a chosen set of metrics, only to still find themselves without alignment and traction.
“To help simplify the landscape, we’ve developed a unified approach to measuring developer productivity called the DX Core 4. The DX Core 4 encapsulates DORA, SPACE and DevEx and includes four dimensions: Speed, effectiveness, quality and business impact. The DX Core 4 provides a focused set of metrics that work effectively at any sized organization and can be augmented with additional metrics for specific goals,” detail Abi Noda, Laura Tacho, Dr. Margaret-Anne Storey, Dr. Michaela Greiler and Dr. Nicole Forsgren, representing views from DX’s research and consulting practices.
In terms of some solid advice to go forward with, magical analyst house Gartner joins Forrester in estimating that around three-quarters of enterprises now have a formal developer experience analysis program in place or planned. Gartner’s quadrilateral wizards say 75% and Forrester says 75%, but at this stage who’s counting?
Fear and Gamification Loathing
Getting more real world at least, the DX Core 4 team agrees that all development teams should avoid the fear factors associated with overly amplified gamification. This is because speed and throughput metrics, when used in isolation, often incite fear and counterproductive behaviors from developers. The DX Core 4 ethos also calls for the need to communicate transparently to teams and leaders.
“Multiple dimensions are needed to capture software development comprehensively because changes to one dimension, such as speed, may negatively affect others (e.g. quality or effectiveness). The DX Core 4 includes four counterbalanced dimensions with metrics that encompass DORA, SPACE and DevEx,” notes the team.
The core of the matter here most likely comes down to the fact that – like a live performance from a rock guitar virtuoso or perhaps a great chef – software application development is tough, complex, essentially creative and often difficult to repeat as we might codify and look to replicate other work functions. Plus anyway, it will often also be a factor of personal taste and satisfaction when application functionality finally ends up in the hands of the user.
