It’s a privilege to join the team of bloggers here on Collaboration Loop. I consider myself a collaboration practitioner; I work for Novell as a Senior Knowledge Manager, responsible for the company’s collaboration architecture and infrastructure. For the last two years, I have led a project to help Novell understand its employees’ collaboration requirements and determine what infrastructure would best fulfill them, and to establish a collaboration infrastructure at the company -- one that will give us a strategic advantage over our competitors. My work has included documenting requirements and processes, creating a collaboration architecture, conducting a gap analysis of our current collaboration systems, working to secure executive funding and commitment, getting internal organization's commitment and alignment, conducting a request for information that was sent to thirty six collaboration vendors, conducting several pilots, and selecting a system. In this, and future blogs, I will share my experiences with you.
Let me begin by sharing what I learned from my research on asynchronous team-based collaboration solutions. My evaluation focused on enterprise requirements for these systems, and therefore my analysis is biased towards enterprise IT management. Some of the most popular vendors in this space include Akiva, Alfresco, Basecamp, Drupal, Mayflower, OpenACS, phpCollab, Ramius, and Xoops.
In order to better evaluate these products, I broke them down into three categories: