Martin Kearn, on lessons learned with a Groove project
Lawrence Liu pointed me to a great post by Martin Kearn on Groove. Its a bit of the good, the bad, and the ugly about his experience using Groove on a project.
The whole thing is worth a read, but here is Martin's Conclusion
Groove does feel like a young product and lacks some of the key features that you take for granted with other Office products and especially SharePoint. There are lots of great collaboration features and ideas in the product and good integration with WSS 3.0, but you are often left thinking “if only it did X, Y or Z”.
Having said that, the fact that Groove is peer-to-peer and has no network dependencies has really paid dividends on this project as it has enabled cross-organisation collaboration for the whole team. This feature alone more than makes-up for Groove’s short-comings around collaboration features and Office integration. I really feel that collaboration would not have been anywhere near as straight forward without it.
I would certainly look to use Groove again on future projects and if the “What I’d do different next time” learning’s are observed, it makes for a great tool to help run small project teams and I’d recommend it without hesitating.
Link to this Article: