I would envision the lag thing a little different from how you described it, Lisa.
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 From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Friday, November 09, 2012 6:32 PM To: [email protected] Subject: Re: [MLO] MLO and project management Hi Lisa. How was your week? For sure, any project implementation would have to be a separate product, MLO Project. Sent from my android device. -----Original Message----- From: Lisa Stroyan <[email protected]> To: "Groups, Email" <[email protected]> Sent: Fri, 09 Nov 2012 17:53 Subject: Re: [MLO] MLO and project management I only use MLO as a personal organizer, but I too would find the idea of "lag" time quite useful, if it could be implemented in a way that fits the current design. With recurring tasks it's kind of, sort of, possible to set them up with a lag, but it's kludgy. If you set up a tree with child and parent, set the parent date's (e.g., every Monday starting X date), set child to the first offset (X +1, e.g. Tuesday), and if parent is set to recur and reset subtasks, then the two tasks will keep their offsets. (for both start and due dates). However, the date difference only is updated when the task recurs, so the "lag" must be created manually each time. You can't really set up a "template" (by which I simply mean a tree in my "Templates" folder, which is duplicated whenever needed) because editing the parent's date will not update the children's. I'm not sure how this could be cleanly implemented, though. There would have to be two new fields, start lag and due lag, and would they count from the parent or the sibling above them? It would be hard to explain to users, also. On Fri, Nov 9, 2012 at 1:00 PM, Mark Levison <[email protected]> wrote: Please don't turn MLO into something it isn't. It works well as a personal organizer. As Dwight (I think) mentioned its missing many things project management tools miss. Further the whole idea that you can just assign tasks to people and get high quality work done just perpetuates the myths I fight everyday, see: http://agilemanifesto.org-- Cheers Mark Levison Agile Pain Relief Consulting <http://agilepainrelief.com/notesfromatooluser> | Writing <http://agilepainrelief.com/notesfromatooluser/> Proud Sponsor of Agile Tour Gatineau Ottawa <http://goagiletour.ca/> Nov 28, Toronto <http://www.torontoagilecommunity.org/display/PUBLIC/Home> 26 and Montreal <http://agilemontreal.ca/agile-tour-2012/> 24 <mailto:[email protected]> Michael Emerald, CFA 9 November, 2012 11:56 AM I appreciated the comments from whomever talked about projects a day or two ago. I agree that MLO will probably not become a major force in the Project Management sphere, but for SMALL projects, I've been begging to see MLO upgraded to do so. Specifically, I enjoy the simple checklist format of MLO, far easier than marking bars 100% complete, or reading down a gantt chart to find what needs to be done or is slipping. On the other hand what I sorely miss in MLO, and I know it's been discussed before, is: a. Dependency relationships, and more importantly b. Lag times between steps. While the above are probably obvious, an example is setting up client meetings. There are about 20 steps I take, and MLO is perfect for it. 3 days before the meeting I prepare all client docs, and a day or so I send out a reminder, and the day of the meeting I prepare my web-conference environment. For this, I need a template that allows for lags. Manually changing the start date, or worse the due date, is cumbersome. But for repeating small projects, like client meetings, MLO fits the bill well. What do you think? Regards, Michael Emerald, CFA Performance Business Design Owner, Business Planner Performance Business Design: <http://www.performancebusinessdesign.com/> http://www.PerformanceBusinessDesign.com My Blog: <http://www.performancebusinessdesign.com/page14.php> http://www.performancebusinessdesign.com/page14.php -- 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] <mailto:mylifeorganized%[email protected]> . For more options, visit this group at http://groups.google.com/group/mylifeorganized?hl=en. -- 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. -- 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.
<<image001.jpg>>
