In this article I address the question of how to measure developer workforce productivity in general and development effectiveness specifically. As most seasoned managers will already have learned, development measurements are best assessed against groups of engineers aligned to an outcome: a service or a product delivers a tangible result or value, rather than against any individual activity: how hard a developer works.
This document is the companion article to the presentation made on 16 November 2018 at Agile Testing Days, Potsdam. I discuss the relationship between disruptive technologies, quality and release orchestration.
Presentation at Agile Testing Days 2018, Potsdam