Templating of technical specification in Agile development
A working product is more important than comprehensive documentation. This is the axiom given by the Manifesto for Agile Software Development.
But what should we do if we still want to tidy up the documentation on long-lived projects? The answer is templating!
But what about templating such a complex and unfathomable artefact as a technical specification? Where is the beginning of templating, and where is its end?
Let's consider various variations of solving this problem and offer our own methodology.