DEV Community

Discussion on: How do you measure and discuss the less measurable things about testing code?

Collapse
jlhcoder profile image
James Hood

I apply this with 2-pizza teams so it doesn't have to be big teams. But if you're talking about 2-3 people, I prefer agile's "people over process" and just poll the group asking how they'd rate quality, what's working, where are the gaps, etc

Thread Thread
danlebrero profile image
Dan Lebrero

I am with James.

I just published Error budget: Google's solution for innovating at a sustainable pace that explains how do you know if you are going too fast.

A couple of tools that you may also want to take into consideration: