From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Sven Bretfeld" Subject: Re: AutOrg, and practice of GTD in a group Date: 27 Jun 2010 22:16:46 +0200 Message-ID: <87d3vcut75.fsf@gmx.ch> References: <20100622211941.GF520@now.cepheide.org> <87wrtqqmi5.fsf@gmx.ch> <20100624130005.GB920@now.cepheide.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from [140.186.70.92] (port=56444 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OSyIF-0003Hx-FI for emacs-orgmode@gnu.org; Sun, 27 Jun 2010 16:17:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OSyID-0002Tn-N9 for emacs-orgmode@gnu.org; Sun, 27 Jun 2010 16:17:31 -0400 Received: from mx5.rz.ruhr-uni-bochum.de ([134.147.64.33]:34260) by eggs.gnu.org with smtp (Exim 4.69) (envelope-from ) id 1OSyID-0002TU-8x for emacs-orgmode@gnu.org; Sun, 27 Jun 2010 16:17:29 -0400 In-Reply-To: <20100624130005.GB920@now.cepheide.org> (Hellekin O. Wolf's message of "Thu, 24 Jun 2010 13:00:06 +0000") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: "Hellekin O. Wolf" Cc: emacs-orgmode@gnu.org Hi Hellekin "Hellekin O. Wolf" writes: > On Wed, Jun 23, 2010 at 08:41:22AM +0200, Sven Bretfeld wrote: >> >> The third level is for the physical actions of the project. As you see, >> only the first has a todo keyword (NEXT). The others are dependent from >> the first (cannot be done before the first is done) and have only a >> context tag. My context tags include things like HOME, OFFICE, SHOPPING, >> TRAIN etc. When the first NEXT action is done, the next NEXT action in >> the list gains the NEXT todo keyword automatically; this is what the >> TRIGGER property cares for. In that way my Agenda Views (defined as >> NEXT/HOME, NEXT/OFFICE etc.) display only next actions that can be done >> immediately. >> > *** I like the concept of "chained actions" and the TRIGGER property. > Very smart, the auto-assignment to NEXT keeps you busy and focused, > and saves a number of key-strokes. > > But I guess that implies multiple NEXT items. Do you maintain several > of those, or one per project? Maybe I'm wrong--I didn't even read the > GTD book thoroughly yet--but I like having *one* NEXT action, so that > I don't get stuck with too many "next" things. I can understand one > NEXT action per project, but several within a single project raises > internal warnings. I think one of the main points in GTD is splitting up a task into multiple physical actions (potential NEXT steps) which can be done one after another depending on the available time, energy level and context. Usually they build up a procedural chain of actions that gradually bring the project to fulfillment. Sometimes there are actions that don't form part of the chain, because they can be done independently from previous steps. I usually put these things at the end of the project's action-list an give them the NEXT status right from the start. For example, this weekend I made my flat secure for my 8 months old son who just starts to crawl and touches every cable he can put his hands on: * Family ** Secure the apartment for the baby :PROJECT: *** NEXT Buy items [0/4] :SHOPPING: - [ ] devices to secure power outlets - [ ] sticky tape - [ ] wire protecting sleeves - [ ] new screws for the baby's bed :PROPERTIES: :TRIGGER: chain-siblings(NEXT) :END: *** secure all power outlets [0/6] :HOME: - [ ] living room - [ ] bathroom - [ ] sleeping room - [ ] child's room - [ ] corridor - [ ] kitchen *** tie all cables with tape :HOME: *** fix the baby bed :HOME: *** NEXT remove loose objects from small tables :HOME: The project has 5 physical actions. Four of them are dependent: First I have to buy what I need, then I can start working. So I buy the items and tick them of in the list one after another as I buy them (C-c C-c in such a list ticks the items and changes the number in the brackets). After I have them all, I set "Buy items" to DONE. Then "secure all power outlets" automatically gets the NEXT status, and so on. As you see, the fifth item "remove loose objects from small tables" can be done without buying anything. So I give it the NEXT status right from the start. It's important to place this item at the end of the list, so that it can't spoil the chain, if I give it the DONE status before the chained list is complete. In fact, for Emacs the last item is part of the chain, but that doesn't really matter in practice. All that could happen, is that I clear the tables before I have finished the other parts and set the fifth item to DONE. When I, then, set the "baby bed" item to DONE, the "loose objects" will get NEXT status again (I'm not quite sure if that really happens, I can't remember such a case). D. Allen recommends that you make a brainstorm when you are planning a project. What are the things I have to do in order to realize the plan? With orgmode you can make brainstorming very easy, just type M-RET and hack in what occurs to your mind. After that, sort the items into (sequential or independent) physical actions, references and so on. More often than not, your collection will still feature some items which are not physical actions, but sub-projects. If you notice that, you have to break them further down into physical actions. But, I think, you don't have to be too dogmatic with that. "Fix the baby bed" in fact consisted of more than one action (change screws, fix a certain plank, tie a cushion), but I had them all in mind and I planned to do them all simultaneously. So I didn't note them too accurately. Greetings, Sven