browse-3The Tech team needs to document its work for the purposes of being able to understand the who, what where, when, why and how of key decisions, key events and key non decisions and non events. What did not happen is as important as what did happen. This section discusses and defines how best to document code, instructions, lessons learned, helpful hints, processes, decisions, testing and validation, and problems to be solved. How we document needs to be painless, embedded in our systems, and truly useful. Contribute your experience and preferred approaches to documentation here.


by Systémique

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>