Glad to see I'm not the only one.
You've got your work cut out for you here; younger developers have grown up with games and channel surfing and most cannot finish reading a book, and creating documents will forever be beyond them.
I've written the first spec the company had ever seen at many jobs and I regard documentation as essential; it does not help when idiotic fads like Agile counsel that social skills are more important, and that documentation is obsolete.
The immediate goal should be to unconditionally requires that all on a project read its documentation, at least at the Requirements level. It is as much a responsibility as the nominal tasks.
The argument that documentation constrains the project is a contemptible excuse; yes things change as we develop, that's what revision-marking is for. I saw no mention of this in your article.
Edit: you're wrong. Software developers damn well better get paid to write documents; I do, and have been since the early 1990s. It's part of the job. Managers who come from the MBA world don't understand functional documentation; they should be able to read it but they won't write it.
Since I don't like what the industry has turned into with the advent of these methodologies I am now more often actually working under the job title Technical Writer; such jobs are much easier to get, managers don't shrivel up at my time zone and their developers can't write more than a tweet.