...

Information workers handle different kinds of information. But for software project we often work with the same set. Architecture decision, work instruction, contract, interface documentation, patterns, stakeholder description, codes, test plan, build plan, persona, user story, use case, meeting minutes, and so on and so on. Well, this set is quite large. Not every artifact is be a document in a wiki. It may be a bug report in a issue management system or an executable test case run on a continuous delivery server. In case a document is actual to be created to provide a given information, there is no need to reinvent the wheel for each document instance. Templates leverage the organization of the actual information. Team members should fetch the most appropriate template for the communication task at hand, add the information in a form their readers expect and push it to a location where interested parties can find it easily. This is about concentrating on the readers' demands and their expectations.

...