Hey guys,
Within our organisation we have a Wiki to capture Developer/Tester/System knowledge, but it doesn’t seem to work well (probably the main reason for this is little buy-in).
What Wiki tool do you use for your development team? Do you use SharePoint or something like Confluence… and why?
Also, does anyone know what Wiki tool even the Microsoft Internal Development teams use?
Cheers.
It sounds as though buy-in is the issue and not the ability to create SharePoint wikis. I developed a System Administrator wiki for a client which works fine. I’m currently in the preliminary stages of another project which involves consolidating existing SharePoint 2007 documentation sites, wikid sites and ServiceNow knowledge base into a holistic approach.
During my preliminary needs analyses, I’ve discovered many of the developers and engineers aren’t familiar with either the existing SharePoint 2007 capabilities or the SharePoint 2013 features.
Although I’m still working on the scope of work for the project, I’ve started walking through the existing SharePoint sites with the team leads, showing them current features and functionality. My own buy-in issue is convincing the team to not collaborate by emailing documents to each other which is part of this project’s change management challenge.
If your organization has a corporate communications area and/or training department, I’d recommend partnering with them to address the change management portion.
I prefer to have the bulk of documentation managed by one program, particularly since SharePoint 2013 beefed up the social aspects. The client is going to continue to host some information on wikid that’s sensitive but the goal is to stop having so many different document repositories, eliminate duplication of effort and implement more formal document collaboration, control and review practices.
