From: rene <jlr_0@yahoo.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bernt Hansen's
Date: Mon, 1 Dec 2014 10:22:48 +0000 (UTC) [thread overview]
Message-ID: <loom.20141201T111452-834@post.gmane.org> (raw)
In-Reply-To: 861tox7xwe.fsf@example.com
Sebastien Vauban <sva-news@...> writes:
> rene wrote:
>
> > I find his code pretty close to what GTD should look like. There are a few
> > things though that could be twicked a bit in order to comply with David
> > Allen's new book on Getting Things Done.
>
> Can you detail them, for our own information, please?
Here are a few thoughts. Feel free to provide feedback and enhancements.
Associating what GTD calls "Areas of Responsibility" to orgmode
categories is great. But launching a search for these categories (areas of
responsibility) has to be hardcoded in everyone's config file. It
would be great if this could work like for Tags (C-a a M) or Todo keywords
(C-a a T).
Why not have a "C-a a R" which would prompt us for our own various
Areas of Responsibility.
Of course there is an org-agenda-filter-by-category function but this
function should then work more as org-agenda-filter-by-tag where the
category would either be selected with a fast selection letter or when
you hit the TAB key you're being prompted for a list of possible
categories.
Within GTD, the way you are to choose which task to perform never
relies on a preset priority level but on three limiting criteria,
namely
- your context: What can I do where I am?
- your time available: How much time do I have?
- your energy: How much energy do I have
It's easy to implement your context as Tags: @home, @computer,
@office, @internet, @errands, etc. It's therefore easy to
extract/filter tasks pertaining to a particular context using "C-a a M".
I find the org-effort-property misleading. It looks like you're
talking about the energy criteria but in fact this deals with the
estimated time duration of a task. Could one straighten this up?
The estimated "task-duration" could then replace the misleading
"org-effort" property.
The "energy" level should work as the org-priority. "A" could mean
the task will require from me a high level of priority, whereas "C"
could mean a low level of priority.
In David Allen's new book, which should be available early 2015, the
three basic steps for the GTD method are: Capture, Clarify and
Organize. In terms of vocabulary, he's not talking about a "task to
refile" but rather an "action to clarify and organize", which in orgmode
would consist in assigning the right: context (tag), duration, energy,
project, where a project would pertain to a area of responsibility
(category).
For me this notion of projects (and sub-projects, sub-sub-projects, etc.) in
org-mode is not that easy to deal with. Maybe I need to investigate
things a bit more. Any idea would be welcome.
Since the Weekly Review is such a key part in the GTD methodology,
I don't think there's any real need to differentiate between active vs stuck
projects. Every 7 to 10 days, you will go over your projects and thus
identify the ones that need a next action to be defined. The ones
that are considered as DONE, if all their sub-actions and sub projects
are themselves done or canceled.
--
rene
next prev parent reply other threads:[~2014-12-01 10:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-16 20:21 TODO items in lists (not headings) Gary Oberbrunner
2014-09-16 20:32 ` Tory S. Anderson
2014-09-16 22:39 ` Gary Oberbrunner
2014-09-17 3:48 ` Thomas S. Dye
2014-09-17 12:45 ` Gary Oberbrunner
2014-09-18 0:41 ` Nick Dokos
2014-11-21 4:19 ` Bernt Hansen's rene
2014-11-21 8:36 ` Sebastien Vauban
2014-11-22 18:08 ` J. David Boyd
2014-12-01 10:22 ` rene [this message]
2014-11-23 18:46 ` Bernt Hansen
2014-09-18 16:23 ` TODO items in lists (not headings) Subhan Michael Tindall
2014-09-18 18:49 ` Gary Oberbrunner
2014-09-23 13:34 ` Gary Oberbrunner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20141201T111452-834@post.gmane.org \
--to=jlr_0@yahoo.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).