Office 2.0 Feature Tracker
Tuesday, July 25th 2006 | Ismael Ghalimi
The Diigo social annotation and bookmarking tool was formally launched today. I won’t go into the details of this release, for my friend Brian Benzinger has done a much better job than I ever could, with one of his usual thorough reviews. What I would like to focus on instead is how service providers such as Diigo manage to quickly release features requested by users.
Back in January, I requested a version of Diigo that would work without any browser extension. Six weeks later, the good folks at Diigo released a working implementation, and this experience became the first instance of a successful request/release process for advanced Office 2.0 features.
I very much like working with solutions for which I can have an input in the development process, and the more reactive the provider, the better. In this respect, I believe that companies like AdventNet — the Zoho folks — have set the benchmark for the industry.
To keep track of such developments, I compiled an Office 2.0 Feature Tracker, similar to the Office 2.0 Bug Tracker. The feature tracker is essentially a log for features that have been requested on IT|Redux, and have been later released by the vendor, or are still waiting for a release. As usual, the whole thing was developed with Dabble DB, and various feeds are available (CSV, JSON, RSS).
If I forgot a feature that I requested and was later released, drop me a line.
Entry filed under: Office 2.0
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Ismael,
Last year I worked with an application called Groove which was developed by Ray Ozzie. As you know, Ray and his company were absorbed into Microsoft, and the rest is history.
It seems to me that Groove could (have) be(en) a candidate for Office 2.0, with very strong project management tools such as Gantt charting and critical path management developed by a company called TeamDirection.
Most of the current Office 2.0 applications call themselves “project management” tools, but even though sophisticated and powerful, their functionality is more that of a to-do list with collaboration features. Basecamp is a good example.
Finally to my point — Gantt chart and critical path functionalities are key to a good project management application, and maybe we should enter them as a feature requests for the Office 2.0 project management applications in your database.
Just a thought,
-Ryan
Ryan,
I totally agree with you.
Which project management application would you like it for?
Also, would anyone know a way to get in touch with Ray? I’d love to invite him to speak at the Office 2.0 Conference. Microsoft CEO Steve Ballmer recently said that software is becoming a service, so I would think that Microsoft’s participation could add a lot to the event.
Ismael:
How about Basecamp for starters?
Ryan
Office 2.0 services lack collaboration and integration schema & platform. This is the main problem as I see it. On your Web 2.0 (Office 2.0) watch one can see many great applications, but without proper integration it’s just another Web application in the pool.
Long live RDF & Semantic Web!
Office 2.0 — Ismael, the name by the way does not reflect the versatility and functionality of the services. Along these lines, here is a great Web 3.0 article by Jeffrey Zeldman.
Zoho Writer — Putting it to the test!
Seeing as how Arvind of the Zoho Writer team…
Trackback this post | Subscribe to the comments via RSS Feed
Leave a Comment