"Big" or "small" software is relative to the problem at hand. The essentially author posits that "big == tightly coupled", which doesn't have to be true whether the team uses agile or not.

I think the real thing that the author denounces is blanket statements like "this project will be big so we must use Java" without really thinking about the project's potential structure or the best language.