What's so unique about it? Heard great things about it, used it, found that beside the Google Apps Integration there's nothing really special about it. Maybe I just don't get it?
So, what's your reason to use basecamp?
|
What's so unique about it? Heard great things about it, used it, found that beside the Google Apps Integration there's nothing really special about it. Maybe I just don't get it? So, what's your reason to use basecamp? |
|||
|
|
|
To me, the biggest draw has been the simplicity, which leads to flexibility. The concepts that Basecamp helps to manage are easily understandable, and there's very little configuration to worry about. (Have you ever tried to use a tool like JIRA? Even its configuration has configuration.) The simplicity starts to pay dividends when you are composing project teams of varying technical experience. The basic nature of to-do list items and milestones are easily understandable by most anybody. |
|||
|
|
|
I don't think there is anything wrong with it, but there are a lot of other ways to address the same issues. I also do not understand the love/loyalty it seems to generate with some users. Personally, it has never fit what I was working on very well, so I have never had a place to use it long-term. |
|||
|
|
|
I've used it a few times to organise groups for various aims and I would do so again. It's easy to use, easy to understand and it does stuff you need but not stuff you don't need. I just found it really easy to get along with. |
|||
|
|
|
It's a great way to centralize information on projects and to have a solid record of communication between users. It's also great if you are working with a distributed team. |
|||
|
|