This pattern of forgetting things is getting dangerous (T minus 32 hours). One thing that I wanted to suggest is that storing your checklists, etc. in a wiki is also ‘acceptable’ from an Agile perspective. Ideally you want them right there with the source code, but a wiki has the advantage of being in the browser. And everyone has seen wikipedia by this point so is has at least heard of the concept of editing content.

If you are going to go down the wiki route, you need to make sure that it, at bare minimum, tracks revisions of edits and can disable anonymous edits (for auditing purposes).

You also want to provide templates for people to use when creating specifically purposed pages. The last thing you want is having 3 or 4 people each doing somethings slightly differently. (Thanks for Marlena for that tip.)

‘Gardening’ is the common term for cleaning up the wiki and time needs to be allocated to do it. Most often when gardening you are looking at adjusting the links between pages and the tags to find them. On this subject Chris says

Links and tags are devices by which to organize related information. The scheme by which you organize the information is up to you, but links and tags are how you manage the organization itself.

Chris also reminded me of something you want to consider with all your infrastructure choices – integration. Check whether your wiki has an API, and if so, start to wire them together.

Both Chris and Matt reminded me to mention that Fitnesse (one of the table-based BDD/ATDD tools) is really just a highly optimized wiki. (Random trivia – the Selenese syntax that Selenium-IDE uses was also a fork of FIT so has wiki heritage.)

Now what else have I forgotten in this series…