Quote:
Originally Posted by amg
- If a project has 5 actions, sequencial by default : why can I put a date on the project ? Shouldn't that be a field to be taken from the actions ? I mean, it makes sense to set dates for the actions, and then look up for the project to see how can it reflect the "posible due date" or "possible start date", depending on the sequencial / parallel choices of the involved activities, right ? (Just like and decent Project tool, like OP does). Does that makes sense ?
|
The project's due date is inherited by the actions, so setting a due date on the project means you don't have to individually set due dates for all the actions if they aren't earlier than the project's due date. What value do I get by putting in a bunch of due dates which are identical to the project's due date? Most of the time (for me, at least), the actions themselves don't have a specific due date, it's just the project that needs to be completed by a deadline. Yes, if I don't notice during my review that I'm now assuming I'm going to do 48 hours of work in the next 6 hours, I'm going to miss that deadline, but a point of the review is to avoid that sort of scenario.
Quote:
|
- If I have a sequencial project : wouldn't it be nice if after the first action (and once you set up start / due dates for that action) the next action forces you to have a start date AT LEAST after the due date of the first action ?
|
How would this be an improvement? If I want the start date so that I don't see the remaining actions in an available actions view, the sequential nature of the project will accomplish that as well. If I want a start date on each action so that it shows up in a "Starts today" group, I can just select all the actions in the project and give them the same start date in the inspector when I create the project or look at it during the review. Also, why would the start date necessarily be after the due date of the previous action? Oddly enough, I do occasionally get things done before the due date, though I try to avoid making a habit of it :-) Forcing the start date of the next action to be no earlier than the due date of the previous action would cause progress on that project to halt whenever something was done ahead of schedule. Perhaps I'm not understanding what you are proposing...how about an example?