Nah, it doesn't pass the sniff test.

Is it more important than a list of critical bugs?

A document explaining how a developer can get the application up and running?

A document detailing how the production server is setup and how to gain access?

When you think about it, lots and lots of projects manage without any kind of glossary but would go up in flames without some kinds of documents.

I find glossaries quite often not very useful because they tend to get copy/pasted across documents and the acronyms are often just expanded without giving the correct meaning in the context of that document. I'd rather have it fully spelled at first usage, with the acronym in brackets. This enforces a more natural order of writing and reading the document and provides a better context.

Agree strongly. I think an even more insidious version of the parent comment is when common nouns that have specific meaning in a given context are used as such, without it being explicitly called out.

Agree. A glossary is a way to introduce a domain piecemeal, without a long-form explanation.

Please explain what ANY expands to...