I'm not sure if I fully understood the question. if you are asking me what I would like to know on the above-listed item. then I will go for build and test.

I always like the fundamentals.

commits

• how do actually good commits look like?
• how are realistic metrics built around it?

builds

• what are good fail/success ratios?
• what data can we gather from a build?
• build time improvements how to measure regressions in the build time of multitarget architectures?

tests

• what are the core differences between: unit, functional, integration tests
• generative testing vs static testing
• maybe generational testing with statistic probabilities of regressions by utilizing 'sleeping' tests as sample sets?
• purposely breaking something to check the tests validity

well code review is always tricky in my opinion. And currently I am quite saturated with this particular topic

I am not quite sure what people data means, so I cannot say anything about that. Is it heatmap behaviour tracking? a/b testing? or internal metrics for the team? Or is it about wellness/happiness of your surroundings and the direct correlation towards work? aka burnout/stress-sickness and so on.

Just thinking out loud here, I hope at least one thing is a bit useful. :)