[tremon]

Of course it is possible with agile, it "just" needs to be properly prioritized. And that also means, in good Agile fashion, that documentation skills needs to be represented in the team. If you don't prioritize documentation and do not value technical writing skills, it doesn't matter whether if you use waterfall or agile processes, you will still end up with sub-par documentation.

Also, what kind of documentation? High-level design documentation? Low-level code documentation? Code structure reading guides? End-user manuals? Elevator-style sales flyers?

[j45]

Documentation in some ways is more of an important output than code.

Documentation serves to to create beginners with the source code and project.

When working with devs it’s made clear that what they are delivering is documentation of which working code is one part.

The ability to write sentences in documentation is as important as writing code.

Writing as one works (not after) and then editing is one of the only ways I’ve found that there is a chance, waterfall, agile or cowboy.