Wikis are a great collaborative tool for developing a knowledge base, but what about meeting the requirements for standard hard copy type deliverables? This is the issue that I am currently running into in my organization. It is hard to be both agile and meet organizational requirements for deliverables.

In my organization we have a group of folks that must review deliverables for compliance with government reporting guidelines. These reviewers do not have access to the wiki, but yet must somehow review it. This means that the review consists of printing hard copies, of what is essentially a living document in an online environment. It is just not the same experience.

I found an interesting case study report called "Using Wikis in Government." While this presentation is focused on customer-facing wikis or internal knowledge bases, my project is more concerned with producing internal test plans and deliverables to meet requirements.

I'm not sure how my organization can evolve to a purely paperless and collaborative workspace, but for now we are still being required to produce a paper report. I am curious to see what expertise is out there on this topic, and I am continuing my research.