#120 Wiki, KB, Task Cost, Portal

open
nobody
None
5
2015-03-26
2010-04-03
KoPoJIb
No

I am organising football tournaments (using webcollab for 4 years). In my opinion, we should think how to retain, classify and capture knowledge. On my experience, regardless time you spend to train your members, projects end up being huge place for rubbish, where everything is chaotically put in different levels of tasks. I tried to switch over SugarCRM and Vtiger but it became even worse as those are too complicated. However, they have a very good sense of structuring information. Based on my experience, I would like to propose few features:

1. Webcollab must have a WIKI to store documentation, procedures or any other material which derived from project experience.
Reason: after project is finished, it needs to be closed and lessons learned required independend page which can be accessible outside projects.
2. KB. Each task should have an issue/case section. This should be then converted into independent KB article.
3. Each task should have a cost which is then automatically generate overall cost of project.
4. I am also working with external customers (like councils and sponsors). Instead of sending emails, I would rather give them access to case or tasks so that they could use portal to publish their information on my tasks.

Thank you.

Discussion