How Tasks and Milestones fit together?
Page: 1
I realize that there is no documentation for aAC but is there an overview about how the system works once you get it up and running.
I am not a Base Camp user and am not interested in their offering and can't find much there anyway.
So is there a how to that exists anywhere?
I am not a Base Camp user and am not interested in their offering and can't find much there anyway.
So is there a how to that exists anywhere?
I'm not one for answering my own posts but I'm going to today.
Can anyone explain how the Tasks /Milestones processes fit together.
I can't get any logic out of the process nor can my testers.
Can anyone explain how the Tasks /Milestones processes fit together.
I can't get any logic out of the process nor can my testers.
Ilija Studen
on Feb 13. 2007. 10:35 am
Milestone can have multiple task lists (and messages BTW), task list can have multiple task. For instance, milestone Beta launch can have two task lists:
1. Prepare product with following tasks:
- build product using build tool
- package version for Windows
- package version for Mac
- test if whole process is working on Windows
- test if whole process is working on Mac
...
2. Announce beta version with tasks:
- write and post announcement on company blog
- upload packages
- update download page
- update releases page
- update homepage to show the most recent version
Milestone <> Task list relation is optional to give more flexibility to the system.
1. Prepare product with following tasks:
- build product using build tool
- package version for Windows
- package version for Mac
- test if whole process is working on Windows
- test if whole process is working on Mac
...
2. Announce beta version with tasks:
- write and post announcement on company blog
- upload packages
- update download page
- update releases page
- update homepage to show the most recent version
Milestone <> Task list relation is optional to give more flexibility to the system.
activeCollab team member
And a milestone can have many tasks under it. Milestones probably should be broader than tasks.
For example, for a web design project, you would probably have these milestones:
1. Design Concept/Creative Brief
2. Execute Design
3. Execute Layout and Backend
4. Local Testing
5. Deployment
6. Testing on Live Site
7. Project Closed
And within each, you would have several tasks and subtasks. At least that's how I'm using it currentlyl. :-)
For example, for a web design project, you would probably have these milestones:
1. Design Concept/Creative Brief
2. Execute Design
3. Execute Layout and Backend
4. Local Testing
5. Deployment
6. Testing on Live Site
7. Project Closed
And within each, you would have several tasks and subtasks. At least that's how I'm using it currentlyl. :-)
Topic is locked. If you have something important to say about issues discussed on this page please write at hi@a51dev.com.



