To Wiki or not to Wiki
I implemented a
FlexWiki test site at work recently with a view to suggesting that we use it as a central location for keeping bug tracking information, release notes etc - something to replace those mental and 'post-it' type notes that are made on projects and soon lost or forgotten. Sometimes we make design descisions etc and then six months later when the project gets implemented :-P - we forget why we made them. I thought this might be a nice tool to help with that. I am still undecided myself as to it's usefulness.
These were my bosses comments:
"The place for release notes is with the project - please ensure that is happening. If you wish to store it, additionally, anywhere else thats fine. Similarly, anything to do with a project belongs with the project.
If one can go to the trouble of creating/placing stuff in a wiki it means that one could go to the trouble of ensuring that the project had it in the 1st place...if it wasn't there then it indicates a lack of disciipline so regardless of where it sits it won't happen."
Does anyone have any comments they would like to add to this? Do you use Wikis at your place of work? What is your feeling on them?
Any comment appreciated...
(Anyone who is currently thinking Wiki? huh? Should start
here)