Collective Wisdom from the Experts 51
• Meeting agenda. Set up a process for stakeholders to suggest future
agenda items online. Subject, of course, to the approval of the software
project manager, the necessity for the item to be presented to the entire
team, and the time limitations of the next meeting.
• Business analyst. Often this person is not colocated in the developer work-
space. This is a perfect space to centralize access to working documents and
domain artifacts that can be accessed from multiple locations.
• Testers. The organizational structure may separate testing responsibility
from the programmer. This site can provide a clearinghouse between the
two teams. Post topics like how to use testing tools such as Selenium, QTP,
and Quality Center. Bug-tracking procedures can be developed and dis-
cussed online, and the final decisions posted here.Some tips:
• Don’t duplicate information. If the information lies elsewhere, link to that
information instead of copying it into the wiki.
• Keep an eye on the volume of changes to make sure the information is not
getting stale. If it does, people will stop using the wiki.
• Try to make your information real-time-data–driven if possible. Look for
project management tools that include a wiki interface to enable creation
of charts and status that is driven from the actual project data. This gives
real-time status for the work in progress.Any time you send project information via email, particularly with file attach-
ments (documents, project plans, budget information, etc.), you should con-
sider whether the team wiki would be a more appropriate place to exchange
and archive that information.