Our use of Open Atrium
One of the main problematic that arises during a project is "How can we keep track of all the information from the start until the end". Who never had an inbox full of threads, a succession of email containing changes in a document that is referring to another thread of mails, or have to dig in the mailbox to find all the necessary documents for a newcomer.
The solution to this issue, and many more, is a collaboration tool. We tried different solutions like, for example, Redmine, which ended up being too technical to be used as a true project management tool (we however kept it as an internal tool for tickets tracking on some projects). We developed our own Drupal based platform at some point; Ren. We finally sticked to Open Atrium from the Development Seed folks. The basic built-in features (Blog, Case tracker, Notebook, Calendar, Shoutbox and Dashboard) allow us to have a single place to store all of our documentations and keep discussions organized.
As we started to use it, it was clear that its feature set could go beyond straight project management. As of now we use it;
- As a project management tool, by creating a group per project and communicating with the customer only via the platform. This ensures that no information is lost and is available at anytime to anyone who is part of the project (thus the group). This is where we also share the project estimate, discuss the features and provide updates to the customer.
- As an internal communication tool, by creating a common pool of documentation on processes, keeping track of holidays, get reminder for employees birthdays or discussing projects ideas with our employees. We actually go down to the most common tasks are buying new pencils or filling in the fridge (developers tend to have a high consumption of sweet drinks...).
- As an administrative tool, which access is limited to the management team, were we share sensitive information and coordinate marketing campaigns. As our management can have period of intensive trips (Ronan just came back after a 4 months business trip around the world: USA, Sudan, France, Denmark...), it is useful to have all the information related to the company accessible from anywhere at anytime.

Open Atrium ended up being a collaboration tool more than anything else and we use it in all steps of our project as well as our internal discussion. Its flow is indeed very much in synch with our Agile methodology, letting us work asynchronously: another important factor for projects with teams scattered around the world. This was key to the success of projects such as the one we led on the Southern Sudan Referendum's voting infrastructure were the team was divided between our office in Shanghai and Juba, Sudan.
On top of this, we use a range of SaaS such as Google Apps, Github; we'll probably get into the details of that setup in a future post.
Using such a tool on our project work usually requires us to the take time of educating our clients, but that investment ends up being invariably a huge gain on both sides of the table; it provides a very high transparency of our internal processes to the customer and let him get involved graciously with our team.
In a nutshell, Open Atrium is an awesome Swiss army knife; we'd recommend you to give it a try and can't remember the number of clients we got switch over to using it as their own intranet.
Comments
I am not sure regarding Sharepoint, however we've already been asked to integrate this with Alfresco several times and it works pretty well; there are plenty of resources online, including screencasts, just Google it or search for Alfresco on Drupal.org.
Hello,
we use open-atrium ourselves as well. What we currently try to work out is to find the best approach for client communication. Do you let your clients post things directly in your open-atrium? And how do you make sure that the information they provide is structured correctly.
Currently we put the product backlog in the case tracker and only let them post things there. But this ends up in having a number of different discussions in the same case-tracker issue.
If we let them communicate via for example blog posts then we get a lot of different discussion threads at the same time and eventually there are so many blog posts that you cannot keep track of everything and eventually you can't find the information you need anymore.
Best regards,
Johnny van de Laar
Lead Engineer @ www.internetunlimited.nl
Indeed, this is a problematic we face pretty often; you should not expect your client to get the way to interact with it on their own. We usually go through a fair amount of "client education" if you will in the first few weeks of our projects before they know how to leverage Open Atrium and our agile development.
At least from our point of view, doing so would mean losing the value of having the client involved in our process and working as a member of the team; letting him go wild in a separate group just does not solve the core issue and does not help us collaborate.
Open Atrium actually handles it nicely; we've been using the email integration you are describing since we started using it. Have a look at the thread about the Reply by Email feature; everything is shipped by default with Open Atrium, you just need to enable it.
As for Redmine and ProjectPier, which I am familiar with as well (I had been using it since before the fork from activeCollab), it is more a matter of usability and focus; while both very decent solutions for bug tracking and regular basecamp-ish project management, I feel like Open Atrium fully embodies our approach to leading projects by fostering collaboration. In a nutshell, Open Atrium happens to better translate our agile approach than these two other solutions.
That being said, we are only talking about software here; you need to find what works for your team and be aware that technology can't solve people problems. Educating your team to properly interact with each other through the tools you chose is, IMHO, more important than finding the "perfect solution".
We actually don't really try to make Open Atrium work as a CRM; while we still keep some customer related information (like contact information) either in our "Administration" group or the customer's projects groups, we still rely on other tools to track clients. To be honest, we haven't found the perfect set up yet; we gave a shot at Highrise and SugarCRM but did not stick with it. For now, we use a combination of Rapportive, Dropbox and things like Boomerang (Quentin wrote a post about some of this a few days ago). We feel like there is indeed a gap here, but use Open Atrium only for what it is good at; team collaboration.
Add new comment