Use case – Effective Project team collaboration
There are numerous tools not only for project management, but also for project team collaboration. But when I look at well regarded tools like Basecamp or Projectplace, it amazes me how they regard conversations as a separate artifact or category along with to-do’s, documents and the likes. That is not natural. Conversations or discussions is an integral part of any project work and should be a function of any project artifact on any level.
Any results, content or intelligence the project team produces is achieved with collaborative effort, and the tool should reflect that. So anything need to be discussed and developed together, from requirement phase all the way down to delivery and project close. And the real value is that it is all recorded and can be followed/traced. This is the more impsortant today when results are reached applying agile methods, where emergence and continuous improvement is the norm rather than comprehensive upfront specifications.
I would say that a natural project team collaboration tool should look more like this:
Isn’t this a lot more natural? It’s the task/issue/case that is in focus and everything plays around these and all is connected/linked in a natural manner.
This follows the (also natural) pattern of case focus outlined in To make the knowledge worker productive