Somewhat orthoganal list here. That top 10 is almost all about "release frequently and test exhaustively and have well understood requirements." The linked article is all about "sleep and be healthy and work sustainably." You can be healthy happy and productive and ignore tests; or stressed and unproductive and write shit tests against shit requirements.

The linked article is about productivity and code quality. This list is about defect density, which is one aspect of code quality. It does not address everything in the article, but it does remove the mystery and common misconceptions of that one aspect.

That's very interesting, I just loved how she couldn't discover the impact of Agile because nobody she looked was doing it right.

That tracks with my experience. Or certainly what I hear others say of their experiences. I've struggled and had what I believe to be a fair amount of success with Agile methods in many ways over the last 20 years. What shocks me is how few folks I talk to have similar stories.

Edit: clarification.

Just to be clear, she didn't test for it because no two people were doing the same thing when they said they did agile.

Her data fits my experience. Your comment seems to reflect a different thing, that may not even be incompatible with that, just not very related.