Troy asked for an update on our use of Basecamp.
Yes, we're keeping it. It's a bit like "project management light", but this is definitely what is wanted if you don't want to get bogged down in updating some sort of tool, but you do need something to organize multiple people and multiple projects that are going on in parallel. Hit the read more link for the full story.
Basecamp facilitates keeping communications about a project all in one place by the use of messages, which can be:
Before moving on to milestones, let me briefly mention files. They have their own tab with which you can upload files directly without attaching them to a message, but the most common use is to associate them with a message.
Files are actually stored on your server, not Basecamp's, which neatly does away with the problem of storage space -- you're free to upload as much as you want, as long as your system has space. This is accomplished by setting up FTP details in the Basecamp system, so that when you upload, you're actually uploading to your own system. For less technical users, this might be a bit of a barrier, but FTP is generally very easy to set up and virtually every web host supports.
They don't currently offer SFTP or WebDav support, but are considering them.
Milestones are the only "dated" item in Basecamp. We use it to track "real" milestones -- when stuff is due, is going live, etc. -- as well as other dated events like meetings. This allows some very easy shared calendar, although specifically focused on projects (it won't show you that the boardroam is booked at 2pm, and in fact doesn't use time at all -- only dates).
As mentioned, messages can be associated with milestones. When creating a message, you can opt to select the project milestones from a drop down list, and then a link to the message will show up organized underneath the milestone. As well, there is a checkbox listed as "This message completes this milestone", which is a good way of giving a description of how the item was completed without having to separately go and check off the milestone.
As well as being the only dated item, milestones are the only item that can be made the responsibility of someone directly. You can choose to make a company (e.g. YourCompany, YourClient) responsible, or you can choose one person.
To do lists are the third major item in Basecamp. They can also be associated with milestones in the same manner as messages, although they cannot be used to (directly) complete milestones. They are very easy to create, consisting of a title and as many text-based items as you want. Since you can't associate a person responsible with a to do list or individual items, you can use several different strategies. You might have a shared to do list, like "Website Pre-Launch Checklist", that uses initials beside particular items. Or, you could title the to-do list to include a person's name.
This is a bit awkward -- I'd like the ability to choose to associate people (or not) the same as milestones. The text labelling seems to be working for now.
It does make sense that individual to-do items don't have dates -- if it is something that is required for a specific date, it should be a milestone.
Lastly there are contacts associated with projects. You need to have admin access to create projects and contacts (really, there are only admin users and non-admin users, although how contacts are set up does give you some additional granularity). As part of setting up Basecamp, you set up your company (of which you are obviously a member). Later users are then added as a contact at your company (where they can be listed as an employee or a contractor) or as a contact at a client company. Employees by default have access to any new projects you create (so you must uncheck access for them), while contractors must be manually given access on a per-project basis. Client contacts can only have access to projects which are associated with their company, and can be given read-only access.
So, while the different types of access are quite simple, in practice they tend to be rich enough. The one downside is that usernames are unique per instance of Basecamp. Most people wouldn't see this as a problem, but I am using the system in several companies, so have a different login for each instance. This could easily be solved by making users global, and by keying by your email address instead of a username.
There are two other aspects that I'm going to mention but not go into much detail about. RSS can be used to notify you of any changes -- this can be done on a per-project basis, or for your entire Basecamp instance. There is also iCal support, with one iCal per project that shows milestones in the calendar and the to-do lists as tasks. While it's called iCal like the tool from Apple, it does also work with Mozilla-based browsers. This includes the newly-released-and-too-early-to-use-seriously Sunbird, which is Mozilla's new stand-alone calendaring app, or the Calendar extension that works with the full version of Mozilla, Firefox, or Thunderbird on all platforms.
iCal on Mac OS X is the only system on which it's really easy to add a calendar -- I'll go into full setup details for the Mozilla's if people want.
And no, it doesn't integrate with Outlook. This is still the default email application on many users' desktops, even if they don't use an Exchange server. So I'm looking for an easy way to sync/integrate iCal into Outlook.
Whew! Well, that was more a description of the system than a review. We are happy with this "good enough" solution, and will continue using it. And I never did mention the elegant interface, but that's really the point -- it's good enough that it doesn't get in the way of actually using the system. Check the Everything Basecamp site for more information -- it's the "official news and support blog".
If our thoughts change, I'll post again. In the meantime, here's a link to a completely free one project plan -- with no 30 day trial and no credit card required. You can still upgrade at any time.
Comments
Community collaboration - real-time
We've recently started using youfig.com for project management and collaboration. In addition to task management, assigmnets, timelines, and so on, it provides us with the ability to collaborate on documents, spreadsheets, videos, etc. Highly recommended and worth a try (especially since they're not charging a cent for it).
I would agree that Basecamp
I would agree that Basecamp is OK for communication. In fact it was created with this idea in mind. "Project management is about communication" was one the creators' mantras. Well, I'd object and say that project management is about collaboration, and these two things are a bit different, don't you think? My team and I, we switched to Wrike http://www.wrike.com/. It's got some very useful "project management like" features. For example, you get an overview of your projects with a simplified version of a Gantt chart. Wrike is integrated with our inboxes and we email tasks to each other adding them to our development plan in Wrike at the same time. We also attach files or screenshots to our emails and they also get captured by the system. I don't know if you heard about it. If not than you should check the tool out.
working for wrike?
Is Lane working for Wrike?
Great idea! I should really
Great idea! I should really offer them my promotion services. Why am I doing it for free? I love the product, so why shouldn't I get payed for promoting it? Thanks for the tip!
No Search Across Projects
There does not appear to be a 'search across all projects' option. That is, if you are a member of multiple projects, you can only go into each project and search the individual project, then move to the next one. Ideally a search across projects would not be a drop-down (which would allow "All projects" then an individual projects) but rather a set of check boxes with the option to "Check all". So instead of the current individual-project-only search, and instead of a 'all or one' search, it should be a 'all, some, or one' search function.
Couple of nitpicks
The inability to assign a to-do list (or to-do list item) to a person registered on a Basecamp project is the one thing that differentiates it from a ticket system. It can be done manually, i.e. via a blog post--which can be automatically emailed to one or more people--but not assigned through the system. Also, there is no commenting on individual to-do list items. That would make it easier to say things like "yes, this is proceeding smoothly, should be done by tomorrow" or ask questions for clarification.
In the main overview of a project, the title of each item (be they milestones, comments, blog posts, or to-do lists) are cut off about halfway, with an ellipsis. It's a bit of a pain to have to click into something "Richard can you please get the..." (also, it only shows the last name of the person posting it, so if there was another person with the same name on the project...?). Overall though, it's a pretty slick system, very pretty, and makes effective use of Javascript. It's a system that strikes a nice balance between RSS and email: those who can and want to can subscribe to the project feed, and others who either don't understand the technology or are still more obsessed with their email account than their aggregator (like yours truly) will still get the notifications in a timely manner.
Assigning to-do items to individuals is coming soon
"The inability to assign a to-do list (or to-do list item) to a person
registered on a Basecamp project is the one thing that differentiates
it from a ticket system."
Stay tuned. I think you'll like what you see shortly.
Except now of course, we want
Except now of course, we want per-user RSS feeds of just their to-dos. Then they can monitor it for new items that other people assign to them.
As far as I can tell, you can only get per-project, not per user feeds.
(Here's hoping that Jason Fried comes back with more good news)
No Email Fridays
Roland Tanglao wrote at Bryght that tools like Drupal and Basecamp eliminated the need to use email internally. What's great about those tools is that they understand what we're going through is a transitional phase rather than a revolutionary one. Roland would argue that RSS is disruptive and revolutionary. He's right, but the vast, vast majority of Internet users still understand email and still use it, despite the spam problems, and the developers of Drupal and Basecamp understand that.
Weird... just a few minutes a
Weird... just a few minutes ago I featured Outpost on my site. It may help you import/export Outlook data.
Thanks, Fabian. From the look
Thanks, Fabian. From the look of it, Outport is focusing on export. The need would be for Outlook to support the import of iCal feeds. It is a common standard, so I imagine this will get implemented at some point.