It’s very hard to define what a good developer experience is. Every engineering team wants to provide one. Some things are table stakes, such as: automated deployments to production for a given branch and git commit, tests running after each push on CI/CD, PR workflow with review step. There have been some highly-regarded attempts to measure devops objectively along these lines of common practices and capabilities of high performing teams, like DORA. At Coherence, we want to build tools that make it easy to measure and improve the KPIs that matter to you.
But high performance does not mean developers know how to use all their tools or that they feel that they’re empowered to do their best work. Something like developer NPS - can also be used for DevOps and in general teams that have invested in good tooling are happy about it in my experience. We believe that quality tooling helps with retention, time to value, and overall performance and productivity.
Not all metrics matter to all orgs, at least not equally. You should think about which KPIs matter to you. Metrics that might be important to your org:
Once you know what metrics you want your team to watch, you need to make sure that they’re able to do so. And also almost as important - kept up to date as metrics and definitions change. How current are your Devops documentation pages? Is your developer experience consistent between different services? Do all of your developers know:
If you’re doing well on the above observability and knowledge metrics, how much time do you spend maintaining those tools and systems? If you’re asking yourself questions like:
Come talk to us and take Coherence for a spin!