One thing about Kanban and similar project noticeboards, they are a complete "big picture" of a project.  And they work a hell of a lot better than relying on Chinese Whispers to move important project information.


Another tool I've heard mention of is use of project wikis to collect project info - this would be ideal for my current project where we're all spreadout.  Anyone any experience of setting one up?

Views: 220

Reply to This

Replies to This Discussion

An option you can explore is Media Wiki

I used it to set up a project wiki,some time back and is "fairly" straightforward to set up and admin.




We also use MediaWiki.  Richard's comment below about the formatting is true, we have trouble with less technical people using it.  However, it's not that hard to link to the SharePoint site for non-techinical people's documents, and it's not hard for them to put links to our wiki pages in their SharePoint documents - so this really isn't that much of an issue.

We use SharePoint.

We create a new Folder for each Project.  All documents for the project go into this folder or a sub-folder.

You know what - we have SharePoint, but everyone hates using it ... meaning no-one uses it.

That's the biggest challenge with any new system - getting people to use it!


Could try looking at PBWorks, SocialText, Google Sites, Wet Paint, Confluence, MediaWiki....

Yup.  A tool that people hate isn't likely to be useful.


Do you know why they hate it?

Is there a way to make it less hateful?

And what could make a project wiki less hateful than SharePoint in your shop?

Mediawikki  has a drawback in that need to learn the formatting language, its ok for the techies but some stake holders wont like it.

The suite of google applications is useful in this regards its very user friendly but I think they claim some ownership of the data so not great if you have signed an NDA.

Macromedia contribute had a nice WYSWIG for users and was easy to set up. The data is kept locally so is secure as you want. I'm not sure about the licencing  since the Adobe merger. It was inexpensive.






We use JSPWiki at our company (although not for testing or even our department exclusively - it is used by the whole company) and it's pretty useful for lots of things. The main problem we have with it is that it's another resource which people need to update when things change, and sometimes it gets left behind. It then becomes a hinderance, as people consult it and get 'old' information.



© 2017   Created by Rosie Sherry.   Powered by

Badges  |  Report an Issue  |  Terms of Service