DORA metrics aren’t enough on their own. Here’s how dev teams can make the leap to elite performance by focusing on pull request size and dev workflow while improving their cycle time.
I am very very skeptic about this whole DORA org and approach and adoption. I have a greatest respect to the DevOps philosophy, but from DORA I only got a baseless/faceless metrics. Maybe it is also Google driving it that gives me additional rejection impulses. I am quite skeptic at what and how Google does and this colors my perception of all thing it produces.
apd@programming.dev 11 months ago
Goodharts Law applies here - “Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes”
douglasg14b@programming.dev 10 months ago
Pretty much.
For instance focusing on PR size. PR size may be a side effect of the maturity of the product, the type of work being performed, the complexity or lack thereof of the real world space their problems touch, and in the methodologies habits and practices of the team.
Just looking at PR size or really any other single dimensional KPI lead you to lose the nuance that was driving the productivity in the first place.
Honestly in my experience high productivity comes from a high level of unity in how the team thinks, approaches problems, and how diligent they are about their decisions. And isn’t necessarily something that’s strictly learned, it can be about getting the right people together.