Lisa, You are right that I switched my tasks in midstream. Here's a concrete example. I have a project template that has a number of dependencies build into it. Most tasks inherit the start and due dates of the overall project, with the dependencies governing which ones appear in today's to-do list. However, after I deliver a proposed final document to a client I want to wait exactly one week before nagging for comments. Too early annoys the customer and enables counterproductive comments like "I'm sure it's fine, I trust you" (the consultants on this forum will recognize why this nice-sounding comment is deadly) and too late introduces delays into the remainder of the project. Right now I am including a @lag task "wait for comments" which is "hidden in to-do list" and I have a view that I see briefly every morning that shows @lag tasks that are due or overdue, all of which I immediately complete, which brings the nag task to my to-do.
Proposed: the nag task would have a + 1 week start date (based on the recurrence pattern, regenerate one week after task is completed) triggered by completion of the "deliver proposed final document to client for comment" task (based on the dependency screen "select all tasks on which the current task depends"). When I complete the "deliver" task the completion date + one week would be set as the "nag" task's start date. If the nag task has a defined and locked lead time, that would be used to establish the nag task's due date. One week later, it would pop onto my to-do. -Dwight From: [email protected] [mailto:[email protected]] On Behalf Of Lisa Stroyan Sent: Saturday, November 10, 2012 8:21 AM To: Groups, Email Subject: Re: [MLO] MLO and project management Which task does the second sentence refer to? I think you switched which task comes first, but even if I swap the first sentence I'm not quite sure what you mean. But, you are right, I think, that we only need a start lag, because the due date would track the start date on the second task, hopefully. Can you give an example? Lisa On Fri, Nov 9, 2012 at 8:55 PM, <[email protected]> wrote: The objective is to say that Task B starts x days after task A completes. I see that as a combination of two existing functions. One is the recurrence pattern that says the task recurs x days or weeks after it completes. The other is the dependence pattern that says that Task A starts when task B completes. Put them together and you get Task A starting x days or weeks after Task B completes. -Dwight -- Lisa _____ Lisa Stroyan, mailto: [email protected] <mailto:[email protected]> -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en. -- You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en.
