Recent posts in this topic
I've been wondering this since first trying Basecamp: what is the value of Checklists? I just don't get it... It only seems to complicate things and make it more tedious to setup and visualize a project.
All I really want is a set of Milestones with end dates and a list of tasks for each Milestone. I think this has been the classic approach for every project management system i've ever tried (and there have been many) until Basecamp invented the To-do list.
When I'm looking at a project, I'd like to see a set of milestones and then be able to drill down in one click to see the tasks. Or better yet, click to expand all tasks displayed below each Milestone.
Can anyone give me an example of how Checklists make your life easier? And if they weren't there, how would it make your life harder?
Any and all feedback would be appreciated and help me maintain my sanity. ;-)
All I really want is a set of Milestones with end dates and a list of tasks for each Milestone. I think this has been the classic approach for every project management system i've ever tried (and there have been many) until Basecamp invented the To-do list.
When I'm looking at a project, I'd like to see a set of milestones and then be able to drill down in one click to see the tasks. Or better yet, click to expand all tasks displayed below each Milestone.
Can anyone give me an example of how Checklists make your life easier? And if they weren't there, how would it make your life harder?
Any and all feedback would be appreciated and help me maintain my sanity. ;-)
Ilija Studen
on Feb 19. 2008. 12:55 am
Some milestones are just big. Try imagining a software release with 10 major features plus polish all over the place.
We don't use checklists, but we use tickets (similar, but more powerful concept available in Corporate version). For instance, in "activeCollab 1.1" milestone we have "Project templates" ticket. Complex tickets such is "Project templates" are than broken down into series of subtasks and completed step by step. Checklists can be used in a similar fashion.
We don't use checklists, but we use tickets (similar, but more powerful concept available in Corporate version). For instance, in "activeCollab 1.1" milestone we have "Project templates" ticket. Complex tickets such is "Project templates" are than broken down into series of subtasks and completed step by step. Checklists can be used in a similar fashion.
activeCollab team member
Maybe my presumption is wrong but my understanding of the intent of Basecamp (and presumably aC) is that the focus is on simple project management (vs. complex management of very large projects).
So in my business, I will have lots of active projects. However, most of those projects would look like 6-10 milestones with 2-8 tasks for each milestone.
So what would be the recommended way to set this kind of project up in aC?
So in my business, I will have lots of active projects. However, most of those projects would look like 6-10 milestones with 2-8 tasks for each milestone.
So what would be the recommended way to set this kind of project up in aC?
Brian:
So in my business, I will have lots of active projects. However, most of those projects would look like 6-10 milestones with 2-8 tasks for each milestone.
So what would be the recommended way to set this kind of project up in aC?
Get the corporate version, make the milestones, then use tickets as tasks.
www.synergetics.be | www.davor.be
Ilija Studen
on Feb 19. 2008. 10:08 am
There was no assumption on size of projects when we designed activeCollab. It works for both quick, one week projects as well as for long, almost never-ending projects (for instance you cannot complete software product project because there are always new versions, improvements, enhancements, feedback). We haven't completed a single project in our own setup because all of them are ongoing and will be open for a long time.
If your projects are simple maybe you could use checklists for some of them instead of creating a new project. Task inside of the checklist support due dates and priorities so milestones may not be required.
Also, a friend of ours uses tickets as subprojects. Every tickets is a little project with discussion area, attachments, subtasks, email notifications and so on.
If your projects are simple maybe you could use checklists for some of them instead of creating a new project. Task inside of the checklist support due dates and priorities so milestones may not be required.
Also, a friend of ours uses tickets as subprojects. Every tickets is a little project with discussion area, attachments, subtasks, email notifications and so on.
activeCollab team member
I very much appreciate your feedback and suggestions. I would really like to make this work. But I still have some difficulty...
Ilija - Using a checklist as a project means the project is not assigned to anyone. So that's a problem.
Davor - Using Tickets as Tasks seems to be much more workable but I have a little difficulty upgrading to a $400 product only for the purpose of beling alble to perform a workaround.
I used to think I was a pretty smart guy but this I just don't get. What is the concept of a "Ticket" supposed to be? I was originally thinking Trouble Ticket but now I'm not sure. Using it as Davor suggests, Tickets really become tasks, and Tasks become subtasks. Which makes sense... But why Tickets and why do I have to buy a $400 product to get this?
As it is, I think my clients will find this a little confusing and one of the primary objects I have for this is to provide a very simple interface to clients so that they/we can keep track of what they are responsible for.
I would much prefer if I could just assign Tasks to a Milestone or a Checklist. Is that not possible Ilija?
Ilija - Using a checklist as a project means the project is not assigned to anyone. So that's a problem.
Davor - Using Tickets as Tasks seems to be much more workable but I have a little difficulty upgrading to a $400 product only for the purpose of beling alble to perform a workaround.
I used to think I was a pretty smart guy but this I just don't get. What is the concept of a "Ticket" supposed to be? I was originally thinking Trouble Ticket but now I'm not sure. Using it as Davor suggests, Tickets really become tasks, and Tasks become subtasks. Which makes sense... But why Tickets and why do I have to buy a $400 product to get this?
As it is, I think my clients will find this a little confusing and one of the primary objects I have for this is to provide a very simple interface to clients so that they/we can keep track of what they are responsible for.
I would much prefer if I could just assign Tasks to a Milestone or a Checklist. Is that not possible Ilija?
Ilija Studen
on Feb 19. 2008. 1:07 pm
Brian:But why Tickets and why do I have to buy a $400 product to get this?
When we were designing v1.0 we needed to make a distinction between what is now task (a single task in context of something bigger) and higher level tasks (what is now ticket) so we ended up with these names. Now that v1.0 is out and we received a lot of feedback we might revisit this decision, but it's how it is for now and it cannot be changed.
For $200 you are not getting just tickets. Modules such is calendar, pages and time tracking (and some that we'll introduce in the near future ;) are also included. Any price is questionable, but we are convinced that these components together (we don't sell them separately) offer a great value and are worth at least $200.
Brian:I would much prefer if I could just assign Tasks to a Milestone or a Checklist. Is that not possible Ilija?
We might consider it for future releases, but it is not possible at the moment. Sorry.
activeCollab team member
Thanks for your reply Ilija.
With all due respect, this feels like you are selling a car with three wheels and in order to get the fourth wheel, I have to buy an upgrade package that includes leather seats, navigation system and convertable top. ;-) Bells and whistles that I don't need and twice the price.
I think $200 is a fair price for what I need but $400 is pretty far out there. For 15 active projects, this makes you almost 40% higher than Basecamp.
Here's a quick fix: Put Ticket support in the $200 edition and take out Checklists. Put Checklists in the $400 edition since, as you've said, they are there to support larger projects.
I would also consider changing the name of Tickets to Tasks, and Tasks to Actions or Subtasks. Lastly, if you put the Tickets (now called Tasks) as hyperlinks beneath the Milestones in the Milestones page, it would be perfect. ;-) What do you think?
With all due respect, this feels like you are selling a car with three wheels and in order to get the fourth wheel, I have to buy an upgrade package that includes leather seats, navigation system and convertable top. ;-) Bells and whistles that I don't need and twice the price.
I think $200 is a fair price for what I need but $400 is pretty far out there. For 15 active projects, this makes you almost 40% higher than Basecamp.
Here's a quick fix: Put Ticket support in the $200 edition and take out Checklists. Put Checklists in the $400 edition since, as you've said, they are there to support larger projects.
I would also consider changing the name of Tickets to Tasks, and Tasks to Actions or Subtasks. Lastly, if you put the Tickets (now called Tasks) as hyperlinks beneath the Milestones in the Milestones page, it would be perfect. ;-) What do you think?
Ilija Studen
on Feb 19. 2008. 2:41 pm
Brian:Here's a quick fix: Put Ticket support in the $200 edition and take out Checklists. Put Checklists in the $400 edition since, as you've said, they are there to support larger projects.
Sorry, we do not plan to do this any time soon.
Brian:I would also consider changing the name of Tickets to Tasks, and Tasks to Actions or Subtasks. Lastly, if you put the Tickets (now called Tasks) as hyperlinks beneath the Milestones in the Milestones page, it would be perfect. ;-) What do you think?
Thanks for the suggestion. Renaming some features might help newcomers (always a good thing) so we'll see what we can do about this. No promises at this point though.
activeCollab team member
OK, well I have to tell you that I have found this experience very troubling.
The truth is that the Small Biz edition of this product is pretty worthless without the Tickets support. That's because Tickets really means Tasks!! But to a new visitor to your website, Tickets means "Trouble Tickets". (Which would seem to make sense in a higher end version of this product.)
I find this to be very misleading advertising. Nowhere on your site do you even explain what you mean by Tickets and I have spent a lot of time needlessly fooling around with this when the reality is that the $200 version is unworkable and the product is really only viable at the $400 version.
I guess I have 2 or 3 weeks left on my 30 day return, hopefully I will cool off by then but I really am put off by gamesmanship like this.
The truth is that the Small Biz edition of this product is pretty worthless without the Tickets support. That's because Tickets really means Tasks!! But to a new visitor to your website, Tickets means "Trouble Tickets". (Which would seem to make sense in a higher end version of this product.)
I find this to be very misleading advertising. Nowhere on your site do you even explain what you mean by Tickets and I have spent a lot of time needlessly fooling around with this when the reality is that the $200 version is unworkable and the product is really only viable at the $400 version.
I guess I have 2 or 3 weeks left on my 30 day return, hopefully I will cool off by then but I really am put off by gamesmanship like this.
