对于一般项目管理，Base Camp 很好，但我们还发现我们有外部文档，其中保存了所有“真实”信息 - 基本上是多页规格，只是每隔一段时间将它们上传到 Base Camp。
I've been using BaseCamp for 2 years now and found it to be an excellent general project information portal. The ability to store documents, to-do tasks, and milestones with a living project view is pretty impressive.
Unfortunately their mantra of 'keep it simple' also has quite a few drawbacks in regards to capabilities:
the calendar is practically unusable for anything but the most basic of milestone tasks... to keep track of our dev team we actually pulled together a custom Google Calendar implementation and use it for all developers and their tasks
BaseCamp is pretty difficult to use for bug tracking once you get a fair number in there assigned to various people - the ability to sort is lacking (beyond just turning people on and off) - you'll be much happier with a full Bug Tracking solution such as FogBugz.
For general project management Base Camp is fine but we've also found that we have external documents where we keep all the 'real' information - basically the multi-page specs and just upload them to Base Camp every once in a while.
上次评估 Basecamp 时，我发现缺少一个功能，即查看多个项目的工作量或其他信息的能力。 例如，如果我想知道开发人员 X 是否有太多的事情要做，或者是否分散在多个项目上，我不知道该怎么做。
The last time I evaluated Basecamp I found one feature that was lacking was the ability to view workload or other information over several projects. For exmaple, if I wanted to find out if Developer X had too much stuff to do or was spread too thin over several projects I could not figure out how to do that.
For me the missing feature was the ability to store my development stories in a way that worked for me. I wanted a single template that I could use to generate every story and the ability to link stories together. Eventually, I ended up using a Wiki for this. I didn't really have any need for to-do lists or time tracking stuff (this is handled separately by a company-wide app).
It's hard to manage own documentation. Writeboards doesn't give you a good way of formatting your code and becomes unmanageable one you got more than 10 in a project. Message/Files gets messy if you got to many.
For me the missing feature was the ability to store my development stories in a way that worked for me. I wanted a single template that I could use to generate every story and the ability to link stories together. Eventually, I ended up using a Wiki for this. I didn't really have any need for to-do lists or time tracking stuff (this is handled separately by a company-wide app).
You can not export your files, they do not provide file api even.
So if you go out, you will get some work to take your files.
Recently I was helping a client to move 50 projects from Basecamp to Assembla. They said Assembla is better for project management and it has more features.
With Basecamp, we were unable to track time spent over our tasks, a task could not be assigned to multiple people, could not maintain secrecy over important matters, could not keep messages as private, faced difficulty in proofing designs, could not freely chat with members of our team. So we went with ProofHub. It has got timesheets, To-do’s, casper mode, private messages, proofing tool and an inbuilt browser chat. We are just fine with it.
I'm finding a big gap with Basecamp to be user roles. It's impossible to have people on a project (other than a "client") who can only see certain to do lists. I'd like to be able to allocated roles for freelancers so they only have access to certain task lists within a project.
发布评论
评论（9）
我已经使用 BaseCamp 两年了，发现它是一个优秀的通用项目信息门户。 通过实时项目视图存储文档、待办任务和里程碑的能力令人印象深刻。
不幸的是，他们的“保持简单”的口号在功能方面也有很多缺点：
I've been using BaseCamp for 2 years now and found it to be an excellent general project information portal. The ability to store documents, to-do tasks, and milestones with a living project view is pretty impressive.
Unfortunately their mantra of 'keep it simple' also has quite a few drawbacks in regards to capabilities:
上次评估 Basecamp 时，我发现缺少一个功能，即查看多个项目的工作量或其他信息的能力。 例如，如果我想知道开发人员 X 是否有太多的事情要做，或者是否分散在多个项目上，我不知道该怎么做。
The last time I evaluated Basecamp I found one feature that was lacking was the ability to view workload or other information over several projects. For exmaple, if I wanted to find out if Developer X had too much stuff to do or was spread too thin over several projects I could not figure out how to do that.
对我来说，缺少的功能是以适合我的方式存储我的开发故事的能力。 我想要一个可以用来生成每个故事的单一模板，并且能够将故事链接在一起。 最终，我最终使用了 Wiki。 我真的不需要待办事项列表或时间跟踪内容（这是由公司范围内的应用程序单独处理的）。
For me the missing feature was the ability to store my development stories in a way that worked for me. I wanted a single template that I could use to generate every story and the ability to link stories together. Eventually, I ended up using a Wiki for this. I didn't really have any need for to-do lists or time tracking stuff (this is handled separately by a company-wide app).
管理自己的文档很困难。 Writeboards 并没有为您提供一种格式化代码的好方法，并且当项目中的代码超过 10 个时，它会变得难以管理。 如果消息/文件太多，消息/文件就会变得混乱。
It's hard to manage own documentation. Writeboards doesn't give you a good way of formatting your code and becomes unmanageable one you got more than 10 in a project. Message/Files gets messy if you got to many.
任务估计与实际值是我注意到的一个大问题。
另外，能够将 tiem 标记为已计费将是它目前缺乏的一个很好的功能。
Task estimates vs actuals is a big issue I've noticed.
Also being able to mark tiem as billed would be a nice feature it currnetly lacks.
对我来说，缺少的功能是以适合我的方式存储我的开发故事的能力。 我想要一个可以用来生成每个故事的单一模板，并且能够将故事链接在一起。 最终，我最终使用了 Wiki。 我真的不需要待办事项列表或时间跟踪内容（这是由公司范围内的应用程序单独处理的）。
For me the missing feature was the ability to store my development stories in a way that worked for me. I wanted a single template that I could use to generate every story and the ability to link stories together. Eventually, I ended up using a Wiki for this. I didn't really have any need for to-do lists or time tracking stuff (this is handled separately by a company-wide app).
你不能导出你的文件，他们甚至不提供文件API。
因此，如果您外出，您将需要一些工作来保管您的文件。
最近，我正在帮助客户将 50 个项目从 Basecamp 迁移到 Assembla。 他们表示 Assembla 更适合项目管理，并且具有更多功能。
You can not export your files, they do not provide file api even.
So if you go out, you will get some work to take your files.
Recently I was helping a client to move 50 projects from Basecamp to Assembla. They said Assembla is better for project management and it has more features.
使用 Basecamp，我们无法跟踪任务花费的时间，无法将任务分配给多个人，无法对重要事项保密，无法将消息保密，在校对设计时面临困难，无法与他人自由聊天我们团队的成员。 所以我们选择了 ProofHub。 它有时间表、待办事项、casper 模式、私人消息、校对工具和内置的浏览器聊天。 我们对此很满意。
With Basecamp, we were unable to track time spent over our tasks, a task could not be assigned to multiple people, could not maintain secrecy over important matters, could not keep messages as private, faced difficulty in proofing designs, could not freely chat with members of our team. So we went with ProofHub. It has got timesheets, To-do’s, casper mode, private messages, proofing tool and an inbuilt browser chat. We are just fine with it.
我发现 Basecamp 在用户角色方面存在很大差距。 项目中的人员（“客户”除外）不可能只能看到某些待办事项列表。 我希望能够为自由职业者分配角色，以便他们只能访问项目中的某些任务列表。
I'm finding a big gap with Basecamp to be user roles. It's impossible to have people on a project (other than a "client") who can only see certain to do lists. I'd like to be able to allocated roles for freelancers so they only have access to certain task lists within a project.