What's the right amount of test coverage? Test Coverage and Post-Verification Defects: A Multiple Case Study](https://onedrive.live.com/redir?resid=493B8BCE8FC1C3DA!26920&authkey=!AFbVeq8YcyR0jDQ&ithint=file%2cpdf) provides some insights. Interestingly, they find:

that the test effort increases exponentially with test coverage, but that the reduction in field defects increases linearly with test coverage.

In other words, it takes more and more effort to reduce field issues. Based on their study most of the benefit accrues up to around 80% code coverage.

Scrum resources:

1. The Scrum Guide
2. Scaling Agile at Spotify

I still don't get why "scrum" is an appropriate name for the methodology. I

1. Bad Agile (from a Googler's perspective).

44 engineering management lessons from a co-founder of rethinkDB → http://www.defmacro.org/2014/10/03/engman.html

organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations

—M. Conway in How do committees invent Datamation magazine, 1968. There's a PDF version with the original layout but with bitmapped fonts.

http://www.melconway.com/Home/Conways_Law.html http://en.wikipedia.org/wiki/Conway's_law

A primer about technical debt, legacy code, big rewrites and ancient wisdom for non-technical managers

PDF of medium post

See also http://blog.ionelmc.ro/2014/08/14/the-three-sins-of-software-development/