I have chosen Basecamp as my tool to manage the project of “Puttin’ on a Show” and to collaborate with cast members, volunteers and other interested parties. My reasons for choosing Basecamp are as follows:
- Minimal learning curve
- Web-based – all you need is a web browser and an internet connection
- Minimal cost – starting at free and easily upgraded if necessary on a month to month basis at reasonable rates
- Incorporates project tracking capabilities
- Milestones
- Tasks
- To-do lists
- Calendar
- Encourages and facilitates collaboration
- Message Board
- Chat
- File sharing
A simple blog or wiki would have allowed me to collaborate and share files with my users. But, it would not have given me the project management tools that are necessary and critical to this project’s success. I could have chosen to use a well know project management software package such as Microsoft Project, but it would really be overkill for this project.
I have read and listened to a number of user reviews and the only negative reviews have been that the software doesn’t have functionality that I do not require for this project. I also checked this out for my earlier class Web 2.0 review and found it to be very simple to use and to have all the pieces necessary to support this project.
The company that developed Basecamp is 37Signals. They are a small, privately held company founded in 1999. They claim to have 1,000,000 users on Basecamp.
Since this is a hosted site, software updates are maintained by 37Signals.
The user community (those involved in the show) are responsible for contributing content to the site. I foresee a core group of users creating milestones, tasks, to-do lists and communicating needs for such things as sets, props, costumes, box office needs, etc.
Individuals can be setup to have access to the project and to receive email notifications and/or RSS feeds. However, the number of people that I see subscribing to a project’s RSS feeds would be limited to a few core users. (Not everyone would be interested in being notified of changes to the project as a whole.)
Once individuals are setup as users their access rights can be specified. If it becomes necessary to further restrict access to individuals, multiple projects could be created and users assigned to only the project(s) that would directly relate to their responsibilities. In other words, permissions could be tailored in more detail if necessary.
A statement taken from the 37signals website sums up my reasoning for choosing this application. “We aim for the software sweet spot: Elegant, thoughtful products that do just what you need and nothing you don’t.”
Thanks for choosing Basecamp. We hope you like it.
By: Jason Fried on August 9, 2007
at 1:41 pm
Diane, Basecamp sounds like a great fit for your needs. I’m really glad you’re adding the “software sweet spot” quote.
Good job giving us a background of the folks at 37signals. They’re design heros of mine. Not only are the using an emerging technology, Ruby on Rails but they have an approach to design that I agree with. Check out their blog about design and usability, Signal versus Noise.
I love even the name of their blog. In the age of information, the ratio of Signal to Noise is a key issue. All the blah blah blahgs out there sure make a lot of noise, without really saying anything significant.
By: krichter on August 9, 2007
at 6:36 pm
However, one thing that worries me is that you won’t be able to upload pictures to the site. That’s often a key thing for the users. They want to “see” something when they get to a site. Too much text may be overwhelming.
Do you have other webspace so you can upload them there, then show them in basecamp?
By: krichter on August 9, 2007
at 6:39 pm
You can control which page the users go to first. To-do, Messages, whiteboard? Milestones?
By: krichter on August 9, 2007
at 6:41 pm