Late spring must be NGO season for Plone.  Following hot on the heels of Oxfam GB's very successful Ploneability  Plone for NGOs mini-conference, Matt Blair, Humaninet's Chief Plonista, has written at length about his experiences implementing Plone as a collaboration tool for Humaninet's internal and external project teams. 

There's a lot of great feedback in these documents, covering both the general usability of Plone, as well as features specific to intensive team collaboration.

Matt's also written a very practical guide to evaluating third party Products for Plone, which contains a ton of hard-won wisdom, a simple explanation of Humaninet's custom workflows (a great example of this powerful feature in a real-world situation), and some interesting thoughts about Plone's unsuitability for multi-author real-time collaborative document editing.  (Which is a darn hard problem, I might add, which no open-source CMS solves very well. Yet.)

Matt's writeup deserves a much closer look than I've had time to give it, but one thought that occurs to me right off is this: a bunch of his needs and frustrations seem to revolve around's Plone lack of built-in document versioning and rollback.  I'm surprised that he didn't give CMFEditions a whirl, which on the surface seems like it's exactly what he needs, and was sponsored in large part by a fellow NGO, Oxfam GB, who presumably are using it for similar use cases.