Templated requirements and test plans. Fill in/extend the template to the needs of the project. In source,use project tag/ID for lines of interest. Sometimes

Templated requirements and test plans. Fill in/extend the template to the needs of the project. In source,use project tag/ID for lines of interest. Sometimes requirements documents explain more than the code or comments. IE: 12345_r.doc User needed X for 2012 tax reporting because of leap year due to the extra day in the year vs accounting's actual 30 day per month business rule. Comments/code would say something along the lines of '/* Project 12345 - Check for leap year */ if tax report and year eq mod4, bit shift left topic 2' It is outdated, but it works. Documents add accountability. Link in emails, project team, sign-offs, etc.